skill-queue-bullmq

To set up a BullMQ queue, configure a shared Redis connection instance and use it to initialize your queue. This shared connection allows multiple workers and job types to interact efficiently without exhausting Redis resources.

BullMQ job retries are configured by defining backoff policies and retry attempts during job creation. This ensures failed background jobs are automatically re-queued with a specified delay, improving overall processing reliability.

Worker orchestration and job progress monitoring in BullMQ are managed by defining worker processes that listen to specific queues and track job states. This provides visibility into background processing and scheduled tasks across services.

Yes, you need a Redis instance to run BullMQ because it relies on Redis-backed systems for queueing. Configuring a shared BullMQ connection to this Redis instance is required to handle job scheduling and worker orchestration.

BullMQ cleanup policies like removeOnComplete and removeOnFail are configured directly within your job options. Setting these flags automatically deletes successful or failed jobs from Redis, preventing memory bloat and managing queue size.

Use BullMQ for background processing when you need robust retry strategies, scheduled tasks, and cross-service job monitoring. It provides reliable orchestration that standard in-memory async tasks cannot persist across application restarts.