Conflict resolution: when two writes collide
The offline cart and the lost update, five resolution strategies, why last-write-wins loses data under clock skew, vector clocks and siblings, CRDTs from G-Counters to OR-Sets and text, replicating CRDT state, choosing a strategy per field, conflict detection, tombstone garbage collection, and an offline notes interview.
01 · Previously
W05 · DAY 04 · Conflict Resolution
What orchestration can't fix.
Previously: durable workflows
Previously, on Day 3, you made sagas durable: workflows that replay from history, activities that retry, signals that wait for days.
0:00 / 19:19