Again this topic brings out the "Always use relational databases" folks. Few say "Always use NoSQL stores". Most of us who use NoSQL, use it in conjunction wi

Again this topic brings out the "Always use relational databases" folks. Few say "Always use NoSQL stores". Most of us who use NoSQL, use it in conjunction with other stores, some of which are relational databases and some aren't. Lunch isn't free, blah blah, etc. However with NoSQL solutions, we can optimize the things we care about (reads and writes) over the things that happen rarely (changes to the schema, indexing, etc) if we want to. Sometimes our apps demand it, sometimes before the cash exists to even try to use oracle or the people you have to hire to properly support it. I don't get why people steadfastly assume everything fits the paradigm they're most comfy with. It doesn't. People who are just as comfy with your paradigm found stuff that works better, easier for them.