Jepsen Disputes MongoDB's Data Consistency Claims (infoq.com)

Article summary

The article discusses Jepsen's dispute of MongoDB's data consistency claims. MongoDB's page on Jepsen's analysis is said to be misleading, as it only mentions passing results and omits findings that show data loss and consistency violations. The discussion revolves around the accuracy of MongoDB's claims and the trade-offs of using NoSQL databases. The Jepsen report highlights MongoDB's limitations in terms of data consistency and safety guarantees.

Main themes

• MongoDB's data consistency claims
• NoSQL databases vs relational databases
• Marketing and transparency
• Database trade-offs
• Data safety and consistency guarantees
• Company culture and response to criticism

What commenters say

• MongoDB's marketing claims are misleading and omit important findings from Jepsen's analysis.
• The company's failure to acknowledge and address these issues is a concern for users and potential users.
• Some argue that MongoDB has improved over time and that its limitations are well-known, while others believe that the company's marketing tactics are deceptive.
• Relational databases, such as MySQL and PostgreSQL, are often preferred for their stronger consistency guarantees, despite potential performance trade-offs.
• The choice of database ultimately depends on the specific use case and the trade-offs one is willing to make.
• MongoDB's response to criticism, or lack thereof, is seen as a sign of a larger cultural shift towards sales and corporatism.
• The importance of transparency and honesty in marketing and technical discussions is emphasized.
• The limitations and potential drawbacks of NoSQL databases, including MongoDB, are highlighted as important considerations for users.