background preloader

CAP theorem

Facebook Twitter

Brewer's CAP Theorem. On Friday 4th June 1976, in a small upstairs room away from the main concert auditorium, the Sex Pistols kicked off their first gig at Manchester’s Lesser Free Trade Hall.

Brewer's CAP Theorem

There’s some confusion as to who exactly was there in the audience that night, partly because there was another concert just six weeks later, but mostly because it’s considered to be a gig that changed western music culture forever. So iconic and important has that appearance become that David Nolan wrote a book, I Swear I Was There: The Gig That Changed the World, investigating just whose claim to have been present was justified. Because the 4th of June is generally considered to be the genesis of punk rock6. We know three chords but you can only pick two The Sex Pistols had shown that barely-constrained fury was more important to their contemporaries than art-school structuralism, giving anyone with three chords and something to say permission to start a band.

Brewer’s (CAP) Theorem The Significance of the Theorem. A plain English introduction to CAP theorem « Kaushik Sathupadi. You’ll often hear about the CAP theorem which specifies some kind of an upper limit when designing distributed systems.

A plain English introduction to CAP theorem « Kaushik Sathupadi

As with most of my other introduction tutorials, lets try understanding CAP by comparing it with a real world situation. Chapter 1: “Remembrance Inc” Your new venture : Last night when your spouse appreciated you on remembering her birthday and bringing her a gift, a strange Idea strikes you. People are so bad in remembering things. And you’re sooo good at it. Remembrance Inc! So, your typical phone conversation will look like this: Customer : Hey, Can you store my neighbor’s birthday?

Chapter 2 : You scale up: Your venture gets funded by YCombinator. And there starts the problem. Your start with a simple plan: You and your wife both get an extension phone Customers still dial (555)–55-REMEM and need to remember only one number A pbx will route the a customers call to whoever is free and equally. Problems with CAP, and Yahoo’s little known NoSQL system. Over the past few weeks, in my advanced database system implementation class I teach at Yale, I’ve been covering the CAP theorem, its implications, and various scalable NoSQL systems that would appear to be influenced in their design by the constraints of CAP.

Problems with CAP, and Yahoo’s little known NoSQL system

Over the course of my coverage of this topic, I am convinced that CAP falls far short of giving a complete picture of the engineering tradeoffs behind building scalable, distributed systems. My problems with CAP CAP is generally described as the following: when you build a distributed system, of three desirable properties you want in your system: consistency, availability, and tolerance of network partitions, you can only choose two.

My second problem is that, as far as I can tell, there is no practical difference between CA systems and CP systems. As noted above, CP systems give up availability only when there is a network partition. (Note, readers from the academic community might wonder why I’m calling PNUTS “little known”.