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) e...

Sliding Window unique-job workflow for Resque jobs

Deliver mail in a resque job

Telework is a Resque plugin aimed at controlling Resque workers from the web UI. It makes it easy to manage workers on a complex systems that may include several hosts, different queue(s) and an evolving source code that is deployed several times a day. Beyond starting and stopping worker...

top for Resque

Unique Resque queues using redis 1.6.0 scripting, sets and not much else

Automatically kill a child of resque worker based on max memory.

Utilities for using Resque in a Rails app

RhoConnect App Integration Server and related command-line utilities

A unified interface for various messaging queues

This plugin provides native instrumentation for collecting Resque metrics for queue, worker, working, failed, pending, and processed jobs.

Provides a simpler interface to enqueue Resque jobs between codebases without having to define the Jobs in multiple codebases.

Duck punch Resque to use active record for backround jobs instead of redis

Trinidad extension to autoconfigure and launch Resque

Uploadbox makes easy to manage files in your Rails application.

This provides achievement features for rails app.

Better jobs. Good jobs.

Provides async methods ruby objects for queuing background jobs. Currently supports Resque. Bonus: callback hooks for ActiveRecord objects

If you're using ActiveRecord with Resque, a new database connection will get opened for each worker process. When the worker completes, this connection is left open by default, which is pretty bad. This adapter closes the connection when the job has_rdoc finished executing.

Uses a Configuration/Controller pattern to allow easy implementation and organziation of multi-tier distributed workloads.