But do we really check & verify whether the website is making a network call & posting the document to their server? We need to be careful about that when we need to parse sensitive data something that belongs to real user. As I mentioned, mostly this parsing is done in client side. We are using online websites & submitting our document to some form where it is getting parsed. So why should we bother about having an offline JSON validator or parser? I would like to point out a couple of things, though these mostly depend on personal use cases or choice. I personally find to be more performant while parsing large JSON files. Obviously there are few websites which are popular & perform this task pretty well & efficiently. And if the JavaScript code is not well written, your browser might hang. So the processing directly consumes memory allocated to your browser. Instead client side code like JavaScript will parse the JSON text within browser. It can’t leverage the resources of the server. So our JSON text won’t be sent to server where it can be processed & parsed. The challenge is that these websites do parsing mostly in client side. Frequently we can see performance issues when we try to parse a decent size JSON document maybe sized several megabytes.
But not all the JSON parsing/formatting online tools are good. We can even collapse or expand different sub-sections of the JSON text conveniently. They take unformatted JSON text, parse it, do validation & show the formatted JSON back to the user.
How do we generally do that? There are multiple online websites which do exactly that.
Parsing & figuring out details from large JSON documents is a regular thing. Or there are NoSQL databases like MongoDB which store JSON documents. It is a common format for REST API payload. As software developers we encounter JSON format frequently, especially if we are into developing web apps.
0 kommentar(er)
