Unfortunately, not an entertaining showdown - too one-sided.

I remember having immensely enjoyed the original "Call me maybe" analysis [https://aphyr.com/posts/284-jepsen-mongodb]. Sometimes it's just fun to see someone beaten.

Because MongoDB is web scale?

Some readers might not be familiar with that particular meme: https://m.youtube.com/watch?v=b2F-DItXtZs

IMHO it perfectly describes the hype-reality disconnect at the early days of MongoDB. Yeah it was that bad.

Mongo has improved since, the hype has toned down and the NoSQL space is more crowded these days.

i remember diaspora chanting about using mongodb.

then a year or two later they admitted that their data model mostly fitted the relational model, and that they spent a lot of time basically reimplementing relational integrity in application code, in ruby.

yeah, diaspora has never been fast. I'm not sure they can blame it on mongodb though.

I remember the Mongo hype when it came out and I really couldn't understand it. You are just throwing away a lot of useful features of a relational database because "schemaless" and "big data". The majority of people using it were on single server setups.

The damage is done. I have to use this crap at work when we should be using an SQL database. We have been planning a migration since before I started a year and a half ago. I won't be surprised if we are still on Mongo in another year and a half.

Fantasy: "Don't use special database features (by which I mean, like, any features) and make sure our ORM supports a ton of different datastores because we might want to change to a different database at some point and don't want to be tied to this one."

Reality: Three app rewrites later plus another application written talking to the same DB, and the database is still the same.

Oh that brings back memories ;)