🔒 Paid
Cascading Service Failure
Checkout Service and Order Service have both started reporting degraded health, and the on-call dashboard is lighting up across multiple teams at once. Request queues are growing throughout the chain and checkout success is dropping. Before you scale or restart anything, find out which service is actually broken and which ones are just waiting on it.
- Difficulty
- Staff
- Expected Time
- ~18 min
- Category
- Distributed Systems
Skills
- Distinguishing root cause from cascading symptoms
- Scoping circuit breakers to the actual point of failure
- Recognizing when a mitigation wastes effort on a healthy service
- Backpressure and load-shedding tradeoffs
System Architecture
- API Gateway
- Checkout Service
- Order Service
- User Profile Service
- Profile Database
This is a Pro scenario. Upgrade to Pro to unlock it.
Upgrade to ProBack to Incidents