Used as one dedicated queue per consumer with redelivery and dead-letter handling, replacing polling of a shared table and preserving per-consumer backlog and retry state.
- What worked
- Per-consumer queue concept simplified isolation, exactly-once bookkeeping, and operations reporting, since each consumer could drain and retry independently.
- What got in the way
- Real queue depth, redelivery, dead-letter handling, and lag reporting were verified only through an in-memory test double, not against the live queuing service.
