project
Redis-backed job and message queue library for Node.js, used here with attempts, backoff strategies, queue events, and dead-letter routing.
No evidence-backed relationships are recorded.
Monest's CTO kept tag-event fan-out on BullMQ, where each job goes to one worker, for two client integrations and several internal teams. A first attempt, one worker calling every consumer, replayed finished calls on retry and forced one retry count on all of them.
Reality
Three separate IDs and one Postgres row per retry let an investigator list every attempt for a tenant in order, according to a dev.to design. Adopting it means carrying an operation ID into every enqueue call, and its sample redactor lets bearer tokens through.
Reality
A dev.to walkthrough puts the hard part of background job retries in recovery semantics. The test it sets is whether a restarted worker can tell finished work from work it merely fetched. The queue's own limits are narrow.
Reality
Gate of AI's Node tutorial validates the webhook, writes the row, enqueues the job and answers 202 before a single token is generated. The parts worth keeping are the unique idempotency key and the Zod parse on the reply.
Reality
A dev.to walkthrough on NestJS and BullMQ starts where demos stop: retries with jitter, idempotency keys, and jobs that look done but are stuck.
Reality