mirrors/system-design-primer
1
0
Fork 0
mirror of https://github.com/donnemartin/system-design-primer.git synced 2025-11-04 02:02:31 +03:00
Code Issues Projects Releases Wiki Activity

Fix broken CAP theorem link #1160 (#1161)

Browse Source
This commit is contained in:
Pranjit Medhi
2025-11-01 08:37:55 +05:30
committed by GitHub
parent 683bdb1678
commit 594a11a71c
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -442,7 +442,7 @@ Generally, you should aim for **maximal throughput** with **acceptable latency**
<p align="center"> <p align="center">
<img src="images/bgLMI2u.png"> <img src="images/bgLMI2u.png">
<br/> <br/>
<i><a href=http://robertgreiner.com/2014/08/cap-theorem-revisited>Source: CAP theorem revisited</a></i> <i><a href="https://robertgreiner.com/cap-theorem-revisited">Source: CAP theorem revisited</a></i>
</p> </p>
In a distributed computer system, you can only support two of the following guarantees: In a distributed computer system, you can only support two of the following guarantees:
@@ -465,7 +465,7 @@ AP is a good choice if the business needs to allow for [eventual consistency](#e
### Source(s) and further reading ### Source(s) and further reading
* [CAP theorem revisited](http://robertgreiner.com/2014/08/cap-theorem-revisited/) * [CAP theorem revisited](https://robertgreiner.com/cap-theorem-revisited/))
* [A plain english introduction to CAP theorem](http://ksat.me/a-plain-english-introduction-to-cap-theorem) * [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) * [CAP FAQ](https://github.com/henryr/cap-faq)
* [The CAP theorem](https://www.youtube.com/watch?v=k-Yaq8AHlFA) * [The CAP theorem](https://www.youtube.com/watch?v=k-Yaq8AHlFA)