/explore
|
You are here 
|
blog.thislongrun.com | ||
| | | | |
philipotoole.com
rqliteis a lightweight, user-friendly, open-source, distributed relational database. It's written inGoand usesSQLiteas its storage engine. When it comes to distributed systems the CAP theorem is an essential concept. It states that it's impossible for a distributed database to simultaneously provide Consistency, Availability, and Partition tolerance. The challenge is in the face of a network partition,... |
|
| | | | | ||
| | | | |
www.ssp.sh
|
|
| | | | | ||
| | | | |
blog.dtornow.com
The CAP theorem is too simplistic and too widely misunderstood to be of much use for characterizing systems. Therefore I ask that we retire all references to the CAP theorem, stop talking about the CAP theorem, and put the poor thing to rest Martin Kleppmann In 2000, Eric Brewer introduced the CAP Conjecture during his keynote address Towards Robust Distributed Systems at the Principles of Distributed Computing conference. Brewer posited that a distributed system cannot achieve Consistency, Availability, and Partition Tolerance simultaneously. |
|
| | | | | ||
| | | | |
sookocheff.com
Title and Author of Paper Cap Twelve Years Later: How the "Rules" Have Changed. Eric Brewer. Summary This article provides an exploration of the CAP Theorem and how it relates to database system design. The author argues that, since partitions are likely to happen, the system designer can introduce methods for safely recovering from partitions to compensate. This strategy allows the database to continue to provide availability during a partition, and enforce consistency once the partition is resolved. |
|
| | | |||
