3 ms·
with high availability you don’t wait for an outage to spin up new resources, at that point it’s too late. it’s by definition not highly available and if you bu
by tekknik 7y ago
with high availability you don’t wait for an outage to spin up new resources, at that point it’s too late. it’s by definition not highly available and if you build infrastructure this way then you can’t blame AWS for an outage
- qaq 7y agoSo you have say 3 Region deployment are you saying that you are running 50% more instances than you need in 2 regions that are not US East to make sure you will have capacity when US East goes down :) ? I somehow seriously doubt that.
- tekknik 7y agoso you’re suggesting entire regions go down at once or one of the AZs? An entire region doesn’t go down. So again, you are not building for high availability.
- qaq 7y agoUS East as a whole went down several times plus a number of incidents when S3 or other critical services went down for the whole region.
- tekknik 7y agoi don’t remember seeing us-east go down in its entirely. show me supporting evidence or this is FUD. multiple DCs physically separated, different flood planes make up a region. it’s not easy to down an entire region. the biggest event they had, the S3 one you’re talking about, effected only 2 AZs and didn’t allow new EC2 instances to start and iirc some EC2 instances failed as well. this is a far cry from the entirely of us-east having an outage.