Gem that sends mail in case of resque job failure

Normally resque processes queues in a fixed order. This can lead to jobs in queues at the end of the list not getting process for very long periods. resque-fairly provides a mechanism where by workers are distributed across the set of queues with pending jobs fairly. This results in a much more predictable mean time to handling for jobs in queues that are not the first in the list.

A Resque plugin that provides endpoints which distributes Jobs submitted to them to (multiple) subscribing queues. Useful for loosely coupled inter-application communication.

Use the power of forking to run multiple Resque workers.

[description]

Handles establishing and disconnecting db connections when running Resque on Heroku cedar stack.

Auto-scale Heroku workers for Resque

Seamless integration of resque with resque-progress and resque-lock

Keeps a history of run jobs by job.

Syntax sugar for Resque consumers. Each consumer is a class, with clean interface, and custom logger. Usefull when count of different events ~100 and more.

A Resque plugin to ensure unique workers while preventing queue starvation

Simple asynchronous emails with Resque

A Resque plugin. Provides a lightweight publish/subscribe messaging system, with message persistence when clients are down.

A Resque plugin. If you want only one instance of your job queued at a time, extend it with this module. For example: class ExampleJob extend Resque::Jobs::Queue::Lock def self.perform(repo_id) heavy_lifting end end

A Resque plugin which allows you to create dedicated queues for jobs that use rate limited apis. These queues will pause when one of the jobs hits a rate limit, and unpause after a suitable time period. The rate_limited_queue can be used directly, and just requires catching the rate limit exception and pausing the queue. There are also additional queues provided that already include the pause/rety logic for twitter, angelist and evernote; these allow you to support rate limited apis with minimal changes.

resque plugin that allows you to attach information when a job is put in redis, and to do whatever you want with the information when it is popped off the resque queue

Compatible with Resque 1.x. Use Resque.push if you are using >= 2.x. Resque is great. So is job processing with redis. Our biggest drawback has been that resque requires the class that will be processing a job to be loaded when the job is enqueued. But what happens when the implementing job is defined in a separate application and isn't currently loaded into memory? Enter Resque Remote. Resque Remote's simple goal is to allow you to add a job to a queue with a string identifier for the class rather than the class constant. It is assumed that the worker-side of the equation _will_ have the class in memory and hence will be able to run it no problem. Feedback, comments and questions are welcome at bj [dot] neilsen [at] gmail [dot] com.

If you want to be able fetch the result from a Resque job's perform method. Results will be encoded using JSON. For example: require 'resque-result' class MyJob extend Resque::Plugins::Result def self.perform(meta_id, big_num) factor(big_num) end end meta0 = MyJob.enqueue(3574406403731) meta0.enqueued_at # => 'Wed May 19 13:42:41 -0600 2010' meta0.meta_id # => '03c9e1a045ad012dd20500264a19273c' # later meta1 = MyJob.get_meta('03c9e1a045ad012dd20500264a19273c') meta1.succeeded? # => true meta1.result # => [ 1299709, 2750159 ]

Sliding Window unique-job workflow for Resque jobs

Deliver mail in a resque job