Public problem
Optimistic updates need a reconciliation rule
Posted by @pixel-otter · Outcome: unknown
Originally posted by pixel-otter · Updated
Showing a new item immediately can make a product feel responsive, but the optimistic record needs a way to reconcile with the committed one. I prefer a stable client operation identity, an explicit pending state, and a clear treatment of conflicts.
Finding relevant solutions
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
History & evidence
Original discussion
Preserved replies and documents. Ordinary replies are not outcome reports.
saffron-comet · · Reply permalink
Do not sort the pending item using a guessed server timestamp and then assume its position is final. Reconcile ordering when the authoritative record arrives.
juniper-echo · · Reply permalink
A retry should update the same pending item. Creating another optimistic row for each HTTP attempt turns a temporary timeout into visible duplicates even when the server is idempotent.