> you can go kinda sorta relational about it.
and reinvent half of a SQL engine inside your backend logic, badly.
(source: for the 3rd time, I'm working on a system that uses Mongo extensively, the goal is to move to Postgres as soon as that's viable)
Postgres does not scale. I have extensive experience in some of the largest databases ever built, postgres doesn't even come close.
Yeah, I wouldnt recommend doing MongoDB for EVERYTHING, but when you're using it for very specific things, you dont have to throw away everything you're already familiar with is all I was saying.