Sidekiq vs. Resque vs. delayed_job



Hacker News, Reddit, Stack Overflow Stats

  • -
  • -
  • 1.83K
  • 16
  • 2.06K
  • 1.03K
  • 2
  • 76
  • 0

GitHub Stats

Description

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.

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

Want advice about which of these to choose?Ask the StackShare community!

Pros

Why do developers choose Sidekiq?
Why do you like Sidekiq?

Why do developers choose Resque?
Why do you like Resque?

Why do developers choose delayed_job?
Why do you like delayed_job?

Cons

What are the cons of using Sidekiq?
No Cons submitted yet for Sidekiq
Downsides of Sidekiq?

What are the cons of using Resque?
No Cons submitted yet for Resque
Downsides of Resque?

What are the cons of using delayed_job?
No Cons submitted yet for delayed_job
Downsides of delayed_job?

Pricing

How much does Sidekiq cost?
How much does Resque cost?
How much does delayed_job cost?

Companies

What companies use Sidekiq?
409 companies on StackShare use Sidekiq
What companies use Resque?
41 companies on StackShare use Resque
What companies use delayed_job?
12 companies on StackShare use delayed_job

Integrations

What tools integrate with Sidekiq?
2 tools on StackShare integrate with Sidekiq
What tools integrate with Resque?
1 tools on StackShare integrate with Resque
No integrations listed yet

What are some alternatives to Sidekiq, Resque, and delayed_job?

  • Beanstalkd - A simple, fast work queue
  • Kue - Kue is a priority job queue backed by redis, built for node.js
  • Que - A Ruby job queue that uses PostgreSQL's advisory locks for speed and reliability
  • Bull - Premium Queue package for handling jobs and messages in NodeJS

See all alternatives to Sidekiq

Latest News

Cleanly Scaling Sidekiq
Related Stack Decisions
Jerome Dalbert
Jerome Dalbert
Backend Engineer at StackShare · | 3 upvotes · 3122 views
atGratify Commerce
Amazon SQS
Ruby
Sidekiq
AWS Elastic Beanstalk
Rails
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’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


Interest Over Time