121–130 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.
I understand the criticisms, but in my experience, MongoDB has come a long way. Many of the earlier issues people mention have been addressed. Features like sharding, built-in replication, and flexible schemas have made scaling large datasets much smoother for me. It’s not perfect, but it’s a solid choice.
I think the amount of people working on large enterprise systems here is a lot smaller than one would think. Whenever a fly.io post about sqlite ends up in here, there are a scary amount of comments about using sqlite in way more scenarios than it should be.
SQLite is a lean and clean tool, it's very much a candidate for being inserted into all manner of contexts.
What beggars belief is the overly complicated, inefficient, rats nests of trendy software that developers actually string together to get things done, totally unaware of how they are implemented or meant to work.
By comparison using SQLite outside of its "blessed (by who?) use cases" is very practical.
Earlier quoted context omitted.
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.
Pretending a pile of json is a database is great for pivoting, not so great for anything else. Maintaining apps built on MongoDB is soul killing.
Earlier quoted context omitted.
I think the amount of people working on large enterprise systems here is a lot smaller than one would think. Whenever a fly.io post about sqlite ends up in here, there are a scary amount of comments about using sqlite in way more scenarios than it should be.
True. I have that feeling many times that the enterprise crowd doesnt visits hacker news.
But mainly because management hasn't worked out how to cancel their licenses without breaking their budgets.
Earlier quoted context omitted.
Why would I use anything other than sqlite?
Easy. Sometimes it's more than you need, and there's no reason to use sqlite when you can just write things to a flat text file that you can `grep` against.
Earlier quoted context omitted.
Is it possible that they simply have a good product?
They do have a good product, but "they accumulate tech debt for years, all their devs leave, now they can't move away" is the story of the place I worked at a few years ago. The database was such a disorganized, inconsistent mess that no-one had the stomach (or budget) to try and get off it.
Genuine question: I appreciate the comments about MongoDB being much better than it was 10 years ago; but Postgres is also much better today than then as well. What situations is Mongo better than Postgres? Why choose Mongo in 2025?
Mongo is real distributed and scalable DB, while postgres is single server DB, so main consideration could be if you need to scale beyond single server.
See https://jepsen.io/analyses for how MongoDB has a tradition of incorrect claims and losing your data.
Distributed databases are not easy. Just saying "it is web scale" doesn't make it so.
Looks like everyone is jumping into the AI game. Is there a bubble?
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?