TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

One Rogue User Took Down Our API

3 点作者 sunny--tech将近 4 年前

1 comment

theamk将近 4 年前
&gt; Unbeknownst to us, the CDN Admin service was having a real bad time. It wasn’t prepared to handle the explosive level of traffic we were sending to them, and we were teetering on the edge of their own complete outage. [...]<p>&gt; Without any end in sight, that team in charge of the Admin service did what they thought was their best option: they revoked our API token.<p>&gt; It didn’t take long before the user complaints came filing in and the status page was updated alerting users to the situation. When the team realized what our situation had spiraled into, we immediately jumped into disaster recovery mode.<p>This sounds like a total communication failure to me! They are two teams of the same company, but they behave like complete strangers!<p>The API team started flooding CDN Admin endpoint, but didn&#x27;t let them know -- couldn&#x27;t they pop in into team&#x27;s channel and let them know? And it sounds like the CDN Admin did not even try to communicate to API team before revoking their token? And even once the token was revoked, they did not let API team know ... instead API team had to look at user complains (why? wasn&#x27;t there monitoring?)<p>This is pretty sad story which shows an importance of internal communications in a company.
评论 #28132485 未加载