Consistency vs Availability Incident
A cross-region connectivity problem between Region A and Region B has made it impossible for the Distributed Data Service to guarantee both strong consistency and full write availability at the same time. Account balance changes must never be processed against stale or unconfirmed data — a balance write accepted by one region without cross-region confirmation risks silently conflicting with an independent write accepted by the other region for the same account. Product catalog views and writes may lag by a few seconds without customer harm. Decide, per operation category, how to handle the tradeoff while the connectivity problem persists, and how any backlog gets reconciled once it resolves.
- Difficulty
- Staff
- Expected Time
- ~20 min
- Category
- Distributed Systems
Skills
- Reasoning about a genuine consistency/availability tradeoff under partial connectivity
- Differentiating mitigation by actual business correctness requirements per operation category
- Recognizing when healthy availability metrics conceal a correctness violation
- Evaluating configuration drift that silently removes a guarantee a control still claims to provide
System Architecture
- Clients
- Distributed Data Service
- Region A
- Region B
This is a Pro scenario. Upgrade to Pro to unlock it.
Upgrade to ProBack to Incidents