All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Stonebraker Challenges NoSQL Community's Interpretation of CAP Theorem

By

onurkanbkrc

4mo ago· 3 min readenInsight

Summary

Mike Stonebraker challenges the NoSQL database community's interpretation and application of Eric Brewer's CAP Theorem. He argues that many NoSQL systems incorrectly claim the CAP theorem forces them to adopt eventual consistency models, pointing out that common database errors are not avoided by eventual consistency and that CAP doesn't apply in these cases. The article discusses Stonebraker's critique of how the database community has misapplied theoretical concepts to justify design choices.

Key quotes

· 3 pulled
Mike challenges the application of Eric Brewer's CAP Theorem by the NoSQL database community.
Many of the high-scale NoSQL system implementers have argued that the CAP theorem forces them to go with an eventual consistent model.
Mike challenges this assertion pointing that some common database errors are not avoided by eventual consistency and CAP really doesn't apply in these cases.
Snippet from the RSS feed
Mike Stonebraker published an excellent blog posting yesterday at the CACM site: Errors in Database Systems, Eventual Consistency, and the CAP Theorem. In this article, Mike challenges the application of Eric Brewer’s CAP Theorem by the NoSQL database com

You might also wanna read