...and increased our flexibility and outage-proofing in the process
A few weeks ago, we moved
PlanForCloud from Heroku, an-all-in-one PaaS, to managing it with RightScale. It was a smooth migration and we're very happy with our shiny new home in RightScale. In terms of cloud infrastructure, we're still using AWS, we've moved from a Ruby PaaS hosted by Heroku in US-East to an IaaS, and we chose US-West Oregon (with RightScale you can deploy to any cloud).
We used Heroku for our first year in operation and found it pretty good, however, we got to a stage where we started to outgrow Heroku. We wanted:
- More Flexibility: ability to customise our stack, fine-tune our app's deployment process, get more visibility of our app's performance and be able to select instance types for different parts of our app. For example, we want to use high-CPU instances for our background worker processes.
- Outage-Proofing: on Heroku, there is nothing you can do about outages; if Heroku has issues, you'll have issues, and you just have to wait for them to fix it. This is something we faced a few times in which the AWS US-East region had an outage and our entire app went down with it. With RightScale, we can control our deployment to a finer extent and can set up disaster recovery procedures which kick in as soon as any cloud outages happen.
Step By Step From Heroku to RightScale