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.
MongoDB acquires Voyage AI
91–100 of 172 posts
Re: MongoDB acquires Voyage AI
#92Earlier quoted context omitted.
Citus is owned by Microsoft. And history has not been nice to startups like this continuing their products over the long term. It's why unless it is built-in and supported it's not feasible for most to depend on it.
that's fair, but that's true of mongodb itself too. I wouldn't count that against either of them.
Microsoft does not make money supporting Citus.
Re: MongoDB acquires Voyage AI
#93Earlier quoted context omitted.
Is it possible that they simply have a good product?
Impossible! It's not based on sqlite, postgres or written in rust, so it must be terrible!
Great products are in my opinion a function of skill and care. The only benefit a "popular" tool or language gets you is a greater developer pool for hiring.
Re: MongoDB acquires Voyage AI
#94Earlier quoted context omitted.
So does a text file. Statements like yours are meaningless when you aren't specific about the operations, schema, access patterns etc. If you have a single server, relational use case then PostgreSQL is great. But like all technology it's not great at everything.
The use a text file. In all seriousness, calling Postgres’ scalability “not-negotiable for most use cases” is wild.
"built-in, supported, proven scalability and high availability"
PostgreSQL does not have any of this. It's only good for a single server instance which isn't really enough in a cloud world where instances are largely ephemeral.
Re: MongoDB acquires Voyage AI
#95Earlier 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.
Why would I use anything other than sqlite?
Re: MongoDB acquires Voyage AI
#96Earlier quoted context omitted.
a) MongoDB has built-in, supported, proven scalability and high availability features. PostgreSQL does not. If it wasn't for cloud offerings like AWS Aurora providing them no company would even bother with PostgreSQL at all. It's 2025 these features are not-negotiable for most use cases. b) MongoDB does one thing well. JSON documents. If your domain model is built around that then nothing is faster. Seriously nothing…
> It's 2025 these features are not-negotiable for most use cases. Excuse me? I do enterprise apps, along with most of the developers I know. We run like 100 transactions per second and can easily survive hours of planned downtime. It's 2025, computers are really fast. I barely need a database, but ACID makes transaction processing so much easier.
Re: MongoDB acquires Voyage AI
#97Earlier quoted context omitted.
Postgres supports JSONB natively. It literally speaks mongo line protocol and you can shove unstructured json into it. It has supported this since 9.4: https://www.postgresql.org/docs/current/datatype-json.html
I don't necessarily agree with the above justifications, but in my experience this is basically why teams pick Mongo. It's easier to get started with.
Re: MongoDB acquires Voyage AI
#98Genuine 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.
MongDB is basically a pile of JSON in comparison, no matter how much you distribute and scale it.
Re: MongoDB acquires Voyage AI
#99Earlier quoted context omitted.
Postgres supports JSONB natively. It literally speaks mongo line protocol and you can shove unstructured json into it. It has supported this since 9.4: https://www.postgresql.org/docs/current/datatype-json.html
I don't necessarily agree with the above justifications, but in my experience this is basically why teams pick Mongo. It's easier to get started with.
But why is that the top priority?
Re: MongoDB acquires Voyage AI
#100Earlier quoted context omitted.
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.
Ahhh, this sounds familiar! https://www.youtube.com/watch?v=b2F-DItXtZs