Resque

 Like

Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.

Resque screenshot 1

License model

  • FreeOpen Source

Platforms

  • Mac
  • Windows
  • Linux
  • Self-Hosted
  • Ruby
  • Redis
  • Ruby on Rails
  • RubyGems
  No rating
0likes
0comments
0news articles

Features

Suggest and vote on features
No features, maybe you want to suggest one?

 Tags

  • web-monitoring
  • background-processing
  • queues

Resque News & Activities

Highlights All activities

Recent activities

No activities found.

Resque information

  • Developed by

    Chris Wanstrath
  • Licensing

    Open Source (MIT) and Free product.
  • Written in

  • Alternatives

    4 alternatives listed
  • Supported Languages

    • English

GitHub repository

  •  9,459 Stars
  •  1,660 Forks
  •  87 Open Issues
  •   Updated Jan 6, 2025 
View on GitHub

Our users have written 0 comments and reviews about Resque, and it has gotten 0 likes

Resque was added to AlternativeTo by yaoqb on Jan 30, 2019 and this page was last updated Feb 1, 2019.
No comments or reviews, maybe you want to be first?
Post comment/review

What is Resque?

Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.

Resque (pronounced like "rescue") is a Redis-backed library for creating background jobs, placing those jobs 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.

Resque is heavily inspired by DelayedJob (which rocks) and comprises three parts:

A Ruby library for creating, querying, and processing jobs A Rake task for starting a worker which processes jobs A Sinatra app for monitoring queues, jobs, and workers.

Resque workers can be distributed between multiple machines, support priorities, are resilient to memory bloat / "leaks," are optimized for REE (but work on MRI and JRuby), tell you what they're doing, and expect failure.

Resque queues are persistent; support constant time, atomic push and pop (thanks to Redis); provide visibility into their contents; and store jobs as simple JSON packages.

The Resque frontend tells you what workers are doing, what workers are not doing, what queues you're using, what's in those queues, provides general usage stats, and helps you track failures.

Resque now supports Ruby 2.3.0 and above. We will also only be supporting Redis 3.0 and above going forward.

Official Links