feat(sreweekly): 新增第 536 期文章导出(html/markdown/articles 8 篇)并更新 manifest
This commit is contained in:
96
sreweekly/html/536-2026-09-28.html
Normal file
96
sreweekly/html/536-2026-09-28.html
Normal file
@@ -0,0 +1,96 @@
|
||||
<p><a class="email_only" href="https://sreweekly.com/sre-weekly-issue-536/">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/536">Planetscale</a>:</h2>
|
||||
<p>PlanetScale is headed to SREcon26 in Dublin this October. Swing by our booth to grab some merch, catch a live demo, and chat with the team behind the world’s fastest databases. We can’t wait to see you there.</p>
|
||||
<p>→ If you’re not at SREcon but still want to learn how PlanetScale can reliably scale your databases, <a href="https://sreweekly.com/link/536"><u>get in touch.</u></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://surfingcomplexity.blog/2026/08/29/omnipresent-availability-risks-in-cloud-software/" target="_blank">Omnipresent availability risks in cloud software</a></div>
|
||||
<div class="sreweekly-description">
|
||||
<p>Common threads seen across incident write-ups from many companies.</p>
|
||||
<p> <small>Lorin Hochstein</small></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="sreweekly-entry">
|
||||
<div class="sreweekly-title"><a href="https://itnext.io/how-we-built-real-time-stock-pricing-at-mofid-brokerage-031015ce1301" rel="noopener" target="_blank">How We Built a Real-Time Stock Pricing System at Scale</a></div>
|
||||
<div class="sreweekly-description">
|
||||
<blockquote>
|
||||
<p>How we built a production architecture handling 1,900+ messages per second and tens of thousands of concurrent connections with Kafka, Redis Pub/Sub, .NET Channels, and SSE.</p>
|
||||
</blockquote>
|
||||
<p> <small>Mohsen Rajabi — ITNEXT</small></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="sreweekly-entry">
|
||||
<div class="sreweekly-title"><a href="https://techgenyz.com/background-jobs-backend-architecture/" target="_blank">Master Background Jobs With Smarter Queue Architecture and Reliability</a></div>
|
||||
<div class="sreweekly-description">
|
||||
<p>This is a thorough tour of the design decisions that separate a background job system that works in development from one that survives production.</p>
|
||||
<p> <small>Shreshtha Saha — Techgenyz</small></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="sreweekly-entry">
|
||||
<div class="sreweekly-title"><a href="https://www.reddit.com/r/sre/comments/1wguk7p/can_automated_root_cause_analysis_reliably/" target="_blank">r/sre: Can automated root cause analysis reliably identify production issues? </a></div>
|
||||
<div class="sreweekly-description">
|
||||
<p>This question kicked off a great comment section:</p>
|
||||
<blockquote>
|
||||
<p>Has anyone gotten an automated RCA setup to actually nail root cause without a person doing the final synthesis, or is that still mostly aspirational marketing from vendors? </p>
|
||||
</blockquote>
|
||||
<p> <small><a href="https://www.reddit.com/user/Acrobatic_Refuse8100/">u/Acrobatic_Refuse8100</a> and many others — reddit</small></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="sreweekly-entry">
|
||||
<div class="sreweekly-title"><a href="https://surfingcomplexity.blog/2026/08/29/quick-thoughts-on-github-actions-aug-26-incident/" target="_blank">Quick thoughts on GitHub Actions Aug 26 incident</a></div>
|
||||
<div class="sreweekly-description">
|
||||
<p>Do you have a way to slow down traffic to your database during an incident? This one has a great explanation of why you need one.</p>
|
||||
<p> <small>Lorin Hochstein</small></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="sreweekly-entry">
|
||||
<div class="sreweekly-title"><a href="https://arpio.io/https-arpio-io-your-agent-is-not-prodution-ready-until-it-can-recover/" target="_blank">Your agent is not production-ready until it can recover</a></div>
|
||||
<div class="sreweekly-description">
|
||||
<p>Through a fictitious case study, this article shows how to go about building a reliable service with an agentic component.</p>
|
||||
<p>FYI the last ~quarter or so is a sales pitch, but the preceding majority of the article isn’t.</p>
|
||||
<p> <small>Arpio</small></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="sreweekly-entry">
|
||||
<div class="sreweekly-title"><a href="https://storiesfromtheedge.substack.com/p/rollback-does-not-erase-distributed" target="_blank">Rollback Does Not Erase Distributed Memory</a></div>
|
||||
<div class="sreweekly-description">
|
||||
<p>Rollback sounds great in theory, but it doesn’t always work. The CircleCI example really hits hard.</p>
|
||||
<p>This reminds me of a classic article from the now-defunct company Skyliner, <a href="https://web.archive.org/web/20181118140222/https://blog.skyliner.io/you-cant-have-a-rollback-button-83e914f420d9?gi=43cf0516912">You Can’t Have a Rollback Button</a>.</p>
|
||||
<p> <small>Balu Kambala</small></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="sreweekly-entry">
|
||||
<div class="sreweekly-title"><a href="https://planetscale.com/blog/the-architecture-of-neki" target="_blank">The architecture of Neki</a></div>
|
||||
<div class="sreweekly-description">
|
||||
<p>Yes, this is a walkthrough of a vendor’s product, but the architecture is genuinely interesting and it reads like an engineering explainer rather than a sales pitch. I especially liked the wrinkle where one shard has to be designated authoritative so that custom type OIDs stay consistent across the whole cluster.</p>
|
||||
<p> <small>Harshit Gangal — PlanetScale</small></p>
|
||||
<p> <small><em>This article is published by this issue’s sponsor, but their sponsorship did not influence its inclusion in the newsletter.</em></small></p>
|
||||
</div>
|
||||
</div>
|
||||
</div></div>
|
||||
Reference in New Issue
Block a user