Outer Web | Explore

Explore >> Select a destination

You are here		compositecode.blog Composite Thrashing Code Adron's success in misadventures of thrashing coding and calamity! MongoDB and CAP Theorem: Key Insights
\|	\|	blog.thislongrun.com Don't use the CAP theorem for node failures	12.5 parsecs away Travel
\|	\|	CAP theorem: node failure, process crash vs. partition and availability.	12.5 parsecs away Travel
\|	\|	blog.dtornow.com The CAP Theorem. The Bad, the Bad, & the Ugly \| Dominik Tornow	11.3 parsecs away Travel
\|	\|	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.	11.3 parsecs away Travel
\|	\|	blog.thislongrun.com The confusing CAP and ACID wording	13.1 parsecs away Travel
\|	\|	CAP theorem and databases: definitions of ACID, Atomic, Consistent, Isolated, Durable vs. available and partition.	13.1 parsecs away Travel
\|	\|	www.mattritter.me Backend In the Frontend: Implementing Raft in JS - Coding, Climbing, and Commentary	88.5 parsecs away Travel
\|		Background Lately I've been studying consensus algorithms to bolster my understanding of distributed systems. Consensus algorithms achieve agreement on data that is replicated across many nod...	88.5 parsecs away Travel