Module 1 · Dive 1.3
Two axes, one decision.
The shootout measured one thing — the loss window. A second axis is independent of it: does the durable state ever leave the machine? A tier can be strict but single-node, or bounded but replicated. Placing a queue means choosing both. Drop a workload below and see the corner it needs.
The durability–replication plane
interactiveThe corner the course reaches
graft.design.mdThe plane makes the design’s target precise. Oban owns the bottom-right — strict, but single-node; Champ’s async snapshot reaches off-box but only at a bounded loss, upper-left. The corner no single engine holds is top-right: strict and off-box. Echo Persistence reaches it by composition — Champ accepts (left axis handled by K), Graft commits transactionally and replicates to Tigris (the move up the right edge) — which is why “Champ + Graft” sits where it does. The next chapters build each half; this is the corner they aim at.
References & sources
- Echo records
- graft.design.mdthe two axes and the target corner
- graft.engine-split.design.mdreplication as a distinct concern
- External
- Tigris object conditionalsthe off-box, fenced commit
- Designing Data-Intensive Applications, Kleppmann 2017replication and durability as separate guarantees (Ch. 5)