Question: How does pub-sub model work in BullMQ?


In the context of BullMQ, a job queue for Node.js, the term "pub-sub" refers to the Publish-Subscribe pattern, a popular messaging model in distributed systems. The pub-sub model in BullMQ allows different parts of your application to communicate and synchronize with each other through jobs and events.

In BullMQ, jobs are processed independently by multiple worker processes possibly running on different machines. To keep all these workers synchronized and maintain consistency across the system, BullMQ uses the pub-sub model provided by Redis. When certain events occur (e.g., a job is completed, a new job is added), BullMQ publishes an event to Redis. All other interested parts of your system can subscribe to these events and react accordingly.

A simple example showing event subscription in BullMQ:

const queue = new Queue('Paint'); // Subscribe to 'completed' event queue.on('completed', (job, result) => { console.log(`Job ${} has been completed with result ${result}`); });

In the above code snippet, we create a queue named 'Paint'. Then we subscribe to its 'completed' event. Whenever a job in the 'Paint' queue is completed, the callback function will be invoked with the job and its result.

This pub-sub feature can be used to build complex distributed systems where you need to coordinate multiple workers or react to changes in job state.

Please note that due to the nature of pub-sub and network communications, listening to events in this manner should not be considered 100% reliable. For critical actions in response to job events, consider using job return values or maintaining your own application-level logs.

Was this content helpful?

Start building today

Dragonfly is fully compatible with the Redis ecosystem and requires no code changes to implement.