Or build your application with the characteristics of the underlying platform in mind. Nobody would run a DB server on a single spindle drive since occasionally they fail. Accordingly, nobody should deploy non-multi-az AWS applications because occasionally they fail.
Except if you want to, you know, ship.
as a matter of fact, our app is using multi-zones not just for instances but also for RDS. As of now, I can't reach anything including the loadbalancer.
All I've ever heard and seen in practice is that RDS should generally be avoided for production usage. Its opaque reliance on EBS is its downfall.
Possibly but there are bigger companies using RDS in production – also, the multi-az feature had worked out better than my own custom setup. Unfortunately lack of resources prevent me from rolling out my own setup on bare metal.
Haha, I probably should. A friend of mine has already suggested I would be better off doing a PaaS startup because of my sysops skills. I always felt the market is currently too saturated. But looking at Heroku having trouble themselves, may be I should give it some serious thought.