Jepsen Disputes MongoDB's Data Consistency Claims
1–10 of 416 posts
Re: Jepsen Disputes MongoDB's Data Consistency Claims
#2Oh, Jepsen and MongoDB again? Somebody get the popcorn!
Re: Jepsen Disputes MongoDB's Data Consistency Claims
#3The Jepsen analysis : https://jepsen.io/analyses/mongodb-4.2.6
Re: Jepsen Disputes MongoDB's Data Consistency Claims
#4Oh, Jepsen and MongoDB again? Somebody get the popcorn!
Unfortunately, not an entertaining showdown - too one-sided.
Re: Jepsen Disputes MongoDB's Data Consistency Claims
#5From the jepsen report:
"""
Curiously, MongoDB omitted any mention of these findings in their MongoDB and Jepsen page. Instead, that page discusses only passing results, makes no mention of read or write concern, buries the actual report in a footnote, and goes on to claim:
> MongoDB offers among the strongest data consistency, correctness, and safety guarantees of any database available today.
We encourage MongoDB to report Jepsen findings in context: while MongoDB did appear to offer per-document linearizability and causal consistency with the strongest settings, it also failed to offer those properties in most configurations.
"""
This is a really professional to tell someone to stop their nonsense.
Re: Jepsen Disputes MongoDB's Data Consistency Claims
#6Re: Jepsen Disputes MongoDB's Data Consistency Claims
#7From the jepsen report: """ Curiously, MongoDB omitted any mention of these findings in their MongoDB and Jepsen page. Instead, that page discusses only passing results, makes no mention of read or write concern, buries the actual report in a footnote, and goes on to claim: > MongoDB offers among the strongest data consistency, correctness, and safety guarantees of any database available today. We encourage MongoDB t…
From top of linked article:
>>> I have to admit raising an eyebrow when I saw that web page. In that report, MongoDB lost data and violated causal by default. Somehow that became "among the strongest data consistency, correctness, and safety guarantees of any database available today"! It's not wrong, just misleading. Seems overblown given that most practitioners know how to read this kind of marketing speak.
Re: Jepsen Disputes MongoDB's Data Consistency Claims
#8I think it's remarkable this report has been out for a week now and no one at MongoDB has commented on it. At least, not that I have seen.
Re: Jepsen Disputes MongoDB's Data Consistency Claims
#9Discussed previously:
Re: Jepsen Disputes MongoDB's Data Consistency Claims
#10From the jepsen report: """ Curiously, MongoDB omitted any mention of these findings in their MongoDB and Jepsen page. Instead, that page discusses only passing results, makes no mention of read or write concern, buries the actual report in a footnote, and goes on to claim: > MongoDB offers among the strongest data consistency, correctness, and safety guarantees of any database available today. We encourage MongoDB t…
From top of linked article: >>> I have to admit raising an eyebrow when I saw that web page. In that report, MongoDB lost data and violated causal by default. Somehow that became "among the strongest data consistency, correctness, and safety guarantees of any database available today"! It's not wrong, just misleading. Seems overblown given that most practitioners know how to read this kind of marketing speak.
I appreciate your optimism in thinking that most (all?) people reaching for distributed systems actually know enough in the space to evaluate such claims.