design - How to: SQL or NOSQL? -

I have not been faced with it yet, but this is what I think (very superficial and simple imho)

If you have an important value type of storage and use all the main lookups you use, NOSQL solution, if you want a lookup based on values ​​(and subvolumes) or some more complex As you would go for a relational solution transaction = Relational (it is also not certain if the nosql solution supports this assumption so far) also looks like NOSQL = denormalized (SQL) (I could be mistakenly wrong here)

In general, any principles / guidelines / thumb rules for deciding to choose a data model for your application. There are several factors to select DB implementation, some of which are:

<> li> < / Li>

Cost: Knowledgeable DBS open source, lean more towards cheaper side

Scalability: NOXQ can do better scale with cheap hardware

If you have a lot All you meet should go for a traditional RDBMS

Compatibility guarantees vary depending on the solution used. Ti are. NoSQL

You can also see the following podcast: SE radio.