title: Managing different resque queues on multiple servers
body: <p>I am currently using <a href="https://github.com/defunkt/resque" rel="nofollow">Resque</a> for dealing with background jobs in my application. Now i have 5 different queues at present (it ll grow very fast). Each of them is doing works like updating Solr indexes, Real-time Notification ,scheduled newsletters, delayed emails &amp; SMS. And currently am using Resque as a rails gem and running the Resque from rails environment.</p>
  
  <p>Now i am planning to move Solr index update task and scheduled newsletters to  different server since these two performing heavy operations. One approach is just copy the rails directory to the new server and run the Resque jobs from the rails environment. But i am not comfortable doing this.</p>
  
  <p>Another one is creating a seperate rake app for resque tasks. But the problem is, both these tasks are heavily tied to rails models and rails templating. I am totally unsure how to proceed next.</p>
  
  <p>Has anyone faced the similar problem, and how you architected the application?</p>