What problem does it solve? Setting up background job processing with BullMQ involves non-obvious production pitfalls: shared Redis connections cause deadlocks, default worker concurrency of 1 bottlenecks throughput, and failed jobs vanish without a dead letter queue. This Skill guides you through designing isolated, correctly sized, failure-safe queue systems. ## Core Features & Use Cases - Queue Architecture: One queue per job type with separate ioredis connections for Queue, Worker, and QueueEvents roles. - Worker Sizing & Rate Limiting: Concurrency formula based on provider rate limits and job duration, plus BullMQ limiter configuration for external APIs. - Failure Handling: Exponential backoff retries, dead letter queues with replay, job flows for dependent tasks, cron scheduling with stable job IDs, and graceful shutdown. - Monitoring: Bull Board dashboard integration with Fastify and authentication middleware. - Use Case: You need to send transactional emails, generate PDFs, and call LLM APIs in the background. This Skill produces three isolated queues with provider-aware rate limits, a DLQ for exhausted retries, and a Bull Board UI at /admin/queues. ## Quick Start Ask the AI to set up a BullMQ background job architecture for your task, for example: set up BullMQ queues with workers, retries, and a dead letter queue for email dispatch and PDF generation.
