Adds methods for working with Batch Jobs

Allows resque jobs to be run in batches with aggregate logging, timing and statistics

Allow resque to serialize consumption from queues based on a key.

Allows you to requeue jobs to another queue This is useful in my situations : - A large amount of jobs are queued in the critical queue, blocking the main queue for Several hours. Select jobs based on criteria and requeue them to the low queue

Show queued Resque job statistics by job class

Resque command line tool

Send Resque.info to CloudWatch Metrics

Allows reporting failures of resque jobs to Amazon CloudWatch

Sends exceptions to coalmineapp.com

A handler for Resque's failure backend that will send exceptions through to crashlog.io. Uses your existing CrashLog setup.

A Resque plugin. Allows you to use Redis to queue up and then Resque to process transactions on transaction-heavy tables that need to be replicated on other tables optimized for reporting.

Defining Resque boilerplate since 2013

Allow execute methods in background without adding new jobs. Like .delay method in DelayedJob

Enable send_later support for Resque. Includes support for mongoid backends. Based on the original resque-delay gem by Michael Ryko.

With ResqueDelivery, you can send ActionMailer messages asynchronously with Resque.

This is a Resque plugin that allows us to disable jobs from being processed, by using the job class name and arguments. It uses some Redis data structures to keep a record of what jobs need to be disabled and how many jobs were disabled for that rule.

Resque allows a single queue to have multiple jobs of the same time. This is because it uses a redis list, which does not have the concept of a unique entry. Sometimes, however, a particular value is only needed if it isn't already on the queue.

Resque queue backed by database audits, with automatic retry

resque_empty_queue is an extension to the Resque queue system runs a job after a queue has been emptied.

A Resque plugin. Adds locking, with optional timeout/deadlock handling to resque jobs. Using a `lock_timeout` allows you to re-aquire the lock should your worker fail, crash, or is otherwise unable to relase the lock. i.e. Your server unexpectedly looses power. Very handy for jobs that are recurring or may be retried.