It looks like I will be speaking at RailsConf again. This time, I’ll be discussing asynchronous processing.
If you’ve worked on a Rails app that strays beyond basic CRUD, you’ve probably had to think about running some actions in the background – that is, outside of the HTTP request/response cycle. I’ve had to worry about this on quite a few projects, and contributed a recipe to the forthcoming Advanced Rails Recipes book. The recipe discussed how to package a Ruby script as a daemon, which is a simple and powerful approach to background processing. But there are quite a few others, including (but not limited to): AP4R, cron, starling, workling, beanstalk, backgroundrb, spawn, background_fu, and Amazon SQS. And I’ve left out quite a few.
So as I prepare for the conference, I’d love your feedback. What options have you tried? What has worked well or worked poorly? What would you like to see at the conference?
Well, seems like ActiveMessaging would make sense in that list. I use it for all sorts of asynch processing.
http://code.google.com/p/activemessaging/
Thanks, Andrew – I’ll dig into that one too. I’ve seen ActiveMessaging but haven’t used it yet. Anything to look out for?