Get Advice Icon

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

Kue
Kue

30
36
+ 1
1
Workq
Workq

0
5
+ 1
0
Add tool

Kue vs Workq: 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, Workq is detailed as "Job server in Go". Workq is a job scheduling server strictly focused on simplifying job processing and streamlining coordination. It can run jobs in blocking foreground or non-blocking background mode.

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

Kue and Workq are both open source tools. Kue with 8.76K GitHub stars and 884 forks on GitHub appears to be more popular than Workq with 1.51K GitHub stars and 77 GitHub forks.

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

Workq is a job scheduling server strictly focused on simplifying job processing and streamlining coordination. It can run jobs in blocking foreground or non-blocking background mode.
Get Advice Icon

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

Why do developers choose Kue?
Why do developers choose Workq?
    Be the first to leave a pro
      Be the first to leave a con
        Be the first to leave a con
        What companies use Kue?
        What companies use Workq?
          No companies found

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

          What tools integrate with Kue?
          What tools integrate with Workq?
            No integrations found
              No integrations found
              What are some alternatives to Kue and Workq?
              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.
              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.
              See all alternatives
              Decisions about Kue and Workq
              No stack decisions found
              Interest over time
              Reviews of Kue and Workq
              No reviews found
              How developers use Kue and Workq
              No items found
              How much does Kue cost?
              How much does Workq cost?
              Pricing unavailable
              Pricing unavailable
              News about Kue
              More news
              News about Workq
              More news