Get Advice Icon

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

Que
Que

10
8
+ 1
0
Workq
Workq

0
5
+ 1
0
Add tool

Que vs Workq: What are the differences?

Developers describe Que 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. 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.

Que and Workq can be primarily classified as "Background Processing" tools.

Que and Workq are both open source tools. Workq with 1.51K GitHub stars and 77 forks on GitHub appears to be more popular than Que with 1.47K GitHub stars and 122 GitHub forks.

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.

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 Que?
Why do developers choose Workq?
    Be the first to leave a pro
      Be the first to leave a pro
        Be the first to leave a con
          Be the first to leave a con
          What companies use Que?
          What companies use Workq?
            No companies found

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

            What tools integrate with Que?
            What tools integrate with Workq?
              No integrations found
              What are some alternatives to Que and Workq?
              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.
              delayed_job
              Delayed_job (or DJ) encapsulates the common pattern of asynchronously executing longer tasks in the background. It is a direct extraction from Shopify where the job table is responsible for a multitude of core tasks.
              PHP-FPM
              It is an alternative PHP FastCGI implementation with some additional features useful for sites of any size, especially busier sites. It includes Adaptive process spawning, Advanced process management with graceful stop/start, Emergency restart in case of accidental opcode cache destruction etc.
              See all alternatives
              Decisions about Que and Workq
              No stack decisions found
              Interest over time
              Reviews of Que and Workq
              No reviews found
              How developers use Que and Workq
              No items found
              How much does Que cost?
              How much does Workq cost?
              Pricing unavailable
              Pricing unavailable
              News about Que
              More news
              News about Workq
              More news