🔒 Paid
Event Processing Backpressure
Upstream event producers have surged well past the processing layer's normal drain capacity, and Kafka consumer lag is climbing along with how stale events are by the time they're processed. The database connection pool and the external API's call budget are both shared with other production traffic, and the external API enforces its own rate limits — exceeding them degrades the dependency for longer than the surge itself lasts. Diagnose why the backlog is growing and bring ingestion, processing, and both downstream dependencies back into a durable, sustainable balance.
- Difficulty
- Staff
- Expected Time
- ~20 min
- Category
- Messaging & Streaming
Skills
- Diagnosing producer/consumer throughput mismatches
- Recognizing when a mitigation transfers pressure to a different subsystem
- Balancing ingestion, processing concurrency, and downstream dependency capacity
- Evaluating priority-based tradeoffs under sustained backpressure
System Architecture
- Event Producers
- Kafka
- Processing Layer
- Database
- External API
This is a Pro scenario. Upgrade to Pro to unlock it.
Upgrade to ProBack to Incidents