Home
Application and Data
Data Stores
Background Processing

Que vs Sidekiq

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

Que
15
18
+ 1
0
Sidekiq
1.1K
547
+ 1
407
Add tool

Que vs Sidekiq: 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, Sidekiq is detailed as "Simple, efficient background processing for Ruby". 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.

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

Que and Sidekiq are both open source tools. Sidekiq with 9.66K GitHub stars and 1.66K forks on GitHub appears to be more popular than Que with 1.47K GitHub stars and 119 GitHub forks.

Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Que
Pros of Sidekiq
    Be the first to leave a pro
    • 123
      Simple
    • 99
      Efficient background processing
    • 60
      Scalability
    • 37
      Better then resque
    • 26
      Great documentation
    • 15
      Admin tool
    • 14
      Great community
    • 8
      Integrates with redis automatically, with zero config
    • 7
      Great support
    • 7
      Stupidly simple to integrate and run on Rails/Heroku
    • 3
      Freeium
    • 3
      Ruby
    • 2
      Pro version
    • 1
      Dashboard w/live polling
    • 1
      Great ecosystem of addons
    • 1
      Fast

    Sign up to add or upvote prosMake informed product decisions

    Sign up to add or upvote consMake informed product decisions

    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 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.

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

    What companies use Que?
    What companies use Sidekiq?
    See which teams inside your own company are using Que or Sidekiq.
    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 Sidekiq?

    Blog Posts

    Kafka and Ruby, a Sidekiq Love Story
    Jun 6 2019 at 5:11PM

    AppSignal

    +9
    15
    1141
    The Stack That Helped Opendoor Buy and Sell Over $1B in Homes
    Mar 9 2017 at 8:02AM

    Opendoor

    +39
    22
    30923
    How Cotap Is Building A HIPAA-compliant Messaging Service On A...
    Jun 26 2015 at 10:14AM

    Zinc

    +39
    5
    1236
    How 500px serves up over 500TB of high res photos
    May 15 2015 at 3:43PM

    500px

    +44
    109
    49943
    From Minimum Triable Product to MVP - Building A Status Monito...
    May 8 2015 at 4:27PM

    StatusGator

    +20
    2
    793
    How Gusto Processes Billions Of Dollars In Annual Payroll
    Apr 17 2015 at 2:44AM

    Gusto

    +29
    6
    2604
    What are some alternatives to Que and Sidekiq?
    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.
    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.
    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.
    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.
    See all alternatives

    Related Comparisons

    Que vs Resque vs SidekiqResque vs Sidekiq vs delayed_jobKue vs SidekiqQue vs Sidekiq vs delayed_jobBeanstalkd vs Resque 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

    Bitbucket vs GitHub vs GitLabBootstrap vs MaterializePostman vs Swagger UIHipChat vs Mattermost vs Slack