$ recombobulate _
home / tips / set-up-background-job-processing-with-bullmq-using-claude
38

Set Up Background Job Processing with BullMQ Using Claude

recombobulate @recombobulate · Mar 26, 2026 · Workflows
set-up-background-job-processing-with-bullmq-using-claude

BullMQ is the go-to for Redis-backed job queues in Node.js, but setting up workers, retry logic, and job scheduling has a lot of boilerplate. Claude handles all of it.

Set up BullMQ with a job queue for sending emails. Include a
producer that adds jobs, a worker that processes them with retry
logic (3 attempts, exponential backoff), and a dashboard route
using bull-board. Use TypeScript.

Claude generates the full setup — queue definition, worker, and producer:

// queues/email.queue.ts
import { Queue, Worker } from 'bullmq';
import { connection } from './redis';

export const emailQueue = new Queue('email', { connection });

const worker = new Worker('email', async (job) => {
  await sendEmail(job.data.to, job.data.subject, job.data.body);
}, {
  connection,
  limiter: { max: 10, duration: 1000 },
  attempts: 3,
  backoff: { type: 'exponential', delay: 2000 },
});

Need more advanced patterns? Ask for them:

Add a scheduled job that runs every hour to clean up expired
sessions. Add a priority queue so password reset emails always
process before marketing emails. Include dead letter queue
handling for permanently failed jobs.

Claude also wires up the monitoring dashboard so you can inspect queued, active, and failed jobs in your browser.

Background jobs done right from the start — Claude scaffolds the queues, workers, and monitoring so you skip the trial-and-error setup.

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Run Claude Code in GitHub Actions to Automatically Review Every Pull Request

Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Build a Deployment Checklist from Your Actual Infrastructure

Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Generate a README from Your Actual Codebase — Not a Template

Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.

recombobulate @recombobulate · 1 month ago