Last-Write-Wins vs Merging: Resolving Conflicting Writes

Sun, 06 Sep 2026 09:50:29 +0900

Overview

When two replicas accept concurrent writes to the same key, a system must reconcile them. Last-Write-Wins picks a single winner by timestamp and discards the rest, while Merging combines both writes into a new value using domain-specific or CRDT logic.

Comparison Diagram

Comparison Table

Aspect	Last-Write-Wins	Merging
Conflict trigger	Fires when two writes to the same key arrive with overlapping validity, regardless of content	Fires the same way, but treats both writes as valid inputs rather than competitors
Resolution mechanism	Compares timestamps (or version numbers) and keeps the highest one	Applies a merge function, CRDT join, or three-way diff to combine both values
Data/metadata required	A reliable clock or monotonic counter per write	Version vectors, causal history, or a semantically defined merge operation
Application involvement	None — resolution is automatic and content-agnostic	Requires the app or data structure to define what ‘combining’ means
Outcome for the losing write	Discarded entirely, no trace remains	Incorporated into the final merged state, nothing is dropped
Consistency guarantee	Deterministic convergence, but the winner may be arbitrary relative to causality	Deterministic convergence that also respects the semantics of both updates
Performance overhead	Minimal — a single comparison per conflict	Higher — merge logic, extra metadata, and sometimes multi-way comparisons
Failure mode	Silent data loss under clock skew or concurrent writes at the same timestamp	Unresolvable merge conflicts that surface to the application or user

Key Differences

LWW resolves conflicts purely by comparing timestamps, keeping only one write.
Merging combines concurrent writes using a merge function or CRDT join instead of picking a single winner.
LWW can cause silent data loss when clocks skew or writes race within the same tick.
Merging needs semantic knowledge of the data type to combine values correctly.
LWW adds negligible overhead per write; merging trades that simplicity for correctness under concurrency.

When to Use Each

Last-Write-Wins

Conflict-Resolution on IT Comparison

Last-Write-Wins vs Merging: Resolving Conflicting Writes

Overview

Comparison Diagram

Comparison Table

Key Differences

When to Use Each