conflict-detection-varies-by-consistency-model

Status: IN

Three systems use distinct conflict detection strategies — sibling retention (KV), per-device version vectors (GDrive), and per-date version counters (hotel) — each matched to the system's merge semantics and consistency requirements.

Justifications

conflict detection strategy correlates with data model — multi-writer replication retains all versions, collaborative editing uses device vectors, single-resource booking uses counters

Depends on (SL): kv-node-stores-sibling-versions, gdrive-version-vector-conflict, hotel-reservation-optimistic-locking

Depended on by

JSON