Stacks32

Followers58

+ 1

Votes4

Kue

Stacks33

Followers66

+ 1

Votes1

Add tool

Bull vs Kue: What are the differences?

Developers describe Bull as "Premium Queue package for handling jobs and messages in NodeJS". The fastest, most reliable, Redis-based queue for Node Carefully written for rock solid stability and atomicity.

. On the other hand, Kue is detailed as "Kue is a priority job queue backed by redis, built for node.js". Kue is a feature rich priority job queue for node.js backed by redis. A key feature of Kue is its clean user-interface for viewing and managing queued, active, failed, and completed jobs.

Bull and Kue can be categorized as "Background Processing" tools.

Bull and Kue are both open source tools. Kue with 8.74K GitHub stars and 880 forks on GitHub appears to be more popular than Bull with 5.78K GitHub stars and 566 GitHub forks.

Pros of Bull

Pros of Kue

2
Automatic recovery from process crashes
1
Ease of use
1
Based on Redis

1
Simple

Sign up to add or upvote prosMake informed product decisions

Sign up to add or upvote consMake informed product decisions

What is Bull?

The fastest, most reliable, Redis-based queue for Node. Carefully written for rock solid stability and atomicity.

What is Kue?

Kue is a feature rich priority job queue for node.js backed by redis. A key feature of Kue is its clean user-interface for viewing and managing queued, active, failed, and completed jobs.

What companies use Bull?

What companies use Kue?

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Bull?

What tools integrate with Kue?

Node.js
Lad

No integrations found

What are some alternatives to Bull and Kue?

Buffalo

Buffalo is Go web framework. Yeah, I hate the word "framework" too! Buffalo is different though. Buffalo doesn't want to re-invent wheels like routing and templating. Buffalo is glue that wraps all of the best packages available and makes them all play nicely together.

Sidekiq

Sidekiq uses threads to handle many jobs at the same time in the same process. It does not require Rails but will integrate tightly with Rails 3/4 to make background processing dead simple.

Resque

Background jobs can be any Ruby class or module that responds to perform. Your existing classes can easily be converted to background jobs or you can create new classes specifically to do work. Or, you can do both.

Beanstalkd

Beanstalks's interface is generic, but was originally designed for reducing the latency of page views in high-volume web applications by running time-consuming tasks asynchronously.

Hangfire

It is an open-source framework that helps you to create, process and manage your background jobs, i.e. operations you don't want to put in your request processing pipeline. It supports all kind of background tasks – short-running and long-running, CPU intensive and I/O intensive, one shot and recurrent.

See all alternatives

Interest over time

Bull vs Kue