|
You are here |
paulkernfeld.com | ||
| | | | |
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. | |
| | | | |
scorpil.com
|
|
| | | | | How the CAP theorem explains trade-offs in software engineering organizations between quality, velocity, and communication. | |
| | | | |
shortdiv.com
|
|
| | | | | [AI summary] The article explains the CAP theorem, detailing the tradeoffs between Consistency, Availability, and Partition Tolerance when designing distributed systems. | |
| | | | |
hashingit.com
|
|
| | | What's the best way to get a return when we mine Bitcoins? Should we mine on our own, mine with a small pool or mine with a large pool? How much difference does it really make? Whether we want to be a gambler or an investor is really a question of how much risk we're prepared to take, but what are those risks and what are the odds of success? | ||