Definition: Deployment strategy that releases a new version to a small subset of users before rolling it out to the entire base, minimizing the risk of errors.
— Source: NERVICO, Product Development Consultancy
What is Canary Deployment
Canary deployment is a release strategy that exposes a new application version to a small percentage of users before extending it to the entire base. The name comes from the historical practice of using canaries in coal mines to detect toxic gases. If the canary (small user group) shows no problems, the percentage is gradually increased until reaching 100%.
How it works
The load balancer or routing system directs a configurable percentage of traffic (for example, 5%) to the new version while the remaining 95% continues using the stable version. During this period, the team monitors key metrics: error rate, latency, resource usage, and business metrics. If metrics remain within acceptable thresholds, the percentage increases progressively (10%, 25%, 50%, 100%). If degradation is detected, traffic is redirected entirely to the previous version.
Why it matters
Canary deployment drastically reduces the impact of production errors. If a new version introduces a bug, it only affects the small percentage of users receiving the canary version. This is especially valuable for applications with millions of users, where a global error can have significant financial and reputational consequences.
Practical example
A SaaS platform with 100,000 active users launches a new search engine. They first deploy the canary version to 2% of users (2,000). After 24 hours with no increase in errors and a 15% improvement in response time, they increase to 10%. On the second day, they detect a subtle increase in 500 errors for queries with special characters. They fix the bug, restart the canary at 5%, and after successful verification, complete the rollout to 100% within five days.