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

Que

15
19
+ 1
0
Resque

111
109
+ 1
9
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.

Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Que
Pros of Resque
    Be the first to leave a pro
    • 5
      Free
    • 3
      Scalable
    • 1
      Easy to use on heroku

    Sign up to add or upvote prosMake informed product decisions

    - No public GitHub repository available -

    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.

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

    What companies use Que?
    What companies use Resque?
    See which teams inside your own company are using Que or Resque.
    Sign up for Private StackShareLearn More

    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.
    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.
    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.
    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.
    Bull
    The fastest, most reliable, Redis-based queue for Node. Carefully written for rock solid stability and atomicity.
    See all alternatives