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

Kue

33
80
+ 1
2
Sidekiq

1K
554
+ 1
407
Add tool

Kue vs Sidekiq: What are the differences?

What is Kue? 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.

What is Sidekiq? Simple, efficient background processing for Ruby. 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.

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

Kue and Sidekiq are both open source tools. It seems that Sidekiq with 9.66K GitHub stars and 1.66K forks on GitHub has more adoption than Kue with 8.74K GitHub stars and 880 GitHub forks.

StackShare, SendGrid, and New Relic are some of the popular companies that use Sidekiq, whereas Kue is used by Gigster, Fraeber Labs Pvt Ltd, and Greenkeeper. Sidekiq has a broader approval, being mentioned in 346 company stacks & 77 developers stacks; compared to Kue, which is listed in 6 company stacks and 4 developer stacks.

Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Kue
Pros of Sidekiq
  • 2
    Simple
  • 123
    Simple
  • 99
    Efficient background processing
  • 60
    Scalability
  • 37
    Better then resque
  • 26
    Great documentation
  • 15
    Admin tool
  • 14
    Great community
  • 8
    Integrates with redis automatically, with zero config
  • 7
    Great support
  • 7
    Stupidly simple to integrate and run on Rails/Heroku
  • 3
    Freeium
  • 3
    Ruby
  • 2
    Pro version
  • 1
    Fast
  • 1
    Dashboard w/live polling
  • 1
    Great ecosystem of addons

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

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

What companies use Kue?
What companies use Sidekiq?
See which teams inside your own company are using Kue or Sidekiq.
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 Sidekiq?
    No integrations found

    Blog Posts

    Jun 6 2019 at 5:11PM

    AppSignal

    RedisRubyKafka+9
    15
    1216
    GitHubSlackMySQL+44
    109
    50188
    What are some alternatives to Kue and Sidekiq?
    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.
    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.
    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.
    See all alternatives