> If you're thinking in the first terms, is a relational DB the right backing store, or wouldn't it be better to back your DB with something more like Mongo?
Certainly relational like for 90% of the cases, if not all.
The relational model is THE answer to nosql from the start (ie: it was the solution of the originals "nosql").
Is totally more flexible, powerful, dynamic, expressive... And that without talking about ACID!
You can model all "nosql" stores with tables. With limited exceptions it will work very fine for most uses...
> This is simply a standard management question with very little technical relevance.
I don't get what your are implicating here...
But nosql solutions are the ones to be suspected and the ones to requiere a harder qualifications and justifications to use. Is the wrong choice in the hands of the naive. "NoSql" is for experts and for niche/specific workloads.
Certainly relational like for 90% of the cases, if not all.
The relational model is THE answer to nosql from the start (ie: it was the solution of the originals "nosql").
Is totally more flexible, powerful, dynamic, expressive... And that without talking about ACID!
You can model all "nosql" stores with tables. With limited exceptions it will work very fine for most uses...
> This is simply a standard management question with very little technical relevance.
I don't get what your are implicating here...
But nosql solutions are the ones to be suspected and the ones to requiere a harder qualifications and justifications to use. Is the wrong choice in the hands of the naive. "NoSql" is for experts and for niche/specific workloads.