Stonebraker on CAP theorem and Databases
6 days ago
- #NoSQL
- #Database Consistency
- #CAP Theorem
- Mike Stonebraker challenges the NoSQL community's application of the CAP Theorem, arguing that eventual consistency doesn't prevent common database errors like application or implementation bugs.
- Network partitions, though claimed to be rare by Stonebraker, are still a significant issue due to networking configuration errors and hardware problems.
- Deferred delete is highlighted as a useful technique for data recovery, marking items as deleted but not immediately removing them.
- The debate between eventual consistency and full consistency is discussed, with arguments that full consistency can be more practical and less surprising for developers.
- Amazon SimpleDB's support for full consistency is mentioned as a positive development for applications requiring strict consistency.
- The discussion concludes that both consistency models have their place, but full consistency might be a better default due to its straightforward semantics.