What is progressive delivery and how does it extend beyond basic canary releases?
Answer
Progressive delivery (a term coined by James Governor) is the evolution of continuous delivery that gives fine-grained control over who receives a new version and monitors impact in real time. Beyond basic canary releases (percentage of traffic), progressive delivery includes: Traffic shadowing (mirroring) — a copy of live traffic is sent to the new version in parallel, with responses discarded, allowing you to observe its behavior under real production load without affecting users; A/B testing — routing specific user segments (by geography, user ID, account plan) to different versions to measure business metric impact; Dark launching — deploying a feature to production but keeping it invisible to users while exercising it with synthetic or mirrored traffic. Tools like Argo Rollouts, Flagger, and LaunchDarkly automate progressive delivery workflows, integrating with Prometheus metrics to automatically promote or abort releases based on error rate and latency SLOs.
Previous
What are the core principles of GitOps?
Next
How is chaos engineering integrated into CD pipelines?
More CI/CD Pipelines Questions
View all →- Advanced What are the core principles of GitOps?
- Advanced How is chaos engineering integrated into CD pipelines?
- Advanced How does Terraform work in fully automated pipelines with plan PR comments and apply on merge?
- Advanced What is compliance as code and how do tools like OPA enforce it in pipelines?
- Advanced What is software supply chain security and what are SLSA levels, SBOMs, and image signing?