Backend agnostic queuing implementation

Resque-compatible job processing in an event loop

Spec support for Pageflow extensions.

A robust implementation of send_later for Rails apps using Resque.

Take a peek into your Resque queues and workers.

Penelope Core library

Sends messages to kafka using different formats and strategies

Cloudfiles client

Tools to manage,create and build distribution packages

Call any ActiveRecord instance method as though it was a Resque job

Description of Qujo.

Flexible bioinformatics search tool.

Guard::Resque automatically starts/stops/restarts resque worker

Run Rake tasks via a Resque worker. Rails startup is slow, hence Rake is too. It's already loaded into Resque so let’s use it from there

Provides a REST API for backing up live RDS instances to S3 as a compressed SQL file.

Redcross gem transport events to an event collector

RedisResqueInitializer.initialize_redis_and_resque( ::Rails.root.to_s, ::Rails.env.to_s )

By allowing multiple jobs to share a single socket, which is persisted over the life of the worker, this plugin is an important building block for implementing a Resque-based service send background iPhone messages via the Apple Push Notification servers.

With this gem you will be able to enqueue your emails on your Resque workers to avoid making your user wait for the email to be send when he causes an email sending action in your application. Using resque_action_mailer_backend makes email sending a breeze as you will be able to use Resque to retry failed emails, easily deliver all those marketing emails to your clients and without changing anything at your email sending code. Just tell your application to use :resque for sending emails and you're done, no need to add yet another tool just for delivering your emails if you're already using Resque for your asynchronous processing.

resque-alive adds a Kubernetes Liveness probe to a Resque instance. How? resque-alive provides a small rack application which exposes HTTP endpoint to return the "Aliveness" of the Resque instance. Aliveness is determined by the presence of an auto-expiring key. resque-alive schedules a "heartbeat" job to periodically refresh the expiring key - in the event the Resque instance can"t process the job, the key expires and the instance is marked as unhealthy.