Prompt
unhappy with BullMQ for multi-service task processing
Latest observation
Nov 1, 2026
OpenAI APIWeb search: off
If you’re unhappy with BullMQ for multi-service task processing, you’re probably running into one or more of these common issues:
- Redis dependency feels limiting or operationally annoying
- Queue visibility / debugging across services is weak
- Backpressure, retries, and dead-letter handling aren’t as ergonomic as you’d like
- Cross-service coordination becomes awkward
- Scaling and reliability are harder than expected
- TypeScript/Node-centric design doesn’t fit all services well
Better alternatives depend on what you need
1. Temporal
Best if you want durable workflows, retries, timers, long-running jobs, and multi-service orchestration.
Pros
- Very strong for distributed task processing
- Built-in retries, timeouts, state persistence
- Great observability
- Good for multi-service orchestration
Cons
- More complex than a simple queue
- Requires adopting workflow concepts
- Operational overhead
2. RabbitMQ
Best if you want a classic message broker for multi-service event/task delivery.
Pros
- Mature and widely used
- Flexible routing patterns
- Good for service-to-service messaging
Cons
- You manage retry/DLQ patterns yourself
- Not a workflow engine
- Less opinionated about task state
3. Kafka
Best if your “tasks” are really event streams and you need scale, replay, and decoupling.
Pros
- Excellent throughput
- Durable event log
- Great for event-driven architectures
Cons
- Not ideal for job-style execution semantics
- More complex to reason about task completion/retries
4. NATS + JetStream
Best if you want lightweight, fast messaging with persistence.
Pros
- Fast and simple
- Good pub/sub and queue semantics
- JetStream adds durability
Cons
- Smaller ecosystem than Kafka/RabbitMQ
- Workflow semantics still need to be built
5. Sidekiq / Resque / Celery / Dramatiq
Best if your stack aligns with Ruby or Python.
If you want to stay in Node.js
Consider:
- Temporal for serious multi-service workflows
- RabbitMQ for robust queues
- NATS JetStream for lightweight distributed messaging
Rule of thumb
- Need orchestration and reliability? Temporal
- Need a queue/broker? RabbitMQ or NATS
- Need event streaming and replay? Kafka
- Need simple in-process-ish job queues? BullMQ may still be fine, but it sounds like you’ve outgrown it
If you want, I can help you choose based on:
- your architecture,
- your service count,
- job volume,
- retry/delay requirements,
- and whether you need exactly-once-ish behavior.