Why another queuing library?

Submitted by Ezekiel Templin 2011-10-20 07:20:24 UTC
Source:  http://opensoul.org/blog/archives/2011/10/19/why-another-queuing-library/

Referenced projects

Resque

Resque is a Redis-backed Ruby 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 is comprised of 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.

Rubygem resque

Total Downloads
4739687
Releases
63
Current Version
1.25.2
Released
2014-03-04 00:00:00 UTC
First Release
2009-11-03 11:00:00 UTC

Github resque/resque

Watchers
6492
Forks
1209
Development activity
Less active
Last commit
2015-04-14 12:16:10 UTC

Redis Ruby

A Ruby client that tries to match Redis' API one-to-one, while still providing an idiomatic interface. It features thread-safety, client-side sharding, pipelining, and an obsession for performance.

Rubygem redis

Total Downloads
12221008
Releases
49
Current Version
3.2.1
Released
2015-02-11 00:00:00 UTC
First Release
2009-06-10 03:00:00 UTC

Github redis/redis-rb

Watchers
2065
Forks
402
Development activity
Active
Last commit
2014-12-11 04:05:36 UTC

qu

a Ruby library for queuing and processing background jobs with configurable backends.

Rubygem qu

Total Downloads
19993
Releases
6
Current Version
0.2.0
Released
2012-06-13 00:00:00 UTC
First Release
2011-09-23 04:00:00 UTC
Depends on following gems
Depending Gems
12

Github bkeepers/qu

Watchers
497
Forks
45
Development activity
Less active
Last commit
2014-11-17 14:28:19 UTC
×

In order to continue, you must be signed in using your Github account.

If you're signing in using this account for the first time Github will ask for your permission to give access to your public user data to the Ruby Toolbox.

Although the Github Authorization page does not mention it, the request includes read-only access to your verified email address (user:email OAuth scope). This is neccessary so there's a way to notify you about comments, information about your accepted project edits and the like. You can review your notification settings on your account page once you're signed in.