Tag Info

New answers tagged

1

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

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 ...


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 ...


0

I think you should use both and I don't see it as a 'versus' decision. A relational database makes sense for fast and efficient storage and retrieval of data that has relational properties. JSON is a great data format because it is simple, lightweight and ideal for passing around raw data in a very basic format with a syntax suited to storing and ...


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 ...


-1

I think you will have better success with using NoSQL than SQL for storing this data, because of the queries you need to do. Also just because some data is purely relational does not mean, anymore, it must be persisted into some RDBMS (SQL). IMO relational data would translate better into graph databases. Of course you can also write the queries in SQL but ...



Top 50 recent answers are included