Canary in the Internet Mine
summary
Argues for incremental, reversible releases using an edge router so traffic shifts, not deploys, control exposure; implements a reverse-proxy that routes a 30% canary while collecting customer-centric metrics (latency, request rate, response codes) and supports header and cookie based dev branch tests. Demo shows a canary that spikes latency and failures, immediate rollback by rerouting traffic, and a successful full cutover when metrics stay healthy.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:35Turbine Labs
- 2:06Testing in Production
- 2:21Current State
- 3:13Microservices
- 4:05Monitoring
- 5:13Per Endpoint
- 6:08Smart Edge
- 6:29Demo
- 11:30Summary
related talks
06mMaintaining Performance and Reliability on the Edge
25mPushing Code: Don't Forget to Flag Your Canaries?
23mTowards Better Canary Releases With Flagger and Gateway API
11mConfident Canary Deployment to Production With Istio
06mGit Going Fast with Cilium and Argo
53mTinkertoys, microservices, and feature management: How to build for the future
30mChoose Your Own Deployment: Interactive Feature Flag Adventure
35mEvolving your APIs, a step-by-step approach