Tag Info

Hot answers tagged

10

Because you can do many more things with real data besides display it in a web page. HTML is just a type of output that web browsers recognize, and it's not really useable as data in a meaningful way, because its metadata is about structure and form, not about the data itself. It also contains all sorts of things that have nothing to do with data output, ...


2

I believe there are more considerations here that you may not be looking for. There are two broad concerns here: Storage Search and Retrieval Storage There are plenty of opinions on why to use no-sql or RDBMS store for your data. One of the most important items that we thought was useful is that we can easily define and store json objects in storage ...


2

I think your question really boils down to: When should I use a NoSQL approach vs. RDBMS? You settled on JSON early (a NoSQL-ish decision), perhaps because you've got Ajax consumers. The answer of course to when to use NoSQL approaches vs. RDBMS's is basically about what type of data you're working with and what consumers you anticipate having. If your ...


1

There are many advantages to returning JSON or XML or returning HTML: JSON (or XML) is typically more compact, so you get better performance throughout the entire system. This matters a lot on mobile. Different browsers have different bugs. If you return JSON or XML, then you only need to handle the bugs in one place, rather than on every page that ...


1

In addition to the answers provided, there's also the fact that in an MVC or MVP front-end, you separate the data from the view. Plus it allows the backend to be useful for multiple projects. You can provide the same data, and have, for example, one application that displays it as a graph, one that uses it in its logic (e.g. a stock market analyser that ...


1

HTML is used for presentation in browsers, but it adds a lot of display artifacts (like <div>, <input>, <img> tags, etc.) XML and JSON aren't concerned with the display ... they can just send a plain representation of the data. How the user sees that data separate concern. By separating the two, you can use the same JSON in a lot of ...


1

In most applications there are requirements to Input data, perform some processing, save the data,retrieve the data and query the data. There may also be a requirement to generate reports on the data. Exchange data between different parts of the system or with external systems In order to achieve the requirements for Item 1 a method of persisting data is ...


1

First, if you're trying to Store JSON data in any storage but not a NoSQL database, I'd definitely discourage you to use JSON. The reason is that if you store your data as a JSON file, for example, then it will be extremely slow to open it, parse it, loop through it, etc. That begin said, I can narrow your question to: What are the pros and cons of NoSQL ...



Only top voted, non community-wiki answers of a minimum length are eligible