4 ms·

I’m getting pretty damned tired of NoSQL as a default. Picking it because it matches your use case exactly is one thing, picking it because you want to avoid mo

I’m getting pretty damned tired of NoSQL as a default. Picking it because it matches your use case exactly is one thing, picking it because you want to avoid modeling your domain, building a schema, and managing migrations is a fool’s errand. All you’re doing is trading problems and ass ache, but I think NoSQL is less flexible than SQL. Hell, DocumentDB is built on Postgres, allegedly (is that confirmed?). I started at a new place that uses DynamoDB and I can’t articulate how much I loathe it. Currently rewriting it into Postgres as we speak.

Izkata 2y ago
> picking it because you want to avoid modeling your domain, building a schema, and managing migrations is a fool’s errand For anyone in this situation, maybe try tricking the NoSQL advocate like I did once: Postgres's json column is just like Mongo, except you also so get the same and more because it's a relational database on top of that. We can do some stuff unstructured, then the rest structured. I'm pretty sure that's not strictly true - I don't know a lot about Mongo, but neither did the person advocating for it on my team. It was enough though and the vast majority of the data ended up in normal columns instead of the json columns, with zero pushback.