Articles
Worth reading
A short take on pieces worth your time — architecture, AI, system design, and engineering careers — each one linked back to its original source.
3 articles
How Netflix Simplified Batch Compute with Kueue
A concrete look at how Netflix simplified its batch compute stack by adopting Kueue, the Kubernetes-native job queueing system, instead of maintaining a bespoke scheduler layer on top of it. It's a good case study in a pattern I see a lot in mature platform teams: replacing homegrown infrastructure with an increasingly capable open-source primitive once the ecosystem catches up to what you built out of necessity years earlier. Useful if you're running batch or ML workloads on Kubernetes and wondering whether you still need your own queueing layer.
Cloudflare outage on November 18, 2025
Matthew Prince's own postmortem of the outage that took down a meaningful chunk of the internet for several hours, X, ChatGPT, and Cloudflare's own status page among the casualties, and the root cause is almost mundane: a database permissions change caused a bot-management "feature file" to double in size and blow past a hardcoded limit. It's a good reminder that the scariest outages rarely come from novel attacks; they come from ordinary config changes interacting badly with an assumption nobody revisited. Prince's willingness to publish the gory detail, including where their own tooling made diagnosis slower, is what makes this worth reading over a sanitized summary.
Monitoring Distributed Systems
The Google SRE book chapter, written by Rob Ewaschuk and edited by Betsy Beyer, that introduced the "four golden signals": latency, traffic, errors, and saturation, as the minimum viable dashboard for any user-facing service. What's held up is the discipline behind it: pick a small number of signals you'll actually look at during an incident instead of a wall of graphs nobody reads at 3am. I still use this as the starting checklist whenever I'm setting up monitoring for a new service.