Get Advice Icon

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

Que
Que

10
8
+ 1
0
Sidekiq
Sidekiq

826
391
+ 1
403
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.

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.
Get Advice Icon

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

Why do developers choose Que?
Why do developers choose Sidekiq?
    Be the first to leave a pro

    Sign up to add, upvote and see more prosMake informed product decisions

      Be the first to leave a con
        Be the first to leave a con
        What companies use Que?
        What companies use Sidekiq?

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

        What tools integrate with Que?
        What tools integrate with Sidekiq?
        What are some alternatives to Que and Sidekiq?
        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.
        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 Sidekiq
        Jerome Dalbert
        Jerome Dalbert
        Senior Backend Engineer at StackShare · | 4 upvotes · 28.1K views
        atGratify CommerceGratify Commerce
        delayed_job
        delayed_job
        Rails
        Rails
        AWS Elastic Beanstalk
        AWS Elastic Beanstalk
        Sidekiq
        Sidekiq
        Ruby
        Ruby
        Amazon SQS
        Amazon SQS
        #BackgroundProcessing

        delayed_job is a great Rails background job library for new projects, as it only uses what you already have: a relational database. We happily used it during the company’s first two years.

        But it started to falter as our web and database transactions significantly grew. Our app interacted with users via SMS texts sent inside background jobs. Because the delayed_job daemon ran every couple seconds, this meant that users often waited several long seconds before getting text replies, which was not acceptable. Moreover, job processing was done inside AWS Elastic Beanstalk web instances, which were already under stress and not meant to handle jobs.

        We needed a fast background job system that could process jobs in near real-time and integrate well with AWS. Sidekiq is a fast and popular Ruby background job library, but it does not leverage the Elastic Beanstalk worker architecture, and you have to maintain a Redis instance.

        We ended up choosing active-elastic-job, which seamlessly integrates with worker instances and Amazon SQS. SQS is a fast queue and you don’t need to worry about infrastructure or scaling, as AWS handles it for you.

        We noticed significant performance gains immediately after making the switch.

        #BackgroundProcessing

        See more
        Jerome Dalbert
        Jerome Dalbert
        Senior Backend Engineer at StackShare · | 3 upvotes · 12.1K views
        atStackShareStackShare
        Sidekiq
        Sidekiq
        Ruby
        Ruby
        delayed_job
        delayed_job
        Redis
        Redis

        We use Sidekiq to process millions of Ruby background jobs a day under normal loads. We sometimes process more than that when running one-off backfill tasks.

        With so many jobs, it wouldn't really make sense to use delayed_job, as it would put our main database under unnecessary load, which would make it a bottleneck with most DB queries serving jobs and not end users. I suppose you could create a separate DB just for jobs, but that can be a hassle. Sidekiq uses a separate Redis instance so you don't have this problem. And it is very performant!

        I also like that its free version comes "batteries included" with:

        • A web monitoring UI that provides some nice stats.
        • An API that can come in handy for one-off tasks, like changing the queue of certain already enqueued jobs.

        Sidekiq is a pleasure to use. All our engineers love it!

        See more
        Interest over time
        Reviews of Que and Sidekiq
        Review ofSidekiqSidekiq

        Pretty good post. I found your website perfect for my needs bullet force

        How developers use Que and Sidekiq
        Avatar of SmartLogic
        SmartLogic uses SidekiqSidekiq

        We turn to Sidekiq when we need to run background jobs in a Rails app, which we do for just about every Rails app we write. We especially like the ops tools that come with Sidekiq, which make it easy to monitor and maintain.

        Avatar of Tim Lucas
        Tim Lucas uses SidekiqSidekiq

        Background processing of Pushover push notifications to admins when sales occur, payments processing via Pin Payments, Campaign Monitor transaction email sending, and Intercom event API posting.

        Avatar of Told
        Told uses SidekiqSidekiq

        Sidekiq is used extensively for a multitude of background jobs, everything from audio/video post-processing to sending push notifications.

        Avatar of Jeff Flynn
        Jeff Flynn uses SidekiqSidekiq

        We offload our background processing tasks (photo sizing, watermarking, etc.) to Sidekiq to keep our app's performance optimal.

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