API Versioning Without Tears: Sunset Headers, Major Versions, and a Go Implementation
Sooner or later every API team hits the wall: a client depends on behavior you need to change. The field
Tag: system-design
Eventual Consistency in Practice: Session Guarantees, Read-Your-Writes, and Bounded Staleness
Replica lag is one of those distributed-systems facts everyone accepts in the abstract and nobody plans for in the code.
Load Balancing Beyond Round Robin: Least Outstanding Requests and Consistent Hashing
Here is a failure mode that shows up in every system with more than two backends: round robin distributes requests
Continue readingLoad Balancing Beyond Round Robin: Least Outstanding Requests and Consistent Hashing
LLM Routing and Cascading: Send Every Query to the Cheapest Model That Can Handle It
If you run a large language model behind a product, you have probably internalized an uncomfortable trade-off. The big frontier
Continue readingLLM Routing and Cascading: Send Every Query to the Cheapest Model That Can Handle It
Cursor-Based Pagination Done Right: Keyset Queries, Opaque Cursors, and the Pitfalls That Bite
Every API that returns a list eventually has to answer the same question: how do you hand out a million
API Versioning Strategies: Path vs Header, Calendar Dates, and Graceful Sunsets
Every API you ship is a promise. Clients hardcode your URLs, parse your field names, and schedule work around your
Continue readingAPI Versioning Strategies: Path vs Header, Calendar Dates, and Graceful Sunsets
Zero-Downtime Database Migrations: Expand-Contract, Backfills, and Locks
Every schema migration tool will happily tell you how to change a table. Almost none of them will tell you
Continue readingZero-Downtime Database Migrations: Expand-Contract, Backfills, and Locks
Native Sidecar Containers in Kubernetes: Ordering, Jobs, and the End of Shutdown Races
The sidecar pattern has been part of the Kubernetes toolkit for as long as pods have existed: run a second
Circuit Breakers in Go: Stopping Cascading Failures Before They Start
Every distributed system has a breaking point. The downstream service you depend on will fail — not “might” fail, will
Continue readingCircuit Breakers in Go: Stopping Cascading Failures Before They Start
CQRS and Event Sourcing in Go: Building Systems That Remember Every Decision
Most CRUD applications follow a predictable pattern: a single database table serves both reads and writes, the same model validates
Continue readingCQRS and Event Sourcing in Go: Building Systems That Remember Every Decision