Outer Web | Explore

/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.

You are here		blog.thislongrun.com Comparing Eventually Consistent and CP-as-in-CAP stores
\|	\|	paulkernfeld.com How Bitcoin Loses to the CAP Theorem - Paul Kernfeld dot com	11.7 parsecs away Travel
\|	\|	Mostly software: Rust, machine learning, and P2P systems. Previously, games and cocktails.	11.7 parsecs away Travel
\|	\|	philipotoole.com Consistency Over Availability: How rqlite handles the CAP Theorem - Philip O'Toole	3.2 parsecs away Travel
\|	\|	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,...	3.2 parsecs away Travel
\|	\|	www.allthingsdistributed.com Eventually Consistent \| All Things Distributed	9.1 parsecs away Travel
\|	\|	Werner Vogels on building scalable and robust distributed systems	9.1 parsecs away Travel
\|	\|	sookocheff.com Paper Review: Cap Twelve Years Later: How the "Rules" Have Changed \| Kevin Sookocheff	13.8 parsecs away Travel
\|		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.	13.8 parsecs away Travel