echd — Echo on Encore · E0.3

The Strategy Catalogue

Four ways to cope with the impossibility — each with a named system that proved it in production, each with the platform tier that buys it here.

Vision · real substrate

echd speaks in the present tense over a build ladder. Every module, verb, key, and port named on this page is real; the composition into one standing platform is the vision the ladder builds.

§1

The module

echd.course.md §4 — the contributors

The paper's §4 is a catalogue of survivors — systems that shipped anyway, each coping with the theorem a different way, and the platform of this course names its debt to each. Best-effort availability guarantees consistency and optimizes responsiveness: Chubby, the lock service at the heart of Google's infrastructure, runs a Paxos-replicated database inside one datacenter — correct always, unavailable only when the cluster splits. Best-effort consistency guarantees the answer and bounds the freshness: the web caching tier pioneered by Akamai serves close to the reader, tolerating a slightly stale page because a stopped one is worse. Trading the trade makes the tolerance a number: Yu and Vahdat's TACT toolkit meters conits — units of continuous consistency — so an airline can loosen the bound while the plane is empty and tighten it seat by seat.

And segmenting — the strategy that shapes this platform — splits one system into parts that each choose differently, along five dimensions the paper walks with named exemplars: data (the shopping cart loose, the billing record strict), operation (PNUTS serving reads always while some writes wait), function (Chubby for locks beside DNS for names), user (Craigslist splitting coasts so each side stays close and coherent), and hierarchy (looser toward the root, tighter toward the leaves). The whole guarantees neither property; every part guarantees exactly what it owes. That sentence is this platform's blueprint — the tiers of E3–E6 are its five dimensions, cashed.

§2

The catalogue

hover a strategy

Four copings, four contributors · the paper's survivors and the platform's tiers · hover to read

Chubby's seat — correctness regardless of the network. A Paxos-replicated database behind a lock-service face, deployed one cell per datacenter, read-optimized around a stable primary: strongly consistent always, unavailable only under a split. The platform buys this seat where money and identity live — one transaction at the ledger, the gate at every seam.

Akamai's seat — the answer, always. Content cached across the world, served close to the reader; an update propagates when it propagates, and a slightly stale page beats a blank one. The platform buys this seat for reads and telemetry: the memory answers from L1, the bus retains and replays, the surface serves last-known — each stamping what it served.

TACT's seat — consistency as a quantity. Conits meter how far a replica may drift — numeric error, order error, staleness — and the application moves the bound at runtime: generous while the plane is empty, strict as it fills. The platform's dial is the framed version<>value and the as_of stamp: the drift is always visible, so the bound is always honest.

The platform's seat — segment, then join. PNUTS answers reads always while some writes wait; DNS names loosely beside Chubby locking strictly; Craigslist splits its coasts so each is close and coherent. Five dimensions, one lesson: choose per part, not per system. What the paper leaves open — how the parts stay ONE system — this platform answers with the branded seam of E2.

Hover or focus a strategy to read it; click to pin. Without scripting, all four read in sequence.

§3

The dives

three moves down

← Back to modules

§4

Doors

the deeper argument

/echd/best-effort-consistency

Best-effort consistency, at length

The lineage page holding the availability-first stance this module compresses to one row.

folds into this module — served beside it until the dives ship.

/redis-patterns

Redis Patterns, Applied

The pattern-level craft under the availability-first seats — caching, queues, streams.

the same seats, bought pattern by pattern in the sibling course.

§5

References

sources · related

Sources

Gilbert & Lynch (2012) — Perspectives on the CAP Theorem§4 — the catalogue and every contributor this module names
Burrows (2006) — The Chubby lock servicethe best-effort-availability contributor, at its source

E0 — The Platform, Standingthe chapter
E0.4 — One Frame, Standingthe catalogue, placed on the master frame
E4 — The Memorythe dial, held in one table