From 5b2ffd6cd6698a3fa2f03b881446200e14dfef22 Mon Sep 17 00:00:00 2001 From: Sanket Patil Date: Mon, 4 Oct 2021 21:39:54 +0530 Subject: [PATCH] added some more resources for 'cap' and consistency models --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 266f8b16..85d91f51 100644 --- a/README.md +++ b/README.md @@ -469,6 +469,7 @@ AP is a good choice if the business needs allow for [eventual consistency](#even * [A plain english introduction to CAP theorem](http://ksat.me/a-plain-english-introduction-to-cap-theorem) * [CAP FAQ](https://github.com/henryr/cap-faq) * [The CAP theorem](https://www.youtube.com/watch?v=k-Yaq8AHlFA) +* [Why you should not call databases CP or AP](https://martin.kleppmann.com/2015/05/11/please-stop-calling-databases-cp-or-ap.html) ## Consistency patterns @@ -495,6 +496,7 @@ This approach is seen in file systems and RDBMSes. Strong consistency works wel ### Source(s) and further reading * [Transactions across data centers](http://snarfed.org/transactions_across_datacenters_io.html) +* [Additional consistency models](https://xzhu0027.gitbook.io/blog/misc/index/consistency-models-in-distributed-system) ## Availability patterns