🔒 Paid
API Traffic Spike
A legitimate, non-malicious surge in customer traffic is underway. Request volume has already roughly quintupled over its normal baseline, and the new traffic mix is hitting a wider, colder set of cache keys than the platform is used to serving. Core checkout and account flows depend on the database staying responsive, and the connection pool is shared across every customer-facing request path — if it saturates, everything downstream suffers together. A separate, non-critical reporting endpoint also shares this same database and cache. Diagnose what is actually running out of headroom as traffic climbs, and bring the platform back to a durable, sustainable state.
- Difficulty
- Senior
- Expected Time
- ~15 min
- Category
- API & Traffic
Skills
- Distinguishing API-tier capacity from downstream database/cache constraints
- Reasoning about cache hit-rate collapse under a changed traffic pattern
- Recognizing when scaling the wrong tier makes contention worse
- Evaluating load-shedding tradeoffs (rate limiting, feature suppression) against root-cause fixes
System Architecture
- Clients
- Load Balancer
- API Fleet
- Database
- Cache
This is a Pro scenario. Upgrade to Pro to unlock it.
Upgrade to ProBack to Incidents