Eventually Consistent

Vogels, Amazon's CTO, wrote this essay to explain why eventual consistency is not a compromise or a bug but a deliberate architectural choice driven by the realities of operating at planetary scale. He walks through the spectrum of consistency models — from strong consistency through session consistency to eventual consistency — showing that each reflects a different set of assumptions about latency, availability, and user expectations. The essay emerged directly from Amazon's experience building Dynamo and operating services where milliseconds of additional latency translated into measurable revenue loss. Vogels made the case that for many real-world applications, the guarantee that all nodes will converge to the same state given enough time is not only sufficient but preferable to the alternative of blocking until global agreement is reached. It is one of the clearest bridges between distributed systems theory and the operational reality of running internet-scale infrastructure.