Resque is pretty heavily used, but development seems to be stalled out at this point. In production, especially on JRuby, sidekiq is much more efficient than running a bunch of resque processes. Also, you don't need to setup a monit/god monitor for each one, you just need to run/monitor a single process. On JRuby/Rbx this single process will use all of your cores without any extra work, and will only use the memory it needs, without much waste. Also, I feel like the API for sidekiq makes a bit more sense than the one resque has, especially considering the extensions it makes to classes, actionmailer, and activerecord.
Full article: http://www.reddit.com/r/ruby/comments/14lxj8/would_an_int...
@rubyreddit
»
10 Dec '12, 4pm
@ruby_news
»
11 Dec '12, 5am
Freelancer.com (formerly GetAFreelancer) is the world's largest outsourcing and crowdsourcing marketplace for small busine...
This will show you how to write a native kernel for the IPython notebook server using node.js . For those who don't know w...
