Outer Web | Explore

Explore >> Select a destination

You are here		blog.thislongrun.com Comparing Eventually Consistent and CP-as-in-CAP stores
\|	\|	compositecode.blog Composite Thrashing Code Adron's success in misadventures of thrashing coding and calamity! MongoDB and CAP Theorem: Key Insights	12.9 parsecs away Travel
\|	\|	The CAP theorem emphasizes the trade-offs between Consistency, Availability, and Partition Tolerance in distributed systems like MongoDB. Prioritizing Availability and Partition Tolerance, MongoDB uses replica sets and sharding for resilience while allowing configurable consistency. Its support for ACID transactions helps maintain data integrity, enabling tailored solutions for varying application requirements.	12.9 parsecs away Travel
\|	\|	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
\|	\|	blog.dtornow.com The CAP Theorem. The Bad, the Bad, & the Ugly \| Dominik Tornow	7.5 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.	7.5 parsecs away Travel
\|	\|	ferd.ca A Distributed Systems Reading List	95.1 parsecs away Travel
\|		An old document I surfaced with my quick tour of distributed systems theory fundamentals	95.1 parsecs away Travel