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.
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.
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
FerretDB allows you to use MongoDB drivers seamlessly with PostgreSQL as the database backend. Use all tools, drivers, UIs, and the same query language and stay open-source.
well see when you’re too lazy to design a schema and just want to throw broken data into a black hole where you may or may not be able to retrieve it and deal with the repercussions in production - or better yet let the ops team handle it at 3am - then that’s when you’d choose mongodb
34 Comments
optissima@lemmy.ml · 113 pts · 233d
Not understanding why I'd need mongodb over a traditional database paying dividends today
fahfahfahfah@lemmy.billiam.net · 53 pts · 233d
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
ThunderComplex@lemmy.today · 11 pts · 232d
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.
Croquette@sh.itjust.works · 4 pts · 232d
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.
count_dongulus@lemmy.world · 6 pts · 232d
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.
Croquette@sh.itjust.works · 3 pts · 232d
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.
qaz@lemmy.world · 31 pts · 233d
I've used it before but couldn't see the advantage over using JSONB with Postgres except change streams.
epyon22@sh.itjust.works · 13 pts · 233d
Glad I'm backed up in that jsonb solves the same problem
Dadifer@lemmy.world · 17 pts · 233d
Exactly what I was thinking 😂
Scipitie@lemmy.dbzer0.com · 12 pts · 233d
"gimme your mongodb url for me to do anything"
Last example where I was ... Annoyed by: unifi. Their management application demands a mongodb.
4am@lemmy.zip · 12 pts · 232d
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
qaz@lemmy.world · 11 pts · 232d
Maybe FerretDB will work.
richieadler@programming.dev · 6 pts · 232d
They even have a SQLite backend now.
4am@lemmy.zip · 2 pts · 230d
Oh sweet, thanks I will make a note to try this!
pupbiru@aussie.zone · 1 pts · 192d
well see when you’re too lazy to design a schema and just want to throw broken data into a black hole where you may or may not be able to retrieve it and deal with the repercussions in production - or better yet let the ops team handle it at 3am - then that’s when you’d choose mongodb
Deceptichum@quokk.au · 82 pts · 233d
qaz@lemmy.world · 25 pts · 233d
What are you referring to?
Deceptichum@quokk.au · 112 pts · 233d
qaz@lemmy.world · 53 pts · 233d
That's fucked up
flambonkscious@sh.itjust.works · 4 pts · 232d
Thanks for the not-linked url. MSN is gross, too but a lot less so
mp3@lemmy.ca · 31 pts · 233d
Found this while searching
https://nypost.com/2025/12/27/us-news/nyc-woman-driven-to-suicide-by-extreme-work-stress-at-hells-kitchen-tech-company-lawsuit/
kubica@fedia.io · 75 pts · 233d
Try to stay positive, think of all the software still using MongoDB that never got updated after 2016.
BlameTheAntifa@lemmy.world · 58 pts · 232d
This is small potatoes for a company that murders it’s employees in cold blood.
MashedTech@lemmy.world · 15 pts · 232d
HOLY FUCKING SHIT
flowers_galore2@lemmynsfw.com · 8 pts · 232d
Jesus fuckin christ that’s awful
patrick@lemmy.bestiver.se · 1 pts · 232d
Agent641@lemmy.world · 44 pts · 233d
One day I'll learn what webscale means, but it is not this day.
witty_username@feddit.nl · 44 pts · 233d
Agent641@lemmy.world · 32 pts · 233d
Gross, and I thought Rust was bad enough.
kibiz0r@midwest.social · 38 pts · 233d
Turns out we were better off piping data to /dev/null
qaz@lemmy.world · 17 pts · 233d
For GDPR compliance, absolutely
probable_possum@leminal.space · 8 pts · 233d
/dev/null ACE incoming soon. ;)
Thorry@feddit.org · 30 pts · 233d
MongoDB is normally not public facing right?
qaz@lemmy.world · 40 pts · 233d
It shouldn't be
enumerator4829@sh.itjust.works · 25 pts · 233d
How else would you be webscale?
anton@lemmy.blahaj.zone · 7 pts · 232d
The default configuration in 2017 was public write access, but those databases where taken over long ago.
goatinspace@feddit.org · 15 pts · 233d
sukhmel@programming.dev · 8 pts · 233d
I feel pain just by looking at it, definitely an instance of move fast break
thingsbones