3 ms·
It's fun watching their list of "Affected Services" grow literally in front of your eyes as they figure out how many things have this dependency. It's still mi
by kalleboo 1y ago
It's fun watching their list of "Affected Services" grow literally in front of your eyes as they figure out how many things have this dependency.
It's still missing the one that earned me a phone call from a client.
- zenexer 1y agoIt's seemingly everything. SES was the first one that I noticed, but from what I can tell, all services are impacted.
- deleted 1y ago[deleted]
- hvb2 1y agoIn AWS, if you take out one of dynamo db, S3 or lambda you're going to be in a world of pain. Any architecture will likely use those somewhere including all the other services on top. If in your own datacenter your storage service goes down, how much remains running
- goatking 1y agoAgreed, but you can put EC2 on that list as well
- mlrtime 1y agoWhen these major issues come up, all they have is symptoms and not causes. Maybe not until the dynamo oncall comes on and says its down, then everyone knows at least the reason for their teams outage. The scale here is so large they don't know the complete dependency tree until teams check-in on what is out or not, growing this list. Of course most of it is automated, but getting on 'Affected Services' is not.
- hbn 1y agoI know Postman has kinda gone to shit over the years but it's hilarious my local REST client that makes requests from my machine has AWS as a dependency . I found that out about Plex during an outage too.