When to Choose Strong Consistency
You'll learn: When your system absolutely needs strong consistency guarantees and why some use cases cannot tolerate stale or conflicting data.
The Core Idea
Strong consistency isn't free—it costs latency, throughput, and availability during partitions. But for certain applications, correctness is non-negotiable. When data races or stale reads could cause financial loss, legal liability, or catastrophic failures, you must prioritize strong consistency over speed.
Critical Use Cases
Banking and Financial Systems
Every account balance update must be immediately visible. Two concurrent withdrawals must never overdraw an account. Strong consistency prevents double-spending, ensures accurate balances, and maintains trust in financial operations.
Inventory Management
When you have 3 items left, selling 4 would be disastrous. Strong consistency guarantees that once inventory hits zero, no further sales complete. This prevents overselling, angry customers, and fulfillment nightmares.
Booking Systems
Airline seats, hotel rooms, concert tickets—these cannot be double-booked. Strong consistency ensures that when a seat is reserved, it's immediately unavailable to everyone else. Two users clicking "book" simultaneously will see one succeed and one fail, never both succeed.
Critical Metadata
Configuration data, access control lists, and schema definitions often require strong consistency. If a user's permissions are revoked, that change must propagate immediately—not eventually—to prevent security breaches.
The Decision Pattern
Choose strong consistency when:
- Correctness matters more than speed
- Conflicts would cause real-world harm (financial, legal, safety)
- Users expect immediate confirmation of state changes
- Regulatory compliance demands it
Key Takeaway: Strong consistency is essential when data conflicts have real consequences—money lost, items oversold, or security breached. Pay the performance cost when correctness cannot be compromised.