🔒 Paid
Checkout, Payment & Inventory Redis Contention
Checkout traffic looks completely healthy. Payment retries are climbing. Inventory's p95 latency is climbing. These look like two unrelated problems in two unrelated services — until you notice Payment and Inventory both depend on the same Redis instance. Redis CPU and memory look fine; its connection pool does not. Diagnose the shared dependency and restore both services without chasing either symptom in isolation.
- Difficulty
- Staff
- Expected Time
- ~18 min
- Category
- Distributed Systems
Skills
- Distinguishing independent symptoms from a shared root cause
- Reading connection-pool saturation vs. CPU/memory as different signals
- Recognizing a plausible-but-inferior single-service remediation
- Verifying recovery across every dependent service, not just one
System Architecture
- Checkout API
- Payment API
- Inventory API
- Redis
This is a Pro scenario. Upgrade to Pro to unlock it.
Upgrade to ProBack to Incidents