Resque vs. delayed_job

Hacker News, Reddit, Stack Overflow Stats

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

GitHub Stats


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!


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

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


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?


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


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


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

What are some alternatives to Resque and delayed_job?

  • Sidekiq - Simple, efficient background processing for Ruby
  • 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

See all alternatives to Resque

Interest Over Time