added some more resources for 'cap' and consistency models

pull/584/head
Sanket Patil 2021-10-04 21:39:54 +05:30
parent 4e70c54a5b
commit 5b2ffd6cd6
1 changed files with 2 additions and 0 deletions

View File

@ -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