@@ -32,27 +32,27 @@ Here is a map of the designs from this tutorial against the consistency-availabi
3232
3333```
3434CONSISTENCY
35- strong ▲ Step 4: conservative coordination
36- │ Strong consistency; may wait forever if an upstream node stops.
37- │
38- │ Step 5 slow path: curtailments
39- │ Same strong-consistency path as Step 4 for high-risk commands.
40- │
41- │ Step 3: finite maxwait
42- │ Strong consistency only while apparent latency <= maxwait;
43- │ otherwise the tardy handler is part of the design.
44- │
45- eventual│ Step 5 fast path: dispatch-up
46- │ Fast response with later reconciliation.
47- │
48- │ Step 1: commutative actor
49- │ Eventual consistency and maximum availability.
50- │
51- none │ Step 2: non-commutative actor
52- │ High availability, but possible permanent divergence.
53- │
54- └────────────────────────────────────────────────────────► AVAILABILITY
55- low / may block high / responds fast
35+ strong ▲ Step 4: conservative coordination
36+ │ Strong consistency; may wait forever if an upstream node stops.
37+ │
38+ │ Step 5 slow path: curtailments
39+ │ Same strong-consistency path as Step 4 for high-risk commands.
40+ │
41+ │ Step 3: finite maxwait
42+ │ Strong consistency only while apparent latency <= maxwait;
43+ │ otherwise the tardy handler is part of the design.
44+ │
45+ eventual │ Step 5 fast path: dispatch-up
46+ │ Fast response with later reconciliation.
47+ │
48+ │ Step 1: commutative actor
49+ │ Eventual consistency and maximum availability.
50+ │
51+ none │ Step 2: non-commutative actor
52+ │ High availability, but possible permanent divergence.
53+ │
54+ └────────────────────────────────────────────────────────► AVAILABILITY
55+ low / may block high / responds fast
5656```
5757
5858---
0 commit comments