High(er) Reliability Software Patterns for Go
summary
Shows a concrete pattern: add go-by-contract pre/post checks for API calls, run reverse proxy contracts that defer postconditions, and send violations to Sentry reporting instead of panicking in production. Demonstrates a real integrity bug (duplicate usernames) and a working proxy implementation that catches the violation without crashing clients, controlled by an env var (DON'T_PANIC=true). Also contrasts practical tradeoffs and references formal-verification examples like Tokeneer and Ada systems.
AI-written summary · about
chapters (8)
- 0:00High reliability background
- 1:10Software safety risks
- 2:57Engineering reliable systems
- 5:57Design by contract concepts
- 7:39Implementing contracts
- 10:41Production contract strategies
- 13:57API integrity at scale
- 17:36Q&A on software reliability








