If you are talking about a system where a polling happens for jobs, and then the processing of the jobs happens independently, I'd suggest decoupling the two parts.
This is how I would go about it ( using AWS ) * 1 EC2 instance to do the polling. * an SQS( a queue ) into which the polling EC2 pushes jobs. * An autoscaling EC2 group which scales based on the number of jobs in the queue and processes the jobs in the queue. - Emil On 30 May 2013 08:21, Soichi Ishida <[email protected]> wrote: > thanks! Resque and Sidliq sound great! I haven't even heard about them > until now. > > -- > Posted via http://www.ruby-forum.com/. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/rubyonrails-talk/35c86d788fc02ff1f5bfa7368a99fd83%40ruby-forum.com?hl=en-US > . > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAJ%3Dox-C_Bqqbx8xwM3VP7pxwiPQoxaOfwTkNFy2gbsVvsetaig%40mail.gmail.com?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
