starter.wiki

Application-owned Redis job workers

BullMQ

An MIT-licensed Redis-backed queue and worker library for application-owned background jobs.

Visit official site

Editorial verdict

Choose BullMQ when the team deliberately wants application-owned Redis jobs and workers and can make them reliable.12

Best for

  • Direct library-level job and worker control
  • Existing Redis operations that meet BullMQ durability needs
  • Retries, delays, concurrency, and dependency patterns that fit BullMQ
12

Not ideal for

  • Teams wanting managed workers or a managed control plane
  • Organizations unable to operate Redis persistence and non-eviction policy
  • Complex multi-service workflows needing durable history
12
Main trade-off

Direct control and low control-plane dependence are gained with full ownership of Redis, workers, scaling, monitoring, retries, duplicates, upgrades, and recovery.12

Product boundary

Whether direct Redis-backed job and worker control is worth owning the full reliability and operations stack.

BullMQ is a library, not managed compute or a managed control plane; the team supplies Redis, workers, persistence, monitoring, scaling, and recovery.12

For: Node.js and supported-client teams able to operate Redis and worker processes

  • Redis durability and non-eviction cannot be guaranteed.
  • The team does not want to operate workers.
  • The workload needs durable workflow history rather than job primitives.

Why teams consider BullMQ

  • Direct controlThe application owns queues, jobs, and workers through the library.12
  • Job primitivesRetries, delays, concurrency, and dependencies are supported.12
  • OSS routeThe core project is MIT-licensed.12

Pricing

BullMQ is open-source with no separate software fee; total cost is Redis, worker compute, network, storage and backup, monitoring, support, and engineering. BullMQ Pro pricing is not represented as a verified public snapshot.4

Self-operated job system

BullMQ OSS plus infrastructure

Model Redis, workers, network, storage, backup, monitoring, on-call, upgrades, and recovery.4

OSS license
MIT4
Commercial boundary
BullMQ Pro is per-organization; no verified public rate4
Pricing checked View official pricing

BullMQ vs alternatives

Trigger.dev

Choose when
Choose managed TypeScript task workers.
Compared with BullMQ
Managed execution adds platform coupling but removes Redis/worker operations.56

Inngest

Choose when
Choose event-driven durable functions and managed orchestration.
Compared with BullMQ
Its control plane and step model replace direct Redis ownership.7

Temporal

Choose when
Choose durable multi-service workflow history.
Compared with BullMQ
The programming and worker model is substantially larger.89

Resources and sources

Official product, policy, and pricing

  • BullMQ documentation
    Open
  • BullMQ production guidance
    Open
  • BullMQ repository and MIT license
    Open
  • BullMQ Pro introduction
    Open

Related tasks

  1. 1
    BullMQ documentation

    Taskforce.sh · Accessed Official

  2. 2
    BullMQ production guidance

    Taskforce.sh · Accessed Official

  3. 3
    BullMQ repository and MIT license

    Taskforce.sh · Accessed Official

  4. 4
    BullMQ Pro introduction

    Taskforce.sh · Accessed Official

  5. 5
    Trigger.dev documentation

    Trigger.dev · Accessed Official

  6. 6
    Trigger.dev pricing

    Trigger.dev · Accessed Official

  7. 7
    Inngest functions

    Inngest · Accessed Official

  8. 8
    Temporal documentation

    Temporal · Accessed Official

  9. 9
    Temporal Cloud pricing

    Temporal · Accessed Official