Best Background Jobs & Queue Tools
Async tasks, schedules, and durable workflows. Ranked by which tools AI agents actually pick when developers build — measured live across Claude, GPT, Gemini.
As of Jun 24, 2026, the job queue AI agents pick most is BullMQ at 17%, measured across Claude, GPT, Gemini.
| # | Tool | Pick Rate | Default Rate | Shortlist |
|---|---|---|---|---|
| 1 | BullMQ | 17% [12%–24%] | 27% | 27% |
| 2 | Temporal | 5% [2%–10%] | 0% | 12% |
| 3 | Inngest | 2% [1%–5%] | 0% | 7% |
| 4 | Trigger.dev | 0% [0%–3%] | 0% | 6% |
| 5 | Graphile Worker | 0% [0%–3%] | 0% | 5% |
What is a background job queue?
A background job system runs work off the request path — sending emails, processing webhooks, calling AI models, scheduled tasks — with retries and durability so jobs survive failures. Options range from Redis-backed queues to durable workflow engines to serverless, event-driven platforms.
Any real app needs async work, and doing it inline blocks requests and loses work on crashes. Serverless broke the old long-running-worker model, spawning a new wave of dev-first tools — so the choice is now as much about your runtime as your throughput.
How to choose
What separates the Background Jobs & Queues options.
A persistent worker process suits servers; serverless apps need an event-driven or hosted runner.
Multi-step, long-running workflows with state need a workflow engine, not just a queue.
Redis-backed queues are simple; managed platforms remove the infrastructure entirely.
Local dev, observability, and retry ergonomics decide day-to-day pain.
Best job queue for your use case
| If you need… | Reach for | Why |
|---|---|---|
| Best serverless / dev-first | Inngest / Trigger.dev | Event-driven and long-running jobs without managing a worker. |
| Redis-backed queue | BullMQ | The standard Node queue when you already run Redis. |
| Mission-critical durable workflows | Temporal | Battle-tested durable execution for complex, long-running workflows. |
| Postgres-backed jobs | Graphile Worker | A job queue that runs on the Postgres you already have. |
Background Jobs & Queues: incumbents vs new entrants
The space spans the Redis-queue standard, a durable-workflow heavyweight, and a fast-rising wave of serverless, dev-first job platforms.
Serverless, event-driven jobs and workflows; strong DX.
Long-running background jobs with great developer experience.
A lightweight job queue backed by Postgres.
Why AI agents decide this category
Ask an agent to 'run background jobs' and the answer depends on context it may or may not have — BullMQ if Redis is around, a serverless platform if not. Whichever it scaffolds gets woven through the app's critical async paths, so the default compounds quickly.
Frequently asked questions
What is a background job queue?
It runs work asynchronously off the request path — emails, webhooks, scheduled tasks — with retries and durability so jobs survive failures. Some are simple queues; others are durable workflow engines.
What is the best background job tool for Node.js?
BullMQ if you run Redis, Inngest or Trigger.dev for serverless/dev-first, Temporal for mission-critical durable workflows. The ranking above shows which AI agents pick.
Inngest vs Trigger.dev vs BullMQ?
BullMQ is a Redis-backed queue you host; Inngest and Trigger.dev are managed, serverless-friendly platforms with more built-in (scheduling, retries, observability). The Pick Rate shows how agents weigh them.
How do I run background jobs in serverless?
Use an event-driven or hosted runner (Inngest, Trigger.dev) rather than a long-lived worker, since serverless functions can't run continuously. The ranking shows what agents reach for.