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

111–120 of 172 posts

Re: MongoDB acquires Voyage AI

#111

Post by g8oz »

threeseed wrote: post #84
scosman wrote: post #82

Earlier quoted context omitted.

A) Postgres easily scales to billions of rows without breaking a sweat. After that shard. It’s definitely negotiable.

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.

If multiple nodes are needed, then why MongoDB and not a Postgres compatible distributed product like CockroachDB or YugabyteDB?

Re: MongoDB acquires Voyage AI

#112

Post by paxys »

schnebbau wrote: post #2

How does MongoDB still have that much available to spend? Everyone I know moved off it years ago.

MongoDB is a public company. Its quarterly financial reports will give you a much more accurate picture of the company's health than "everyone you know".

Re: MongoDB acquires Voyage AI

#113

Post by 999900000999 »

codr7 wrote: post #102
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.

If learning SQL is hard, maybe software isn't the best choice of career. Writing code and creating good software requires a lot of mental clarity and effort; that fact is never going to change, not even with AI.

Billions upon billions of value have been created just upon the premise that SQL is hard.

Firebase by and almost every NoSql technology is based upon this.

Re: MongoDB acquires Voyage AI

#114

Post by tristan957 »

threeseed wrote: post #94
scosman wrote: post #89

Earlier quoted context omitted.

The use a text file. In all seriousness, calling Postgres’ scalability “not-negotiable for most use cases” is wild.

What's wild is you misrepresenting what I said which was: "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.

Do you mean ephemeral clients or Postgres servers?

Re: MongoDB acquires Voyage AI

#115

Post by riku_iki »

threeseed wrote: post #80
riku_iki wrote: post #70

Earlier 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.

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.

I think major providers provide PG service with cross zone availability through replication.

Re: MongoDB acquires Voyage AI

#116

Post by cpursley »

threeseed wrote: post #81
thayne wrote: post #68

Earlier quoted context omitted.

> MongoDB ships with horizontal sharding out-of-the-box Maybe it's better than it was, but my experience with Mongodb a decade ago is that that horizontal sharding didn't work very well. We constantly ran into data corruption and performance issues with rebalancing the shards. So much so that we had a company party to celebrate moving off of Mongodb.

> my experience with Mongodb a decade ago So before the Apple Watch was released. Why is this relevant today ? Technology changes very quickly.

And Apple Watch still sucks as an actual watch vs a Casio.

Re: MongoDB acquires Voyage AI

#117

Post by cryptonector »

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.

I thought this was sarcasm till the last sentence. Now I'm not sure.

Re: MongoDB acquires Voyage AI

#118

Post by rudolph9 »

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?

Don’t choose Mongo. It does everything and nothing well. It’s a weird bastard of a database—easily adopted, yet hard to get rid of. One day, you look in the mirror and ask yourself: why am I forking over hundreds of thousands of dollars for tens of thousands' worth of compute and storage to a company with a great business operation but a terrible engineering operation, continually weighed down by the unachievable business requirement of being everything to everyone?

Re: MongoDB acquires Voyage AI

#119

Post by tiltowait »

chpatrick wrote: post #75
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.

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

Why is that? I found Postgres's JSONB a pill to work with beyond trivial SELECTs, and even those were less ergonomic than Mongo.

Re: MongoDB acquires Voyage AI

#120

Post by koakuma-chan »

margalabargala wrote: post #95
koakuma-chan wrote: post #91

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.

Damn good point! didn't think about that!
Post reply on HN