Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Resque review

Free#32 of 36 in Task Queue Software

A focused, open-source queue for Ruby teams running background jobs on Redis.

6.1/10Editor score
Resque6.1 Visit Resque

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Resque is an open-source Ruby library for creating background jobs, placing them on persistent Redis-backed queues, and processing them through worker processes. It suits Ruby and Ruby on Rails teams that need a basic self-hosted task queue with multiple queues, priorities, queue visibility, and failure tracking. Jobs use JSON-serializable arguments, while integrations include Redis, Ruby on Rails, ActiveJob, and Sinatra.

Its strongest feature is the combination of queue control and operational visibility. Teams can run multiple queues, assign priorities, and use worker processes for background execution. The Sinatra web interface provides views of queues, jobs, workers, and failures, while configurable failure backends support failure tracking. This makes Resque a focused fit for applications that want core queue processing without adopting a broader application platform. Its official SDK coverage is Ruby, so teams centered on Ruby will find the clearest ecosystem alignment.

Resque stays narrow by design. Deployment is self-hosted, making infrastructure operation part of adopting the software. Recurring and delayed jobs are available through the separately maintained resque-scheduler extension rather than the core Resque repository, so scheduling is an additional component to manage. Teams should choose Resque when they want an open-source Redis queue for Ruby or Rails and value a straightforward monitoring interface. It is less suitable for organizations seeking a managed service, broad language coverage, or scheduling built directly into the core package.

Resque pros and cons

  • Where it wins
    • Persistent Redis queues with priorities and multiple queue support
    • Sinatra interface monitors queues, jobs, workers, and failures
    • Open-source, self-hosted deployment for Ruby and Rails applications
  • Where it doesn't
    • Scheduling requires the separately maintained resque-scheduler extension
    • Self-hosted deployment places operations and maintenance with the team
    • Ruby-focused ecosystem limits its fit for non-Ruby applications

Resque fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update