🔒 Paid
Duplicate Event Processing
Consumer acknowledgements to the broker are failing intermittently, and unacknowledged messages are being redelivered. Order and payment processing must remain idempotent — an order or payment side effect applying more than once for the same underlying event is a critical integrity incident, not a cosmetic one, regardless of how healthy throughput and acknowledgement metrics otherwise look. Diagnose why redelivery is occurring and bring the system to a state that is genuinely safe to hand back, not merely fast.
- Difficulty
- Staff
- Expected Time
- ~20 min
- Category
- Messaging & Streaming
Skills
- Distinguishing availability metrics from correctness guarantees
- Recognizing when a mitigation improves throughput without addressing duplication
- Reasoning about acknowledgement timing and redelivery amplification
- Evaluating idempotent processing and deduplication-window tradeoffs
System Architecture
- Producer
- Broker
- Consumers
- Payment/Order Side Effects
This is a Pro scenario. Upgrade to Pro to unlock it.
Upgrade to ProBack to Incidents