EngineYard - Clustered Ruby on Rails

A hosting company to keep an eye out for and one who will be part of our review is the new on the scene clustered apphost. I'm very excited to review their services and seeing what this innovative setup is capable of.

Here is the brief history of engine yard by written by Tom one of ther core developers:

It’s been 14 months since I took Rails seriously, and perhaps 18-20 months since I first heard about it. Where did the time go?

After watching the video, ordering the books from Amazon, installing on my laptop, and duplicating an existing application in less time than it took me to create it originally in Perl (my ‘native’ language at the time), I had learned the same thing that many others had learned, and many more have since learned, and many, many, many more have yet to learn.

Rails is FANTASTIC!

One of the first things that struck me about Rails, after reading the book, was that it had a really mature deployment method as its default. By this, I mean it assumed a three tier deployment architecture of HTTP server, application server, and DB server. I had spent a lot of time and energy learning that lesson in Web 1.0, so I was delighted that I wouldn’t have to roll my own this time around.

After watching 30,000+ posts to the Rails mailing list, I had an insight: While I appreciated DHH’s long term deployment goals, the community was having a much easier time writing applications than deploying them.

In fact, the deployment mechanism was so flexible that there weren’t any Rails to stay on for deployment! You could use CGI, FCGI in several versions, several web servers, including one I had never heard of with too many consonants in its name, and nobody was using Apache!

I saw an opportunity and began discussing it with my partner, Lance Walley.

Engine Yard was officially born that evening in February 2006. I began to plan the best deployment platform that I could imagine. I wanted Engine Yard to make it easy to deploy my own applications. Even though I wasn’t as many problems as other folks were having, it was still a lot of work to get a new system up and configured.

I had already begun to notice a person on the Rails mailing list with an odd name that was hard to remember and hard to forget. Ezra was answering every question I was answering, and, he was often answering more accurately and more subtly than I was. I wrote him an email and popped the question: “Would you like to help me create the ideal Rails deployment service.” Ezra said yes, he would. :-)

As Ezra said at RailsConf 2006, Engine Yard is opinionated hosting. It’s all about our opinion that Rails is great and deserves a great deployment solution. We’re anxious to see if you agree with us on this manner, and we’re working hard to get to a point where we can show it to you.

Stay tuned. We see light at the end of the tunnel. :-)