3 ms·
I'm not sure even the cloud providers themselves could give you this information. In Nov 2020, AWS Kinesis Firehose went down for a few hours and took down a s
by chizhik-pyzhik 5y ago
I'm not sure even the cloud providers themselves could give you this information.
In Nov 2020, AWS Kinesis Firehose went down for a few hours and took down a slew of other services that depended on each other (Cloudwatch depends on kinesis, ec2 autoscaling and lambda depend on cloudwatch, everyone depends on ec2 and lambda...)
This was all sort of a large surprise internally that a "small" component like kinesis streams could take down so much.
https://aws.amazon.com/message/11201/ https://aws.amazon.com/message/11201/
- lgylym 5y agoIf you take into account dependencies in different regions it’s even more problematic (yes there shouldn’t be any but there usually are some)
- kevinsundar 5y agoIm sure this must be documented somewhere internally. Whenever a new region is built for AWS, services must be deployed in topologically sorted order. So I'd imagine figuring out dependencies for each service is something that comes up quite often.
- bradknowles 5y agoIt’s a hard problem to solve. Even when you think you’ve got it right, you will discover edge cases.