CAP twelve years later: How the "rules" have changed
By Eric A. Brewer. Computer, 2012
686 citations recorded by the source corpus.
Subfields: Computer Networks and Communications, Information Systems
View Paper: https://www.semanticscholar.org/paper/c9c73f5a1668b8bf12aae2efb6ac5a5a2c34002a
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Computer Networks and Communications
- Nikolay Grozev
- Rajkumar Buyya
- Jennifer Petoff
- Betsy Beyer
- Roberto Baldoni
- Igor L. Markov
- Leonardo Aniello
- Chris Jones
In Information Systems
- Nikolay Grozev
- Rajkumar Buyya
- Jennifer Petoff
- Betsy Beyer
- Roberto Baldoni
- Igor L. Markov
- Leonardo Aniello
- Chris Jones
Citations in the corpus
- Limits on fundamental limits to computation (2014, background): “Technology-specific limits for modern computers tend to express tradeoffs, especially for systems with conflicting performance parameters and properties [88].”
- Inter‐Cloud architectures and application brokering: taxonomy and survey (2014, background): “In essence the NoSQL approach aims at balancing between consistency and partition tolerance following the result of the famous CAP theorem [32, 33], while NewSQL approaches keep to standard relational approaches but discourage or ban performing certain inefficient operations [31].”
- Site Reliability Engineering: How Google Runs Production Systems (2016, methodology): “CAP Theorem The CAP theorem ([Fox99], [Bre12]) holds that a distributed system cannot simulta‐ neously have all three of the following properties:”
- PBFT vs Proof-of-Authority: Applying the CAP Theorem to Permissioned Blockchain (2018, background): “Previous PoA algorithms are here compared with PBFT, first in terms of consistency and availability properties via the CAP Theorem (Section 4.1), then of performance (Section 4.2).”