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
\|	\|	alexdebrie.com Inconsistent thoughts on database consistency \| DeBrie Advisory	3.6 parsecs away Travel
\|	\|	In this post, understand the different concepts of consistency as applied to distributed databases, as well as some issues with the conversation of consistency.	3.6 parsecs away Travel
\|	\|	blog.thislongrun.com Don't use the CAP theorem for node failures	3.8 parsecs away Travel
\|	\|	CAP theorem: node failure, process crash vs. partition and availability.	3.8 parsecs away Travel
\|	\|	blog.dtornow.com The CAP Theorem. The Bad, the Bad, & the Ugly \| Dominik Tornow	3.7 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.	3.7 parsecs away Travel
\|	\|	blog.willportnoy.com Will Portnoy: Lessons Learned from Implementing Paxos	38.1 parsecs away Travel
\|		My group at Microsoft uses Azure for many of its projects. We have a shared data store that we run as a service in Azure, and some of the g...	38.1 parsecs away Travel