|
You are here |
blog.thislongrun.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. | |
| | | | |
eli.thegreenplace.net
|
|
| | | | | [AI summary] An introductory post from a blog series detailing the implementation of the Raft distributed consensus algorithm in the Go programming language. | |
| | | | |
aphyr.com
|
|
| | | | | [AI summary] This technical blog post series introduces the concepts of distributed consensus and network partitions using the CAP theorem, while providing a tutorial on setting up a node cluster to experiment with database behavior during failures. | |
| | | | |
voxxeddays.com
|
|
| | | Hi Gunnar, tell us who you are and what lead you into microservices? I'm an open-source enthusiast and software engineer working at Red Hat, where I'm leading the Debezium project. Debezium is a platform for change data capture (CDC) based on Apache Kafka, allowing you to react to all the inserts, updates and deletes in [...] | ||