I found engineyard very unflexible... Sure you can create custom recipes to get around that but since they update their system without warning, the custom recipes end up becoming stale...
Both EngineYard and Heroku run on top of Amazon EC2
Yes, but the problem is that they use their own gentoo based environment that they update as time go...
To do anything custom that they didn't plan beforehand, you need to create custom chef recipes that will be executed whenever a new instance is provisioned or if you deploy with their web interface (but not if you deploy with capistrano).
The problem is that it's hard to make sure that the custom chef recipes will work when the underlying environment changes and you are not told ahead of time of those changes...
Re:We're moving. Goodbye Rackspace.
by stcredzero on Tuesday November 09, 2010 @09:32AM
(#1886506)
What sort of stuff was in those recipes?
If I were doing this with a Rails app, I'd use Engine Yard for sure. Engine Yard Cloud makes stuff like load-balanced app servers and master/slave replication really easy (you can do it from the web interface), and they really know what they're doing and have tuned the stack based on that knowledge.
I don't know if there are similar offerings that are reasonably priced yet awesome for other languages though.