21–30 of 172 posts
How does MongoDB still have that much available to spend? Everyone I know moved off it years ago.
that’s what I thought, but every single candidate I interviewed mentioned MongoDB as their recent reference document database, I asked the last candidate if they were self-hosting, the answer is no, they used MongoDB cloud.
thats the reason for using Atlas
Earlier quoted context omitted.
Pretty sure they achieved fiscal nirvana by exploiting enterprise brain rot. You hook em, they accumulate tech debt for years, all their devs leave, now they can't move away & you can start increasing prices. Eventually the empty husk will topple over but that's still years away.
Is it possible that they simply have a good product?
https://gist.github.com/cpursley/c8fb81fe8a7e5df038158bdfe0f...
What am I missing? Are Mongo users simply front end folks who didn't have time to learn basic SQL or back end architecture?
How is MongoDB still a thing when there's already several ways to handle json in Postgres including Microsofts new documentdb extension: https://gist.github.com/cpursley/c8fb81fe8a7e5df038158bdfe0f... What am I missing? Are Mongo users simply front end folks who didn't have time to learn basic SQL or back end architecture?
How is MongoDB still a thing when there's already several ways to handle json in Postgres including Microsofts new documentdb extension: https://gist.github.com/cpursley/c8fb81fe8a7e5df038158bdfe0f... What am I missing? Are Mongo users simply front end folks who didn't have time to learn basic SQL or back end architecture?
also, I'd challenge your thinking - ultimately the goal is to solve problems. you don't necessarily need SQL, or relations for that matter. that being said, naively modeling your stuff in mongodb (or other things like dynamodb) will cause you severe pain...
what's also true, which people forget, is naively modeling your stuff with a relational database will also cause you pain. as they sometimes say, normalize until it hurts, and then denormalize to scale and make it work
the amount of places I've seen that skip the second part and have extremely normalized databases makes me cringe. it's like people think joins are free...
How does MongoDB still have that much available to spend? Everyone I know moved off it years ago.
We use it a lot for a specific use-case and it works great. Mongo has come a long long way since the release over a decade ago, and if you keep it in Majority Read and Write, it's very reliable. Also, on some things, it allows us to pivot much faster. And now with the help of LLMs, writing "Aggregation Pipelines" are very fast.
How does MongoDB still have that much available to spend? Everyone I know moved off it years ago.
We use it a lot for a specific use-case and it works great. Mongo has come a long long way since the release over a decade ago, and if you keep it in Majority Read and Write, it's very reliable. Also, on some things, it allows us to pivot much faster. And now with the help of LLMs, writing "Aggregation Pipelines" are very fast.
Maintaining apps built on MongoDB is soul killing.
Last MongoDB is still slower than MongoDB 3.4. An almost 10-year old release. For both reads and writes.
I rather them focus on performance. Last MongoDB is still slower than MongoDB 3.4. An almost 10-year old release. For both reads and writes.