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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

The 4 Minute Bug

50 点作者 kinduff超过 2 年前

3 条评论

krallja超过 2 年前
Love it. This reminds me somewhat of a similar issue I saw in 2012, where Cheezburger.com went down over Thanksgiving weekend because we had no deploys for more than 80 hours, and an accidental per-server cache filled up in about that much time. <a href="https:&#x2F;&#x2F;jacob.jkrall.net&#x2F;turkey-day-down-time" rel="nofollow">https:&#x2F;&#x2F;jacob.jkrall.net&#x2F;turkey-day-down-time</a>
评论 #33021369 未加载
pachico超过 2 年前
It looks to me like a bad architected solution...<p>If you have a background job to update data, there is no need to do any TTL. If we&#x27;re speaking about currency exchange, you might prefer to store a transactional history of exchanges, together with the current one, and populate a fast read model too (Redis) with a failover against the oltp version...<p>Maybe it&#x27;s just me.
评论 #33023168 未加载
javier_e06超过 2 年前
The story falls on the category of &quot;it won&#x27;t happen until it happens&quot;. Testing is expensive and even with all the testing in advance we observe emergent behaviors that make us run to the reams of logs to ask the very simple question: &quot;What happened?&quot; My take away: If you have to fail, because you will, fail graciously. Good post.
评论 #33023143 未加载