Re:Incident at Slack
by zht on Wednesday March 09, 2022 @08:46AM
(#30614317)
this sounds very complicated lol
[ Parent
| on HN ]
Re:Incident at Slack
by sharklazer on Wednesday March 09, 2022 @09:11AM
(#30614543)
No, not really. If your calls time out, ping the status server. Done.
It sounds more like laziness than complication to me. But that typifies Slack dev culture—“just use duct tape”
And that's exactly how you DDOS your status server.
Re:Incident at Slack
by matthew-wegner on Wednesday March 09, 2022 @10:28AM
(#30615499)
Why can't they put a status.json file on S3/CloudFront/R2/wherever?
And in an absolute worst-case infra collapse, someone there could manually edit/upload a new one...
Re:Incident at Slack
by charcircuit on Wednesday March 09, 2022 @03:44PM
(#30619718)
Put a CDN in front of the status server. If that overwhelms your CDN then add some exponential back off to the mix.