go for a SQL Database, and when do you go for NoSQL?
very good question. Usually a RDBMS (SQL) is good for handling Relations, Foreign keys, etc. But this is not the only point. I'm interested how others will answer this :)
choose a db based on your data model, Something that'll lead to simpler code.
Nosql document stores solve only a subset of what sql solves. You can perfectly model anything that Nosql does in postgresql for example. The opposite is not true. Data, it's structure and relation to itself is what sql is about. It has been fine-tuned and battle-tested for almost half a century. So, to answer your question, I've used no sql only on very few projects with severe constraints on budget / personnel and lax / non-existant constraints for data.
Обсуждают сегодня