What is BullMQ
General description of BullMQ and its features
The library is designed so that it will fulfill the following goals:
- Exactly once queue semantics, i.e., attempts to deliver every message exactly one time, but it will deliver at least once in the worst case scenario*.
- Easy to scale horizontally. Add more workers for processing jobs in parallel.
- High performant. Try to get the highest possible throughput from Redis by combining efficient .lua scripts and pipelining.
If you are new to Message Queues, you may wonder why they are needed after all. Queues can solve many different problems in an elegant way, from smoothing out processing peaks to creating robust communication channels between micro-services or offloading heavy work from one server to many smaller workers, and many other use cases. Check the Patterns section for getting some inspiration and information about best practices.
- Minimal CPU usage due to a polling-free design
- Distributed job execution based on Redis
- LIFO and FIFO jobs
- Delayed jobs
- Scheduled and repeatable jobs according to cron specifications
- Retries of failed jobs
- Concurrency setting per worker
- Threaded (sandboxed) processing functions
- Automatic recovery from process crashes
- Parent-Child dependencies
BullMQ is used by many organizations big and small, here are some notable examples: