bull
Premium Queue package for handling distributed jobs and messages in NodeJS. (by OptimalBits)
The gist
BullMQ - Message Queue and Batch processing for NodeJS and Python based on Redis (by taskforcesh)
Our great sponsors
bull | The gist | |
---|---|---|
50 | 26 | |
15,039 | 5,182 | |
0.9% | 4.9% | |
6.8 | 9.7 | |
3 days ago | 5 days ago | |
JavaScript | TypeScript | |
GNU General Public License v3.0 or later | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bull
Posts with mentions or reviews of bull.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-03-15.
-
Prioritizing Concurrent Requests: Queuing system to handle distributed processes and messages with NodeJS and Bull
To implement the solution with a queue, I used a package called 'Bull' (https://github.com/OptimalBits/bull). It's a library that helps with distributed job control, providing some very useful solutions for this type of work, such as background job processing, queues with priorities (FIFO, LIFO, and others), among other features. 'Bull' uses Redis for queue storage, so if your application crashes for any reason, once it's back online, it will continue executing the processes that are in the queue. In our case, we'll use the FIFO (First in, first out) queue solution, meaning priority based on arrival order.
-
Instrumentation for Event Driven
We use bull-js for our distributed queue and event-driven library.
-
Redis master/slave setup on Kubernetes throwing error: BRPOPLPUSH { ReplyError: MOVED 2651
I'm using the excellent Redis based Bull.js as a job queue on Kubernetes.
-
How to use Job Queue to handle email sending in your Nestjs server
For Job Queue, NestJs provides a package named @nestjs/bull as an abstraction/wrapper on top of Bull, a popular, well-supported, high-performance Node. js-based Queue system implementation.
-
How do you handle queues in Node.js? Have you ever tried using pgboss?
I'm working on a large ETL project that involves handling queues for file integration. Currently, we are using Redis with Bull (https://www.npmjs.com/package/bull) for this purpose. However, to streamline our architecture and address security concerns, we are considering migrating the queue to PostgreSQL.
-
What is a good background scheduler?
BullMQ is a pretty solid choice: https://github.com/taskforcesh/bullmq It's the successor of Bull: https://github.com/OptimalBits/bull
-
Learning Guidance
For Node specifically, things like Streams, understanding the asynchronous model completely, and the event loop. Also, queues tend to get used a lot in Node, so understanding the basic concepts behind that and how to use something like bull would be useful.
-
image processing in express application, should it be done in a separate thread?
To do this properly, you need to put the task into queue, so if there are 1000 simultaneous uploads it won't kill your server but will be processed one by one. For the queue, see bull. Image hostings like AWS have some functionality for processing on their side, as an option.
- Best development practice for setting up a cron job for each user?
-
How do I implement Heroku background processes?
This is a memory intensive process though and Heroku is OOM'ing with R14 errors. For this they recommend migrating intensive work like this to a Background Job via Redis, implemented in Bull and Throng
The gist
Posts with mentions or reviews of The gist.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-07-06.
-
Object Narrowing in Typescript with Graphile Worker
Graphile worker has been great for me because it's a library that works with Postgres that allows me to queue jobs and execute them on the server without adding too many additional layers of complexity for being able to accomplish async tasks. (I'm aware of how popular bull is, but I don't want to add another data-store only for async tasks)
-
Job Schedulers for Node: Bull or Agenda?
Bull is currently in maintenance mode, we are only fixing bugs. For new features check BullMQ, a modern rewritten implementation in Typescript. You are still very welcome to use Bull if it suits your needs, which is a safe, battle-tested library.
-
Are there any generally accepted standards for inter-microservice communication? Or does everyone just go it their own?
I use bullmq with node
-
Next.js background jobs
You might consider using a queue for processing the request. I've found bullMQ, which works with Redis, to be a nice developer experience.
-
What is a good background scheduler?
BullMQ is a pretty solid choice: https://github.com/taskforcesh/bullmq It's the successor of Bull: https://github.com/OptimalBits/bull
-
How to schedule tasks in a Node.js app 🕙
BullMQ
-
First time building microservice-based application
For Node.JS you can use something like BullMQ (https://github.com/taskforcesh/bullmq) and then dispatch jobs to the message queue with your worker handling the jobs. You can read about an example for Bull MQ here (https://deadsimplechat.com/blog/best-nodejs-schedulers/#2-bull)
-
Is my health check endpoint good enough?
bullmq seems like an open issue
-
Help implementing Heroku Data For Redis (+bull & throng) / `ioredis`
In order to try and mitigate the OOMs. I read the Background Jobs in Node.JS with Redis blog post and implemented Heroku Data For Redis with ioredis, BullMQ and Throng,
- BullMQ – fastest, most reliable, Redis-based distributed queue for Node
What are some alternatives?
When comparing bull and The gist you can also consider the following projects:
Bee-Queue - A simple, fast, robust job/task queue for Node.js, backed by Redis.
kue - Kue is a priority job queue backed by redis, built for node.js.
better-queue - Better Queue for NodeJS
node-resque - Node.js Background jobs backed by redis.
RedisSMQ - A simple high-performance Redis message queue for Node.js.
agenda - Lightweight job scheduling for Node.js
bottleneck - Job scheduler and rate limiter, supports Clustering
bree - Bree is a Node.js and JavaScript job task scheduler with worker threads, cron, Date, and human syntax. Built for @ladjs, @forwardemail, @spamscanner, @cabinjs.