I thought the whole point of AWS that it was a distributed system with no one point of failure? In that case, how did it have an outage?
do they not teach people what a failure domain is anymore? https://en.wikipedia.org/wiki/Failure_domain Clouds aren't magic. They require a certain amount of operational confidence in order to understand that, yes, an entire region can fall out from under you at any time and it's your responsibility to detect and deploy into an unaffected region if possible. edit: Generally, one entire region will not fail. However,…
Amazon packages pile up after AWS outage spawns delivery havoc
31–40 of 219 posts
Re: Amazon packages pile up after AWS outage spawns delivery havoc
#32I thought this story was about this house x-) "Neighbors in Tennessee city worry as Amazon packages pile up outside home" https://www.youtube.com/watch?v=qVQjEB2sxBw
When a residential house becomes a review farm.
Re: Amazon packages pile up after AWS outage spawns delivery havoc
#33Re: Amazon packages pile up after AWS outage spawns delivery havoc
#34Earlier quoted context omitted.
why wouldn't they?
Because it's terrible and has always been terrible? After 2017 I'll never use US-east-1 again. Hell... I should have learned that particular lesson in 2011 but it took two catastrophic failures for me to figure it out. There are numerous threads here on HN covering the topic "why does US-east-1 suck so hard." https://news.ycombinator.com/item?id=13756082 is just one example.
Re: Amazon packages pile up after AWS outage spawns delivery havoc
#35Re: Amazon packages pile up after AWS outage spawns delivery havoc
#36I thought the whole point of AWS that it was a distributed system with no one point of failure? In that case, how did it have an outage?
do they not teach people what a failure domain is anymore? https://en.wikipedia.org/wiki/Failure_domain Clouds aren't magic. They require a certain amount of operational confidence in order to understand that, yes, an entire region can fall out from under you at any time and it's your responsibility to detect and deploy into an unaffected region if possible. edit: Generally, one entire region will not fail. However,…
There are also way too many successful, public cloud-native businesses running without any semblance of a Business Continuity or DR Plan among any of their teams. I wish I could name and shame some of the more egregious cases I have seen.
Re: Amazon packages pile up after AWS outage spawns delivery havoc
#37Re: Amazon packages pile up after AWS outage spawns delivery havoc
#38I thought the whole point of AWS that it was a distributed system with no one point of failure? In that case, how did it have an outage?
do they not teach people what a failure domain is anymore? https://en.wikipedia.org/wiki/Failure_domain Clouds aren't magic. They require a certain amount of operational confidence in order to understand that, yes, an entire region can fall out from under you at any time and it's your responsibility to detect and deploy into an unaffected region if possible. edit: Generally, one entire region will not fail. However,…
Empirically? No.
But seriously, instead of making every dev team consuming an AWS product hire the extra engineers required to build a system that spans multiple failure domains — which lets be honest, companies won't — why hasn't Amazon just hired the engineers required to do it for me?
> Generally, one entire region will not fail.
Laughs in global failures.
Re: Amazon packages pile up after AWS outage spawns delivery havoc
#39Re: Amazon packages pile up after AWS outage spawns delivery havoc
#40Earlier quoted context omitted.
Region outages happen, which is why the guidance is to build in multiple regions, but even Amazon sometimes doesn't take their own advice. Sometimes the reason is good, sometimes it isn't.
I thought the guidance was to be multi-AZ, as an AZ is the failure boundary?