News for hackers. Stuff that matters.
Re:MongoDB Announces Acquisition of Voyage AI for $220M by riku_iki on Monday February 24, 2025 @04:52PM (#43165378)
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.
Re:MongoDB Announces Acquisition of Voyage AI for $220M by throw14082020 on Monday February 24, 2025 @04:55PM (#43165407)
Re:MongoDB Announces Acquisition of Voyage AI for $220M by riku_iki on Monday February 24, 2025 @06:32PM (#43166214)
things still can be true, even if being wrapped into meme videos by haters..
Re:MongoDB Announces Acquisition of Voyage AI for $220M by itake on Tuesday February 25, 2025 @02:06AM (#43169073)
Postgres has replicas? Most people use those for reads and a master writes.
Re:MongoDB Announces Acquisition of Voyage AI for $220M by Tostino on Tuesday February 25, 2025 @04:15PM (#43177507)
This can take you really damn far.

I've been playing with CloudNativePG recently and adding replicas is easy as can be, they automatically sync up and join the cluster without you thinking about it.

Way nicer than the bare-vm ansible setup I used at my last company.

Re:MongoDB Announces Acquisition of Voyage AI for $220M by codr7 on Monday February 24, 2025 @06:29PM (#43166196)
Calling MongoDB a real database compared to PostgreSQL is hilarious.

MongDB is basically a pile of JSON in comparison, no matter how much you distribute and scale it.

Re:MongoDB Announces Acquisition of Voyage AI for $220M by riku_iki on Monday February 24, 2025 @06:35PM (#43166240)
I think there is no distributed db on the market available with features parity to PgSQL. Distributed systems are hard, and sacrifices need to be made.
Re:MongoDB Announces Acquisition of Voyage AI for $220M by threeseed on Monday February 24, 2025 @05:13PM (#43165551)
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.

Re:MongoDB Announces Acquisition of Voyage AI for $220M by riku_iki on Monday February 24, 2025 @07:42PM (#43166728)
I think major providers provide PG service with cross zone availability through replication.
Re:MongoDB Announces Acquisition of Voyage AI for $220M by amazingamazing on Monday February 24, 2025 @05:30PM (#43165716)
It's sad that this was downvoted. It's literally true. MongoDB vs. vanilla Postgres is not in Postgres' favor with respect to horizontal scaling. It's the same situation with Postgres vs. MySQL.

That being said there are plenty of ways to shard Postgres that are free, e.g. Citus. It's also questionable whether many need sharding. You can go a long way with simply a replica.

Postgres also has plenty of its own strengths. For one, you can get a managed solution without being locked into MongoDB the company.

Re:MongoDB Announces Acquisition of Voyage AI for $220M by threeseed on Monday February 24, 2025 @05:41PM (#43165808)
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.

Re:MongoDB Announces Acquisition of Voyage AI for $220M by amazingamazing on Monday February 24, 2025 @05:48PM (#43165876)
that's fair, but that's true of mongodb itself too. I wouldn't count that against either of them.
Re:MongoDB Announces Acquisition of Voyage AI for $220M by threeseed on Monday February 24, 2025 @06:07PM (#43166033)
MongoDB makes money selling and supporting MongoDB.

Microsoft does not make money supporting Citus.

Re:MongoDB Announces Acquisition of Voyage AI for $220M by jwr on Monday February 24, 2025 @09:57PM (#43167560)
sigh

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.

Re:MongoDB Announces Acquisition of Voyage AI for $220M by riku_iki on Tuesday February 25, 2025 @01:07AM (#43168717)
Are you aware:

1. That PgSQL also has issues in jepsen tests?

2. of any distributed DB which doesn't have jepsen issues?

3. It is configurable behavior for MongoDB: can it lose data and work fast, or work slower and do not lose data. There is no issues of unintentional data loss in most recent(5yo) jepsen report for MongoDB.

Re:MongoDB Announces Acquisition of Voyage AI for $220M by jwr on Tuesday February 25, 2025 @01:46AM (#43168958)
Distributed databases are not easy. You can't simplify everything down to "has issues". Yes, I did read most Jepsen reports in detail, and struggled to understand everything.

Your second point seems to imply that everything has issues, so using MongoDB is fine. But there are various kinds of problems. Take a look at the report for RethinkDB, for example, and compare the issues found there to the MongoDB problems.

Re:MongoDB Announces Acquisition of Voyage AI for $220M by riku_iki on Tuesday February 25, 2025 @01:54AM (#43169005)
> Take a look at the report for RethinkDB

RethinkDB doesn't support cross document transactions, problem solved lol

Re:MongoDB Announces Acquisition of Voyage AI for $220M by theamk on Tuesday February 25, 2025 @01:17PM (#43175379)
PgSQL only defect was anomaly in reads which caused transaction results to appear a tiny bit later, and they even mentioned that it is allowed by standards. No data loss of any kind.

MongoDB defects were, let's say, somewhat more severe

[2.4.3] "In this post, we’ll see MongoDB drop a phenomenal amount of data."

[2.6.7] "Mongo’s consistency model is broken by design: not only can “strictly consistent” reads see stale versions of documents, but they can also return garbage data from writes that never should have occurred. [...] almost all write concern levels allow data loss.

[3.6.4] "with MongoDB’s default consistency levels, CC sessions fail to provide the claimed invariants"

[4.2.6] "even at the strongest levels of read and write concern, it failed to preserve snapshot isolation. Instead, Jepsen observed read skew, cyclic information flow, duplicate writes, and internal consistency violations"

let's not pretend that Mongo is a reliable database please. Fast? likely. But if you value your data, don't use it.

Re:MongoDB Announces Acquisition of Voyage AI for $220M by riku_iki on Tuesday February 25, 2025 @03:30PM (#43176960)
In attempt to understand your motives in this discussion, I would like to ask question:

* why you are referring on 12yo reports for very early MongoDB version?

Re:MongoDB Announces Acquisition of Voyage AI for $220M by jwr on Wednesday February 26, 2025 @08:54PM (#43190444)
This discussion refers to the entire history of MongoDB reports, which shows a lack of care about losing data.

If you wish to have a more recent MongoDB report, Jepsen is available for hire, from what I understand.

Re:MongoDB Announces Acquisition of Voyage AI for $220M by riku_iki on Wednesday February 26, 2025 @09:07PM (#43190524)
No, discussion started with question "Why choose Mongo in 2025?" So, old jepsen reports are irrelevant, and most recent one from 2020 is somehow relevant.