The protocol nobody asked for
2026.183Every team eventually builds a retry mechanism. They all build it during an incident. None of them write the spec first.
distributed-systems
all tags →Every team eventually builds a retry mechanism. They all build it during an incident. None of them write the spec first.
The abstractions rotate every few years. The failure modes don't.
Why static failure counts break at both ends of the traffic spectrum, and a lock-free Go circuit breaker that uses percentage-based thresholds to adapt automatically.
The three-state machine that keeps a failing dependency from taking down everything else -- with sony/gobreaker, a custom atomic implementation, and retry composition.
Cache-aside, write-through, write-behind -- and the three problems that make caching hard: stampedes, coordinated expiry, and invalidation.