Dear awesome person,
this weeks paper is about a topic that can be considered ancient in our CS world. The CAP theorem was first introduced in 2000 and this weeks paper is revisiting it in 2012. In contrast to the age the theorem is still highly relevant for building distributed systems and will help you understand the short comings of distributed databases and cloud products
Did you ever asked yourself: “Why is DynamoDB only offering eventual consistent reads by default?”…the CAP theorem is the answer.
Software exists to create business value
I am Simon Frey, the author of the Weekly CS Paper Newsletter. And I have great news: You can work with me
As CTO as a Service, I will help you choose the right technology for your company, build up your team and be a deeply technical sparring partner for your product development strategy.
Checkout my website simon-frey.com to learn more or directly contact me via the button below.
Abstract:
Almost twelve years ago, in 2000, Eric Brewer introduced the idea that there is a fundamental trade-off between consistency,availability, and partition tolerance. This trade-off, which has become known as the CAP Theorem, has been widely discussed ever since. In this paper, we review the CAP Theorem and situate it within the broader context of distributed computing theory. We then discuss the practical implications of the CAP Theorem, and explore some general techniques for coping with the inherent trade-offs that it implies.
Download Link:
https://dspace.mit.edu/bitstream/handle/1721.1/79112/Brewer2.pdf