this post was submitted on 28 Aug 2025
373 points (99.2% liked)
Programmer Humor
26229 readers
1678 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
Every time I'm assigned to a project that uses a document database
"So how are you guys handling all your related data?"
Finds collection of massive JSON documents containing all the related data
"Oh boy."
What's the problem with that? In my previous team, we had a structure with four levels of nesting where we only ever needed to query the first two levels. At first we used Postgres with normalized tables, but it was just slow as hell. Switching to MongoDB actually made our performance issues vanish.
Of course it all depends on what kinds of queries you need to run, but I don't think that large JSON documents are necessarily a problem.
Those are rookie numbers.