2. You can go from strict guarantees to looseness safely, when you demonstrably need to. The reverse isn't true -- it's easy to wind up realising, much too late, that you actually needed particular guarantees that you didn't even think of.
Relational databases didn't become incredibly popular by accident. It's because they were a drastic improvement -- theoretically and empirically -- on the generation of NoSQL databases that preceded them.
If you are just using one table with two fields (id/value and value contains a json object that changed) for logging perhaps a relational database isn't the right choice. Redis might be better / mongo might be better depending on what comes next.
Let's stop the next cycle where everyone moves to postgres for everything only to throw it away for the next thing. I was using postgres in 2008 and it was great.. why did it take until 2019 for everyone else to discover? We are in the peak postgres cycle. I hope it doesn't get disgarded when the serverless hype kicks into gear.
A lot of things “become popular” but that doesn’t necessarily mean they are good.
I’m bringing up C# again...
Querying with Mongo using the Mongo driver in C#....
var people = db.GetCollection<People>().AsQueryable();
var seniorMales = from p in people where p.Age >= 65 && p.Sex == “M” select p;
var people = context.People;
var seniorMales = from p in people where p.Age >= 65 && p.Sex == “M” select p;
NoSQL databases aren’t “schemaless”. Mongo understands the schema of JSON data and can query against it just like an RDMS understands rows and columns.
Too bad GlobalsDB went nowhere...