Get Advice Icon

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

Que
Que

10
8
+ 1
0
Resque
Resque

84
50
+ 1
8
Add tool

Que vs Resque: 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, 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.

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

Que and Resque are both open source tools. Resque with 8.54K GitHub stars and 1.57K 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 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.
Get Advice Icon

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

Why do developers choose Que?
Why do developers choose Resque?
    Be the first to leave a pro
    What are the cons of using Que?
    What are the cons of using Resque?
      Be the first to leave a con
        Be the first to leave a con
        What companies use Que?
        What companies use Resque?

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

        What tools integrate with Que?
        What tools integrate with Resque?
        What are some alternatives to Que and Resque?
        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.
        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.
        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.
        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
        Decisions about Que and Resque
        No stack decisions found
        Interest over time
        Reviews of Que and Resque
        No reviews found
        How developers use Que and Resque
        Avatar of La Cupula Music SL
        La Cupula Music SL uses ResqueResque

        Short term we'll migrate to Sidekiq.

        Avatar of PiggyBike
        PiggyBike uses ResqueResque

        Background syncing of Strava data.

        How much does Que cost?
        How much does Resque cost?
        Pricing unavailable
        Pricing unavailable
        News about Que
        More news
        News about Resque
        More news