Re:Ask HN: What's a good, open source, distributed, worker q...
by rantfoil on Monday September 20, 2010 @02:56AM
(#1708052)
In addition, Delayed Job is also a battle-hardened/tested queue system too, with better retry / error rescuing (ironically enough). It is slower due to MySQL locking though -- Resque is built on top of Redis and is lightning fast.
We use DJ for jobs that MUST succeed (e.g. autopost) whereas we use Resque for more frequent but less essential jobs.
Re:Ask HN: What's a good, open source, distributed, worker q...
by mceachen on Monday September 20, 2010 @03:05AM
(#1708076)
We use Delayed Job at AdGrok for both for async jobs kicked off from user activity as well as nightly maintenance jobs.
If you need support for "job prerequisites", (one job to not start before other jobs have finished successfully), we'll be adding that to our fork from collectiveidea soon. The DJ codebase is pretty nice to look at, too. Note also that there are capistrano dj deployment recipes in the git source.
Re:Ask HN: What's a good, open source, distributed, worker q...
by lzw on Monday September 20, 2010 @02:44AM
(#1708031)
Looks good too. Ruby is not a problem.
I've now got multiple choices that seem like they can do the job and just need to decide which one is the best fit.
Thanks
Re:Ask HN: What's a good, open source, distributed, worker q...
by thibaut_barrere on Monday September 20, 2010 @02:39PM
(#1709990)
I second the vote for Resque: I have been amazed by how easy and stable it is.
edit: This is in Ruby though.