What is eventual consistency?
Understand the concept
Eventual consistency allows copies or derived views to differ temporarily while updates propagate. If no new changes occur and processing succeeds, those views converge. This is useful when a delay is acceptable, but the product must define what users see during that delay and how failed propagation is repaired.
Important ideas
-
Different copies may temporarily show different data.
-
Without new writes, they converge after pending updates are applied.
-
Suitable for some feeds or analytics; current stock or order allocation may need stronger guarantees.
-
Examples include a report updating after an order is accepted, or a search index catching up with a profile change.
Can you explain it without the notes?
What is eventual consistency?
Use your own words. Explain an example and one limitation before checking the explanation.
Check your explanation
Eventual consistency allows copies or derived views to differ temporarily while updates propagate. If no new changes occur and processing succeeds, those views converge. This is useful when a delay is acceptable, but the product must define what users see during that delay and how failed propagation is repaired.
Turn this concept into a clear answer.
- Name the permitted delay and reconciliation mechanism; “eventually” without an operational bound is not a complete plan.
Adapted from 07_SYSTEM_DESIGN_ARCHITECTURE.md · “What is eventual consistency?”. Examples are study fragments; framework behavior can depend on your version.