In short, Gearman is multi-language, multiple different backends, possible to do RPC-style synchronous processing. Resque and friends[1] are single-language, exclusively async, but also extremely transparent because they're just JSON blobs in redis. Resque has a huge following as well.
[1]: https://github.com/defunkt/resque/wiki/alternate-implementat...
In Gearman, an open source framework for distributed processingdefunkt
resque
OPEN SOURCE2010–2012
defunkt / resque
resque
Moved to resque/resque
10Distinct people
11Mentions
0Explicit recommenders
57GitHub stars
What to know before exploring
What it is
Moved to resque/resque
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 7:02:26 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year11 dated mentions
Observed mentions: 2010-01-22 12:31:59 UTC to 2012-11-15 20:02:06 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2010 | 2010-01-01 00:00:00 UTC | 2011-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2011 | 2011-01-01 00:00:00 UTC | 2012-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 3 | 0 | 3 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
What Hacker News says
2 sourcesA quick tip would be to run everything process intensive in the backend, don't waste frontend resources with API calls, data processing etc, got something that takes more than 200ms to run, place it in a job que and do the processing later.
Some tools for the job:
https://github.com/defunkt/resque
https://github.com/tobi/delayed_job
Also don't forget to cache. You shouldn't worry too much if you do these two properly.
In Ask HN: Where/How can I learn more about general webapp maintenance?