What is BullMQ?
It is a Node.js library that implements a fast and robust queue system built on top of Redis. It is carefully written for rock solid stability and atomicity.
BullMQ is a tool in the Message Queue category of a tech stack.
BullMQ is an open source tool with GitHub stars and GitHub forks. Here’s a link to BullMQ's open source repository on GitHub
Who uses BullMQ?
- 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
BullMQ Alternatives & Comparisons
What are some alternatives to BullMQ?
See all alternatives
Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.
Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.
Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.
No related comparisons found