Home
Application and Data
Data Stores
Background Processing

Kue vs Que

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

Kue
42
88
+ 1
2
Que
16
20
+ 1
0
Add tool

Kue vs Que: 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, Que is detailed as "A Ruby job queue that uses PostgreSQL's advisory locks for speed and reliability". Que is a high-performance alternative to DelayedJob or QueueClassic that improves the reliability of your application by protecting your jobs with the same ACID guarantees as the rest of your data.

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

Kue and Que are both open source tools. It seems that Kue with 8.76K GitHub stars and 884 forks on GitHub has more adoption than Que with 1.47K GitHub stars and 122 GitHub forks.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Kue
Pros of Que
  • 2
    Simple
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    - No public GitHub repository available -

    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 Que?

    Que is a high-performance alternative to DelayedJob or QueueClassic that improves the reliability of your application by protecting your jobs with the same ACID guarantees as the rest of your data.

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

    What companies use Kue?
    What companies use Que?
    See which teams inside your own company are using Kue or Que.
    Sign up for StackShare EnterpriseLearn More

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

    What tools integrate with Kue?
    What tools integrate with Que?
      No integrations found
      What are some alternatives to Kue and Que?
      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

      Related Comparisons

      Bull vs KueQue vs Resque vs SidekiqKue vs ResqueKue vs SidekiqQue vs Sidekiq

      Trending Comparisons

      Django vs Laravel vs Node.jsBootstrap vs Foundation vs Material-UINode.js vs Spring BootFlyway vs LiquibaseAWS CodeCommit vs Bitbucket vs GitHub

      Top Comparisons

      Bootstrap vs MaterializeHipChat vs Mattermost vs SlackBitbucket vs GitHub vs GitLabPostman vs Swagger UI