From 594a11a71ca0dfeced11b253675618dea708461a Mon Sep 17 00:00:00 2001 From: Pranjit Medhi Date: Sat, 1 Nov 2025 08:37:55 +0530 Subject: [PATCH] Fix broken CAP theorem link #1160 (#1161) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index cedbdfcb..f9529b3e 100644 --- a/README.md +++ b/README.md @@ -442,7 +442,7 @@ Generally, you should aim for **maximal throughput** with **acceptable latency**


- Source: CAP theorem revisited + Source: CAP theorem revisited

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 -* [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) * [CAP FAQ](https://github.com/henryr/cap-faq) * [The CAP theorem](https://www.youtube.com/watch?v=k-Yaq8AHlFA)