4 ms·
The systematic failure is on: - people using us-east-1 when it has been shown to be the most problematic AWS region - companies building shitty applications a
by lykr0n 6y ago
The systematic failure is on:
- people using us-east-1 when it has been shown to be the most problematic AWS region
- companies building shitty applications and devices that require the cloud to function and not considering what happens when the cloud/internet is down
- people assuming the cloud can't/won't go down or have issues between the end user and the server
These types of events will continue to happen, so for the love of god stop using us-east-1
- ipsocannibal 6y agoAWS should just pay people to move to us-east-2. It would be better for both them and their customers.
- ljm 6y agoThen everyone moves to the next-cheapest region and the cycle repeats.
- freehunter 6y agoI live in Michigan and I’ve used us-east-2 since it became available. Not only is Ohio right next door, but it’s also closer to the mean center of the US population (which is currently in Missouri). I don’t know if it’s actually measurably faster for West cost folks, but my application is used mostly in the Midwest and only a little on the coasts so it makes sense for me, but might be a good choice for coast-to-coast companies too.