Need advice about which tool to choose?Ask the StackShare community!

Kue

33
80
+ 1
2
Resque

109
104
+ 1
9
Add tool

Kue vs Resque: What are the differences?

Developers describe Kue 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. On the other hand, Resque is detailed as "A Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later". 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.

Kue and Resque belong to "Background Processing" category of the tech stack.

Kue and Resque are both open source tools. It seems that Kue with 8.76K GitHub stars and 884 forks on GitHub has more adoption than Resque with 8.54K GitHub stars and 1.57K GitHub forks.

According to the StackShare community, Resque has a broader approval, being mentioned in 34 company stacks & 8 developers stacks; compared to Kue, which is listed in 6 company stacks and 5 developer stacks.

Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Kue
Pros of Resque
  • 2
    Simple
  • 5
    Free
  • 3
    Scalable
  • 1
    Easy to use on heroku

Sign up to add or upvote prosMake informed product decisions

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 is 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.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Kue?
What companies use Resque?
See which teams inside your own company are using Kue or Resque.
Sign up for Private StackShareLearn More

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

What tools integrate with Kue?
What tools integrate with Resque?
    No integrations found
    What are some alternatives to Kue and Resque?
    Bull
    The fastest, most reliable, Redis-based queue for Node. Carefully written for rock solid stability and atomicity.
    RabbitMQ
    RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
    Celery
    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.
    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.
    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