Hacker News Reader

I feel the opposite about SQL: It is often being shoehorned into use cases that don't fit the relative/transactional database model at all. My own default database is AWS DynamoDB, because it fits 90% of my own use cases quite well and offers a fast approach for iterative development. Recently I've been evaluating how to find the same level of abstraction in open source databases, and MongoDB feels like the closest match. Postgres with JSONB comes second, but manipulating JSON with SQL is not very comfortable and tends to result in subtle problems e.g. when something is NULL.

+1

I'd also like to understand whether there are still any cases when MongoDB is the right choice

Yes. My group is utterly incapable of adhering to a schema so it's easy for them to just dump data in roughly the right spot and let people like me worry about how to grab it back out in a systematic way.