Observability Driven Development
summary
Argues for testing in production and building observability to run real experiments: deploy A/B experiment with 50 blue variants (Google) and measure clicks, shadow new logic with the open‑source scientist pattern, and use feature-flag ring rollout to enable/disable risky releases. Recommends logs → metrics → distributed traces (Zipkin) to answer why a request slowed, defines concrete SLOs (example: 99.9% availability over 30 days) and ties observability metrics to deployment gates and product decisions.
AI-written summary · about
chapters (9)
- 0:00Start
- 11:25WHAT IS KEY TO TESTING ON PROD?
- 22:17TIME HAS COME
- 23:29DEVOPS CYCLE
- 27:53STRUCTURED LOGGING
- 32:31METRICS
- 34:00DISTRIBUTED TRACING
- 39:47EXPERIMENT IN PRODUCTION
- 52:43TONIGHT
related talks
37mObservability-Driven Development
44mObservability: Superpowers for Developers
31mObservability for Developers: How to Get There
13mObservability that matters
53mDeliver Results, Not Just Releases: Control & Observability in CD
29mObservability for Developers: How to Get From Here to There
37mBetter Reliability Through Observability and Experimentation
41mA peek into observability from testers lens
