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.
Resque is a tool in the Background Processing category of a tech stack.
Resque is an open source tool with 8.6K GitHub stars and 1.6K GitHub forks. Here’s a link to Resque's open source repository on GitHub
Who uses Resque?
43 companies reportedly use Resque in their tech stacks, including Walls.io, MAK IT, and NoRedInk.
40 developers on StackShare have stated that they use Resque.
Why developers like Resque?
Here’s a list of reasons why companies and developers use Resque
Resque Alternatives & Comparisons
What are some alternatives to Resque?
See all alternatives
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.
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 is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.
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.
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.