Go E-Commerce Failed Job Retry: DLQ Redrive vs Database Polling Queues
go
dev.to
A failed job retry in a rate-limited worker pool needs a DLQ and bounded redrive; otherwise recovery traffic can become the next incident. Short answer: for a small e-commerce app, use a queue with a dead-letter queue (DLQ) and controlled redrive for failed job retry; keep durable attempt history in the application database, and reserve database polling for deliberately small maintenance workloads. This split gives operators an explicit place for poison messages, while the database remains the