gdp's Comments

Union Station : 5 Tips for Deploying Background Jobs in Ruby on Rails

Tue, 20 Oct 2009 20:25:35 +0000

Hey Todd, There isn't anything special that should be required. There is logic in most of the libraries to handle multiple hosts processing jobs. The main thing to remember is that they need to be deployed on the same code base and utilize the same database (since this is where the jobs live and are locked). For instance we have a number of customers using BJ configured to run under cron on multiple slices. Additionally we have customers running DJ (workers) on multiple slices. The setup is the same each time.

Union Station : 5 Tips for Deploying Background Jobs in Ruby on Rails

Tue, 11 Aug 2009 21:39:50 +0000

I just review the commit logs and look at the code itself. Also you can always hop on irc (irc.freenode.net) and talk to the author(s).

Union Station : 5 Tips for Deploying Background Jobs in Ruby on Rails

Tue, 11 Aug 2009 21:38:45 +0000

Hey Sav, I'd suggest the main issues with BackgrounDRB are around memory leaks and process control. Re a table of pros and cons -- sounds like a good idea for a future blog post :)

Union Station : 5 Tips for Deploying Background Jobs in Ruby on Rails

Tue, 11 Aug 2009 18:50:27 +0000

I'm not aware if Tobias is still maintaing or not. I think with all the forks the "masses" are choosing at will. Collectiveidea and Weplay have pretty active forks on GH with some good patches (http://github.com/collectiveidea/delayed_job and http://github.com/weplay/delayed_job). Looks like there is a good opportunity for someone to step in and help here :)