bibliography & references
- Martin Kleppman, "Please stop calling databases CP or AP". blog
- Martin Kleppman, "Designing Data-Intensive Applications". book
- Coda Hale, "You can't sacrifice partition tolerance". blog
- Doug Terry, "Replicated data consistency explained through baseball". paper
- Henry Robinson, The Paper Trail, "The CAP FAQ". article
- Kyle Kingsbury, "Consistency Models". blog
- Kyle Kingsbury, "The network is reliable". blog
- Jeff Dean, "Designs, lessons and advice from building large distributed systems". slides
- Salome Simon, "Brewer's CAP Theorem". paper
- Jeff Hodges, "Notes on distributed systems for young bloods". blog
- David Kravets, "It's Official: Sharks no longer a threat to subsea Internet cables". article
- Daniel Abadi, "Problems with CAP, and Yahoo's little known NoSQL system". blog
- Eric Brewer, "Lessons from giant-scale services". paper
- Phillipa Gill, Navendu Jain, Nachiappan Nagappan, "Understanding network failures in data centers: Measurement, analysis, and implications". paper
- Paolo Viotti, Marko Vukolic, "Consistency in Non-transactional Distributed Storage Systems". paper
- Stephen Asbury, "Eight fallacies of distributed computing". video
- Nickolas Means, "Who destroyed Three Mile Island?". video
- Foone Turing, "The Normalization of Deviance". blog twitter
- John Allspaw, "Poised to adapt: Continuous Delivery's relationship to Resilience Engineering". video
- John Allspaw, "How your systems keep running day after day". article
- Christian Witts, "The CAP Theorem of Humans". slides