5 ms·
I am currently using Resque(http://github.com/defunkt/resque http://github.com/defunkt/resque) for a similar requirement. You might want to check it out. edit:
by hsuresh 16y ago
I am currently using Resque(http://github.com/defunkt/resque http://github.com/defunkt/resque) for a similar requirement. You might want to check it out.
edit: This is in Ruby though.
- lzw 16y agoLooks 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
- thibaut_barrere 16y agoI second the vote for Resque: I have been amazed by how easy and stable it is.
- rantfoil 16y agoIn 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.
- mceachen 16y agoWe 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.