Get Advice Icon

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

Resque
Resque

87
52
+ 1
8
Sidekiq
Sidekiq

819
386
+ 1
403
Add tool

Resque vs Sidekiq: What are the differences?

Resque: 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; Sidekiq: 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.

Resque and Sidekiq can be categorized as "Background Processing" tools.

"Free" is the top reason why over 3 developers like Resque, while over 120 developers mention "Simple" as the leading cause for choosing Sidekiq.

Resque and Sidekiq are both open source tools. Sidekiq with 9.68K GitHub stars and 1.67K forks on GitHub appears to be more popular than Resque with 8.54K GitHub stars and 1.57K GitHub forks.

HotelTonight, New Relic, and Twilio SendGrid are some of the popular companies that use Sidekiq, whereas Resque is used by MAK IT, Stitched, and Youboox. Sidekiq has a broader approval, being mentioned in 348 company stacks & 77 developers stacks; compared to Resque, which is listed in 34 company stacks and 8 developer stacks.

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.

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 Resque?
Why do developers choose Sidekiq?

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 Resque?
      What companies use Sidekiq?

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

      What tools integrate with Resque?
      What tools integrate with Sidekiq?
      What are some alternatives to Resque and Sidekiq?
      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.
      Celery
      Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.
      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.
      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.
      See all alternatives
      Decisions about Resque and Sidekiq
      Jerome Dalbert
      Jerome Dalbert
      Senior Backend Engineer at StackShare | 4 upvotes 25.1K views
      atGratify CommerceGratify Commerce
      Amazon SQS
      Amazon SQS
      Ruby
      Ruby
      Sidekiq
      Sidekiq
      AWS Elastic Beanstalk
      AWS Elastic Beanstalk
      Rails
      Rails
      delayed_job
      delayed_job
      #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鈥檚 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鈥檛 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 10.1K views
      atStackShareStackShare
      Redis
      Redis
      delayed_job
      delayed_job
      Ruby
      Ruby
      Sidekiq
      Sidekiq

      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 Resque and Sidekiq
      Review ofSidekiqSidekiq

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

      How developers use Resque 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.

      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 Resque cost?
      How much does Sidekiq cost?
      Pricing unavailable
      Pricing unavailable
      News about Resque
      More news