3 ms·
> I have a hard time understanding why devs choose / chose MongoDB. Postgres with JSON columns gets you so far, why would you go with MongoDB, given the issues
by s_kilk 9y ago
> I have a hard time understanding why devs choose / chose MongoDB. Postgres with JSON columns gets you so far, why would you go with MongoDB, given the issues it's had?
Jsonb is a pretty recent addition to postgres, when compared with the MongoDB timeline. And even today postgres still doesn't have the replication/failover story that made MongoDB pretty compelling. I know, it's coming, whatever, but the point is that there was a time where if you wanted a json store that could stay alive through network issues, MongoDB was one of the only choices available, and postgres simply didn't have what was needed.
- tensor 9y agoThe problem with that thinking is that the replication mattered. I'd argue it didn't, it was essentially a scam that people fell for. Who cares about failover when you're losing data due to a bad implementation? Who cares about replication when you can gain the same performance by using a performant database on a single node? Did mongodb truly allow anyone to really horizontally scale? Most places that need massive horizontal scaling using something like mysql as far as I know.
- imtringued 9y agoThe thing I don't understand about mongodb is that it makes a tradeoff for scalability. The secret ingredient in the horizontal scaling sauce is giving up inter node ACID transactions. Nothing prevents you from making the same tradeoff with mysql or postgresql.
- eloff 9y agoIndeed, that's how youtube, twitter, and facebook use MySQL, among others.