duo-production-reliability

How to know what production is actually doing, and what to run when it breaks — extracted from Duolingo's engineering blog and made portable to any product. Covers always-on request identity versus sampled tracing, runtime dead-code detection, kill switches that fail open, automatic repair of state users earned, incident command for long-running incidents, dogfooding gates, zero-friction bug intake and feedback aggregation, datasets treated as production software, and continuous quality and security verification. Use when someone asks why is production slow for this one customer, how do we find dead code, what should our kill switch look like, how do we run an incident that lasts all day, how do we compensate users after an outage, should we gate the release on internal telemetry, or why are our bug reports useless.

Version

2.0.0

License

MIT