Scaling Rails – On The Edge – Part 3

11.25.09 by Gregg Pollack

You can now watch the last episode of the three part series covering some of the newest libraries for helping you scale your Rails apps. This screencast dives into three new libraries that each can help you scale your website in a different way. We start with an introduction to rubber, an alternative to chef / chef deploy which can help you to quickly deploy a server cluster in the cloud. Then we take a look at Cloud Crowd, a completely Ruby background processor which can perform map reduce. Lastly we dive into a web service called Mad Mimi, which isn’t just useful for maintaining mailing lists, but can also host all of your app’s emails.

Scaling Rails

Download this Episode – (81.7 MB, 17:07, MP4)

In this second episode I introduce three tools:

  • rubber – A capistrano/rails plugin for deploying to Amazon ec2.
  • Cloud Crowd – Background job processor with map reduce.
  • Mad Mimi – Scale your mailing lists / campaign emails

These screencasts look great on your iPhone, so I highly encourage you to subscribe and download them on iTunes. Also, to keep up to date on the latest news in the Ruby and Rails community, be sure to check out the Ruby5 podcast if you haven’t already. Thanks!

Related posts:

  1. Scaling Rails – On The Edge – Part 1
  2. Scaling Rails – On The Edge – Part 2
  3. Ruby Call Center

8 Responses to “Scaling Rails – On The Edge – Part 3”

Comments

  1. [...] Scaling Rails – On The Edge – Part 3, awesome screencast from Envy Labs Tags: database, performance, rails, ruby, scalability, scm, text-editor Comment (RSS)  |  Trackback [...]

  2. [...] Pollack included a great review of CloudCrowd in a recent episode of his show, Scaling Rails. CloudCrowd will still be Greek to the truly non-technical readers out [...]

  3. Jeff says:

    Greg,

    First. Thx for the Scaling Rails videos. I celebrate the entire series!

    I find Rubber fascinating, but was considering some changes and would love your opinion.

    Could I simplify my cluster and reduce costs if I tweaked my Rubber deployment to use Amazon’s load balancer and Amazon’s managed MySQL. I’m fuzzy on the timeline, but I think these are relatively new AWS services that may not have been offered when Rubber was developed.

    Please advise. Thx.

Leave a Reply

* Required Fields

Additional comments powered by BackType