Architecture & Systems
Microservices, distributed systems, service boundaries, scalability, reliability
-
Your consumer’s headroom is a staleness budget
Moving a call onto a log does not remove the coupling between two services. It moves the coupling into time, and the consumer’s spare capacity decides how much time. Take a chat app, a…
-
Your Retry Policy Is a Capacity Limit You Cannot See
Retries and hedges cut tail latency on a normal day. Each one also sets a load above which the service cannot recover from a short stall, and no dashboard shows it. Take two copies…
-
When Two Services Cannot Deploy Without Each Other
Repair it, merge it, or write down why you are doing neither. A service boundary should keep paying rent. The release runbook says deploy A, wait for validation, deploy B, verify together. It has…
-
Five Signals a Service Boundary Has Stopped Paying Rent
And what each one actually points at, which is rarely a merge. Picture two services, one team, separate pipelines for three years. Latency is fine. Neither is a hub. They fail independently, mostly. Then…



