# Overview An approach for handling a write-write conflict where the 'winning' write is just the one determined to be the 'latest' write. # Key Considerations # Pros # Cons - Can cause data loss, because it is not a reliable method for various reasons: - A node with a lagging clock will always lose to a node with a fast clock. The real latest data will get overwritten without warning. - Cannot distinguish between writes that occurred sequentially in quick succession with the support of a [[Vector Clock]]. # Use Cases # Related Topics