ACID Properties: Correctness Through Coordination
Performance Cost of Coordination
ACID requires coordination before confirming writes. A typical setup writes to a distributed log, waiting for a quorum (majority) to acknowledge. This adds one network round-trip plus disk flush: 10-20ms median, 20-40ms P99 (99th percentile). Cross-region ACID uses two-phase commit (coordinator asks all to prepare, commits if all agree), pushing latencies to 100-200ms.
Availability Trade-off
ACID systems become unavailable during partitions if they cannot reach quorum. When the primary fails, a new one must be elected, blocking writes for 10-30s. This is acceptable when correctness is non-negotiable: money transfers, inventory at checkout, ledgers, entitlements.
Practical Boundaries
Use ACID within boundaries where coordination is cheap (single region, single shard) and relax guarantees across boundaries. Single-shard transactions stay fast (10-40ms); cross-shard either uses distributed transactions (slower) or eventual consistency patterns.