On Sun, Aug 16, 2009 at 1:44 AM, Ricardo S.
RightScale is good solution but very expensive, a cheaper alternative
is using Scalr (scalr.net)
and they have both a free version (open source) as well as a paid
service (scalr.net being
the paid service, only $50/month + Amazon fees).
Actually, the current charge for scalr.net is $99 per/month + Amazon
charges. The $50 per/month
was before August 16th. Also, Rightscale has a developer edition that
give you the opportunity
to tryout their services.
Both RightScale and
Scalr are considered
cloud management tools and they work very well with Amazon Web
RightScale feature set is richer than Scalr.
Also, Scalr.net recently graduated from beta to production on August 1,
2009. Also, I wish that I would
have known that one of the founders members, Alexey Kovalyov, resides in
Ukraine because I was
there back in October 2008 and it would been a pleasure to meet him.
You should keep in mind that Amazon is not the only kid in the game
(in the PaaS - platform
as a Service). There is also GoGrid and Rackspace (with their cloud
Finally, there is a new breed of rails hosting solutions: Heroku and
Heroku has some very excellent hosting solutions from what I have
heard from others and what appears on their site. Also, the hosting
from what I hear is dead simple.
rails deployment. If you want to deal the least with server
configuration, I would strongly suggest
a service like Heroku (they even have github integration). I havent
used EngineYard’s but their
Solo offering seems quite good for development/testing as well. The
moment you need production-ready
features then you have to start paying for more in both Heroku/
Yes, I would agree with Ricardo in this regard but you want to limit
developing/testing to the local platform because some of these services
have per/hour usage fees. The plan that I have with Rightscale has
15000 hours/per month for $500 which is great for deploying several
applications per month. Thus, when I test a new application or updat
an existing application, I tend to do the following:
a) start the instance
b) test the application
c) stop the instance
Note: The above doesn’t affect the following application because I tend
to create a staging instance for testing both new and updates