Rescuing Resque
Rails Israel Conference, Monday, November 12, 2012, 12:00

 

Resque has been plagued by issues over the past half a year due to inactivity on the project. For instance, resque doesn't handle the cleaning up workers on distributed systems like Heroku. This issue (#319) has been open for over a year. redis.rb 3.0.0 came out on May 23rd which brings improved performance and backward incompatible changes. Also due to this inactivity, other queueing libraries like Sidekiq have come up to fill the void with new features.

We'll use my story of taking over Resque as a case example for maintaining an Open Source project. I made a lot of mistakes along the way that you can hopefully avoid. Some examples include balancing pushing forward with new features and maintaining the latest stable release or getting comfortable with the prior design decisions. We'll close the talk with a roadmap to Resque and how it fits with Rails 4 and ActiveQueue.

Terence%20lee

Terence Lee

Ruby Engineer

Terence works at Heroku maintaining the Ruby stack and a slew of OSS projects such as Bundler and Resque, as well as helping with the Rails Girls movement. When he's not going to an awesome Heroku or Ruby event, he lives in Austin, TX, the taco capital of America.

(Terence loves Friday hugs, EVERY DAY OF THE WEEK! Give him a big one when you see him!)

 

 

Other Presentations at Rails Israel

Platinum
Sponsorship
Gold
Sponsorship
Media
Sponsorship