Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MongoDB acquires Voyage AI

investors.mongodb.com

Post reply on HN
Print view View original

71–80 of 172 posts

Re: MongoDB acquires Voyage AI

#71

Post by hartator »

memco wrote: post #47
hartator wrote: post #28

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.

Can you share more details about the conditions under which it is slow in recent versions? We moved from 3.x to 7 for our main database and after adding a few indexes we were missing we have seen at least an order of magnitude speed up.

Most regular inserts and regular selects: https://medium.com/serpapi/mongodb-benchmark-3-4-vs-4-4-vs-5...

We have internally a benchmark with MongoDB 8.x, but same pattern of disappointing results.

Re: MongoDB acquires Voyage AI

#72

Post by hartator »

touche_bag wrote: post #56
hartator wrote: post #28

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.

I think 8 was a release purely focused on performance, with some big improvements. Comparing 3.4 is kinda unfair.. You were fast with the tradeoff of half your data missing half the time

That might explain the write performance degradation, but not the reads.

Re: MongoDB acquires Voyage AI

#73

Post by throw14082020 »

riku_iki wrote: post #70
jamesrr39 wrote: post #67

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.

Ahhh, this sounds familiar! https://www.youtube.com/watch?v=b2F-DItXtZs

Re: MongoDB acquires Voyage AI

#74

Post by SEJeff »

999900000999 wrote: post #69
jamesrr39 wrote: post #67

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?

Simple. Postgres is hard, you have to learn SQL. SQL is hard and mean. Mongo means we can just dump everyone into a magic box and worry about it later.No tables to create. But their is little time, we need to ship our CRUD APP NOW! No one on the team knows SQL! I'm actually using Postgres via Supabase for my current project, but I would probably never use straight up Postgres.

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

Re: MongoDB acquires Voyage AI

#75

Post by chpatrick »

999900000999 wrote: post #69
jamesrr39 wrote: post #67

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?

Simple. Postgres is hard, you have to learn SQL. SQL is hard and mean. Mongo means we can just dump everyone into a magic box and worry about it later.No tables to create. But their is little time, we need to ship our CRUD APP NOW! No one on the team knows SQL! I'm actually using Postgres via Supabase for my current project, but I would probably never use straight up Postgres.

Even as a JSON document store I'd rather use postgres with a jsonb column.

Re: MongoDB acquires Voyage AI

#76

Post by connectsnk »

beoberha wrote: post #64
connectsnk wrote: post #49

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.

True. I have that feeling many times that the enterprise crowd doesnt visits hacker news.

Re: MongoDB acquires Voyage AI

#77

Post by threeseed »

jamesrr39 wrote: post #67

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?

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. You can do tuple updates on complex structures at speeds that cripple PostgreSQL in seconds.

c) Nobody who is architecting systems ever thinks this way. It is never MongoDB or PostgreSQL. They specialise in different things and have different strengths. It is far more common to see both deployed.

Re: MongoDB acquires Voyage AI

#78

Post by 999900000999 »

SEJeff wrote: post #74
999900000999 wrote: post #69

Earlier quoted context omitted.

Simple. Postgres is hard, you have to learn SQL. SQL is hard and mean. Mongo means we can just dump everyone into a magic box and worry about it later.No tables to create. But their is little time, we need to ship our CRUD APP NOW! No one on the team knows SQL! I'm actually using Postgres via Supabase for my current project, but I would probably never use straight up Postgres.

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

#79

Post by jeremycarter »

threeseed wrote: post #77
jamesrr39 wrote: post #67

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?

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…

Great response. All arguments are valid and fair.

Re: MongoDB acquires Voyage AI

#80

Post by threeseed »

riku_iki wrote: post #70
jamesrr39 wrote: post #67

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.

High availability is more important than scalability for most.

On average an AWS availability zone tends to suffer at least one failure a year. Some are disclosed. Many are not. And so that database you are running on a single instance will die.

Question is do you want to do something about it or just suffer the outage.

Post reply on HN