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.
2 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.
Avoiding fallback in distributed systems
A genuinely counterintuitive argument from AWS's own playbook: fallback logic — the code path meant to save you when the primary system fails — is often the riskier system, precisely because it almost never runs and so almost never gets tested under real conditions. I've seen this bite teams that were proud of their "graceful degradation" story; the fix argued for here is investing that same engineering effort into making the primary path more reliable instead of building a second, untested one. Changed how I run resilience design reviews.