Is important to take in context the SIZE. A lot of Ink is wrongly interpreted because people not think about the SIZE of the (data/problem). MOST, if not ALL(

Is important to take in context the SIZE. A lot of Ink is wrongly interpreted because people not think about the SIZE of the (data/problem). MOST, if not ALL(99%) of the thinking about this stuff is for the very end of the scale: Terabytes, dozen/thousand of machines, insane latency, etc. MOST, if not ALL(99%) of the ACTUAL data people deal with, the one that matters, is in the low of gigabytes, at best. One, maybe 2 servers, answer in a second(is) is more than ok. You can fit most databases in an iPhone with spare to work. Instead, the real trouble that people face is wrong schema/query designs, and introducing bugs and other stuff that the RDBMs thankfully correct/protect against. Making the primary store MORE strict is a big win to alleviate the real issues.