Live data from Hacker News

MongoDB acquires Voyage AI

investors.mongodb.com

171–172 of 172 posts

Re: MongoDB acquires Voyage AI

#171
post #158

Earlier quoted context omitted.

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…

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?

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 acquires Voyage AI

#172
post #171

Earlier quoted context omitted.

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?

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.

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.
Post reply on HN