Consistency Choices at a Glance
Recall decision cues for strong, eventual, and session-level consistency choices.
Strong vs Eventual Strong Use when a stale answer can violate an invariant or cause a duplicate irreversible action. Eventual Use when stale data is acceptable within a named window and the UI or workflow tolerates it. Objection: Strong everywhere If stale data is confusing, why not make every read strongly consistent? Reply Spend coordination on trust moments and invariants; use bounded lag for lower-risk derived views. Blanket strong reads can add cost, latency, or availability trade-offs without improving the user promise. It ties consistency to risk instead of treating it as a universal quality setting. What question reveals read-your-own-write…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in