Engine Yard As A Service
Ezra just announced a new service coming in January. They’re extracting the Engine Yard stack into an easily configurable service for booting up new Engine Yard nodes. The service is promising, even supports building nodes based on JSON. I’d expect this type of setup to replace AWS as a rails stack based on all the work Engine Yard has done on the deployment process and operations of a rails stack. The screens shown looked highly configurable, check boxes with memcached, mysql, erlang, etc. also add users, ip addresses, etc. Just about everything you would need to build a complete rails stack, with no hands.
After talking to Ezra and Vivek Engine Yard As a Service is not necessarily a web service they provide but more of a stack as a service they provide. Say you’re locked into a contract with a hosting company or you love your hosting company but they don’t know anything about building a rails stack or you’re cheap and you want cheap VPS’s, you run EYAS on your choice platform. I asked a few questions about how Engine Yard intends to go about doing this, though partnership or through an install process for the end user and it sounded like some of those things are either secret or not defined yet. Even with the specifics still a bit unclear the prospect is very exciting.
Trackbacks
Use the following link to trackback from your own site:
http://www.actsasflinn.com/trackbacks?article_id=engine-yard-as-a-service&day=18&month=11&year=2008

