this post was submitted on 29 Dec 2025
342 points (99.7% liked)
Programmer Humor
28379 readers
1059 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Not understanding why I'd need mongodb over a traditional database paying dividends today
The fact that a lot of relational databases now offer document storage does lend credence to the idea, but at the same time you lose so much when you only have document storage
But if you’ve planned your app through and know beforehand you don’t need relational data, you can skip the overhead of a RDBMS.
At least that’s what I would say if I hadn’t been in this exact situation and it later turned out we do need relational data so we had relational documents.
Also working with MongoDB without ODM is pure pain.
Side tracking here : to me, it seems like every DB is relational, no?
What use case would a DB used and not be relational? With my minimal experience in DB, I haven't seen any other use cases than a relational DB.
Cache-like storage, private user-specific data, blobby or otherwise schemaless data. Stuff like that. But IMO it's a matter of time until you find a need to operate against this data relationally, and then you regret using document storage. I've made this mistake twice now and do not intend to make it again. I now consider document storage architecture to be a performance optimization with significant tradeoffs, and not a choice to be made by default for nearly any scenario.
My reason asking is because there are other scheme I feel are more adequate for non relational data, but this isn't my domain and I barely dabbled in that, so that's worth absolutely nothing.
But your point about the data being used later makes a lot of sense and I didn't think about that. Down the road, someone will ask you to create links to your data and if you already have a DB, then you don't have to change the whole infrastructure to accommodate that. You can create new schemes and already have a somewhat functional access to it.
Thanks for the input.
I've used it before but couldn't see the advantage over using JSONB with Postgres except change streams.
Glad I'm backed up in that jsonb solves the same problem
Exactly what I was thinking 😂
"gimme your mongodb url for me to do anything"
Last example where I was ... Annoyed by: unifi. Their management application demands a mongodb.
This has actually prevented me from upgrading it because my homelab hardware was one generation too old for AVX instructions, which are required now. And now hardware is going to be priced out of range for average people.
Anyway I just said fuck it and I’m using the ISP router. I’ve too much other bullshit to deal with. Fuck MongoDB
Maybe FerretDB will work.
They even have a SQLite backend now.
Oh sweet, thanks I will make a note to try this!