5 ms·
These things happen to every datacentre. That’s why AWS has multiple, separately managed regions that you can use to keep your app up with.
by kondro 9y ago
These things happen to every datacentre. That’s why AWS has multiple, separately managed regions that you can use to keep your app up with.
- memer 9y agoand pay double? no way
- frakkingcylons 9y agoEnjoy your downtime then.
- kondro 9y agoHardware will always fail at some point. You can either add extra resources elsewhere, or deal with that inevitable downtime. Both are reasonable, depending on the impact of downtime.
- cratermoon 9y agoIt's not paying double. Take the total number of instances serving the app and divide them across data centers and availability zones within datacenters. This might require adding a few of servers if the app is replicated across a very small number of instances, but for apps that already have a significant number of instances to handle the capacity, it's just a matter of rearranging things. Depending on how quickly new instances of the app can be brought up to, it may be worthwhile to run a bit more capacity so that the remaining instances don't melt down should all the instances in one zone become unavailable.
- thalesac 9y agoThat's why my aws console wasn't working properly this afternoon. It seems that Amazon is not using it's services correctly
- ggggvg 9y agoNonsense. The console is hosted out of us-east-1. Also, please learn to spell before posting. Thanks.
- bklyn11201 9y agoBut AWS has the concept of availability zones that they equate to a data center. AWS refers to an AZ as an "isolated location". It's becoming clear with the S3 outages and this outage that isolation is not as robust as expected so now we see more reference to cross-region replication. But unlike cross-AZ services like S3 or DynamoDB, you need to build your own cross-region replication and failover.
- paulddraper 9y agoYep. My take: humans fail at more than hardware does, and AWS takes a lot of action per region.