Three Strategies, Three Outcomes

Three Strategies, Three Outcomes A data-flow diagram generated by Archify. 01 / Offline edits 02 / Sync input 03 / Resolution 04 / Merged cart Sync input · adds + removes · 02 / Sync input · merge point Sync input adds + removes merge point Last-write-wins · newest cart wins · 03 / Resolution · loses updates Last-write-wins newest cart wins loses updates Sibling union · keep both · 03 / Resolution · manual merge Sibling union keep both manual merge OR-Set · tags + tombstones · 03 / Resolution · convergent OR-Set tags + tombstones convergent Device A offline · removes milk, saw t1 · 01 / Offline edits · observed Device A offline removes milk, saw t1 observed Device B offline · removes bread, saw t2 · 01 / Offline edits · observed Device B offline removes bread, saw t2 observed Device B fresh add · adds milk@t3 unseen · 01 / Offline edits · concurrent Device B fresh add adds milk@t3 unseen concurrent LWW result · one cart wins · 04 / Merged cart · loses updates LWW result one cart wins loses updates Sibling result · both carts kept · 04 / Merged cart · manual merge Sibling result both carts kept manual merge OR-Set result · empty + t3 rule · 04 / Merged cart · convergent OR-Set result empty + t3 rule convergent both carts both carts adds + removes remove milk@t1 remove bread@t2 add milk@t3 winner kept merged Legend primary data policy / PII async batch data store data flow