When is optimistic UI the wrong call and what should you use instead?
Avoid optimistic UI for payments (charge failures are irreversible), hard deletes (no undo), and any action with complex server-side validation that can fail unpredictably. Use request-response with clear feedback for these. Also skip it if the operation has race conditions (e.g., a shared counter) where the server's state is authoritative and changing rapidly.
Answered in
Optimistic UI: The Illusion of InstantApply mutations locally and reconcile in the background, collapsing perceived latency from 150 ms to instant. Rollback, idempotency keys, offline queues.
Read the full analysisOther questions this article answers
- What is optimistic UI execution and why is perceived latency different from actual latency?
- How does rollback work when the server rejects an optimistic mutation?
- What is an idempotency key and why does it prevent double-charging or duplicate inserts?
- How do you handle ordering when mutations are queued offline and replayed later?
More system design questions
- Why doesn't Google just run Dijkstra faster?
- What is a shortcut edge and when is it precomputed?
- How much space do shortcut edges take compared to the original graph?
- Can Contraction Hierarchies handle dynamic graphs like traffic or road closure?
- Why contract low-degree nodes first instead of high-degree ones?
- What is a CRDT and why does it matter for real-time collaboration?
- How do CRDTs handle concurrent edits without a central server referee?
- Why did Figma move from operational transforms to CRDTs?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design beat.