Node.js + BullMQ

Node + BullMQ for job queues.

BackendModerate

Stack Components

RuntimeNode 22

QueueBullMQ 5

DBRedis 7

FrameworkExpress 5

Why

Redis-backed, retries, scheduling, flows. Node.js, Go, and Python are the top 3 backend languages (Stack Overflow 2024).

Go's goroutines handle 100k+ concurrent connections per process; Node's event loop excels at I/O-bound workloads.

When

Use for background jobs. Avoid for simple setTimeout.

How

1. npm i bullmq ioredis 2. Create Queue and Worker 3. Add jobs 4. worker.run() 5. Add environment configuration — cp .env.example .env && edit values 6. Run tests — npm test or pnpm test to verify setup 7. Deploy — git push to trigger CI/CD or manual deploy

Example

const queue = new Queue('email') const worker = new Worker('email', async job => sendEmail(job.data)) queue.add('send', { to: '[email protected]' })

Common Problems

⚠Redis connection — use maxRetriesPerRequest: null
⚠Job priority — use priority option
⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

✓Use QueueScheduler for retries
✓Leverage flows for job dependencies
✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is Node.js + BullMQ and what projects is it for?

Node + BullMQ for job queues. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.

How do I spin up a working demo with Node.js + BullMQ in 10 minutes?

Two steps: (1) npm i bullmq ioredis; (2) Create Queue and Worker. Get the local dev server running, then wire one real data source to verify the end-to-end loop.

What is the most common pitfall with Node.js + BullMQ and how do I avoid it?

The most common pitfall is: Redis connection — use maxRetriesPerRequest: null. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.

What are the best practices for Node.js + BullMQ?

Best practices for Node.js + BullMQ include: Use QueueScheduler for retries; Leverage flows for job dependencies; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use QueueScheduler for retries" — should be set up at project init to avoid costly rework later.

When should I NOT choose Node.js + BullMQ?

Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). Node.js + BullMQ shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.