Outside.in Scales Up with Engine Yard and moving from PHP to Ruby on Rails

This article explains how Outside.in, the local social network and aggregator, scaled up its service and moved from PHP to Ruby on Rails (they moved maybe because Ruby code seemed to be more maintanable that PHP code?).

The whole article is here on EngineYard blog.

Comments

Re: Outside.in Scales Up with Engine Yard and moving from PHP to

What? That case study reads more like a sales pitch than an informative article. I didn't learn a single thing about migrating from PHP to Ruby on Rails.

It was a migration of convenience

It seems they switched to Ruby on Rails because they could....essentially facing a rebuild from spaghetti PHP code, what are your options? Seems to be they could have easily stayed on PHP and gone with a better framework and architecture too. Or am I missing something?

Seems like an interesting horse race nowadays among Ruby on Rails, Python and Django, and PHP and CodeIgniter.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd><div ?=?><p ?=?> <img ?=?><h1 ?=?><h2 ?=?><h3 ?=?>
  • Lines and paragraphs break automatically.
  • Glossary terms will be automatically marked with links to their descriptions
  • You may link to webpages through the weblinks registry

More information about formatting options

To combat spam, please enter the code in the image.