feat(sreweekly): 新增 533 期 HTML 与 532 期译文,更新 manifest;附带 youtube-transcript 转录输出
This commit is contained in:
97
sreweekly/html/533-2026-09-07.html
Normal file
97
sreweekly/html/533-2026-09-07.html
Normal file
@@ -0,0 +1,97 @@
|
||||
<p><a class="email_only" href="https://sreweekly.com/sre-weekly-issue-533/">View on sreweekly.com</a></p>
|
||||
|
||||
<div class="sreweekly-sponsor-message" style="border: 1px solid #b0b0b0; width: 80%;">
|
||||
<h2 style="text-align: center; font-size: 80%; color: #909090;">A message from our sponsor, <a href="https://sreweekly.com/link/533">Planetscale</a>:</h2>
|
||||
<p>Most database incidents start with one expensive query, not the database being down. PlanetScale gives SRE teams high-availability Postgres and MySQL with automated failover, query insights, and Database Traffic Control to stop runaway queries before they page you.</p>
|
||||
<p><a href="https://sreweekly.com/link/533">→ Explore PlanetScale</a></p>
|
||||
</div>
|
||||
|
||||
|
||||
<div class="wp-block-group"><div class="wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow">
|
||||
<div class="sreweekly-entry">
|
||||
<div class="sreweekly-title"><a href="https://greatcircle.com/blog/2026/08/04/detection-gap/" target="_blank">Incidents start before the response does</a></div>
|
||||
<div class="sreweekly-description">
|
||||
<p>What can you do to shorten the time to detect an incident? Some great ideas in here, especially monitoring your company’s main web page for a sudden uptick in traffic.</p>
|
||||
<p> <small>Brent Chapman</small></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="sreweekly-entry">
|
||||
<div class="sreweekly-title"><a href="https://surfingcomplexity.blog/2026/08/16/quick-thoughts-on-azure-regional-outage-from-july-23-26/" target="_blank">Quick thoughts on Azure Regional Outage from July 23, ’26</a></div>
|
||||
<div class="sreweekly-description">
|
||||
<p>What an interesting incident! I recommend reading Azure’s write-up before reading Lorin’s excellent analysis.</p>
|
||||
<p> <small>Lorin Hochstein</small></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="sreweekly-entry">
|
||||
<div class="sreweekly-title"><a href="https://dzone.com/articles/distributed-databases-coordination" target="_blank">Why Distributed Databases Fail at Coordination Boundaries</a></div>
|
||||
<div class="sreweekly-description">
|
||||
<blockquote>
|
||||
<p>Distributed databases rarely fail in the clean, isolated ways described by component diagrams. They fail through timing gaps, stale metadata, ambiguous ownership, retry storms, incompatible health decisions, and overlapping maintenance activity.</p>
|
||||
</blockquote>
|
||||
<p> <small> Varsha Ganesh — DZone</small></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="sreweekly-entry">
|
||||
<div class="sreweekly-title"><a href="https://read.zerosevzero.com/p/the-record-says" target="_blank">The Record Says</a></div>
|
||||
<div class="sreweekly-description">
|
||||
<p>I love this concept of a “political incident”:</p>
|
||||
<blockquote>
|
||||
<p>The subject was political incidents, by which I mean the ones where the severity arrives before the impact assessment does.</p>
|
||||
</blockquote>
|
||||
<p>And ouch, I felt this bit:</p>
|
||||
<blockquote>
|
||||
<p>You have spent forty minutes of the incident on the severity field.</p>
|
||||
</blockquote>
|
||||
<p> <small>Tim Irving</small></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="sreweekly-entry">
|
||||
<div class="sreweekly-title"><a href="https://hackernoon.com/what-sres-should-automate-and-never-automate-with-ai" target="_blank">What SREs Should Automate — and Never Automate — with AI</a></div>
|
||||
<div class="sreweekly-description">
|
||||
<p>Where can you safely use LLM agents, versus when you should keep things in human hands? This one has some good criteria to consider.</p>
|
||||
<p> <small>Sai Joshitha Kathari — HackerNoon</small></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="sreweekly-entry">
|
||||
<div class="sreweekly-title"><a href="https://www.datadoghq.com/blog/engineering/gitretriever/" target="_blank">20× the CI traffic without getting slower: How we rebuilt Git serving at Datadog</a></div>
|
||||
<div class="sreweekly-description">
|
||||
<p>I learned a lot about Git while reading this one. Speeding up Git clones in CI may not seem important, but it will when you’re trying to roll out a fix during an incident.</p>
|
||||
<p> <small>Mike Thompson and Daniel Esponda — Datadog</small></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="sreweekly-entry">
|
||||
<div class="sreweekly-title"><a href="https://netflixtechblog.com/a-tale-of-two-flink-autoscalers-e9f6a1b1492b" target="_blank">A Tale of Two Flink Autoscalers</a></div>
|
||||
<div class="sreweekly-description">
|
||||
<p>Switching from their custom-written autoscaler to the new off-the-shelf option made sense, but it wasn’t a simple drop-in replacement.</p>
|
||||
<p> <small>Samuel Yeboah, Francesco Di Chiara and Mingliang Liu — Netflix</small></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="sreweekly-entry">
|
||||
<div class="sreweekly-title"><a href="https://www.adaptivecapacitylabs.com/2026/08/24/there-is-more-to-code-review-than-automatable-detection/" target="_blank">There is more to code review than (automatable) detection</a></div>
|
||||
<div class="sreweekly-description">
|
||||
<p>Can we replace human code review with LLM-based reviews? This article lays out what an LLM can’t replicate, and I’d argue that these are the pieces that matter most for reliability.</p>
|
||||
<p> <small>John Allspaw — Adaptive Capacity Labs</small></p>
|
||||
</div>
|
||||
</div>
|
||||
</div></div>
|
||||
Reference in New Issue
Block a user