Deployment Strategies
In depthConcept
Also known as: Blue-Green, Canary, Rolling Update
Techniques for shipping new versions with minimal risk: blue-green, canary and rolling updates.
Deployment Strategies, explained
Written by EduVerseWhat it is
Deployment strategies are ways to swap a running version of your software for a new one without taking everything down at once. A rolling update replaces servers a few at a time, blue-green switches traffic between two full environments, and a canary first sends a small share of users to the new version.
Why teams use it
Every release carries some risk, and stopping the whole app to install a new version means downtime. These strategies limit how many users a bad release can reach and make going back fast. Which one fits depends on cost, on your infrastructure and on how quickly you need to roll back.
An example from work
Your team ships a new checkout flow as a canary to 5 percent of traffic. Within ten minutes the error rate for that group climbs on the dashboard, while the old version stays clean. The rollout is halted, all traffic goes back to the previous version, and most customers never noticed.
Our own explanation, not a quote from the book.
In the book
Sentences from The Software Realm, Decoded that mention Deployment Strategies, exactly as printed.
Peter “But how do I actually know if the canary is healthy?”
Chapter 10 · 10.3.2 Deployment Strategies · p. 224Open in the free preview
2 more passages about Deployment Strategies in the full book
Read every conversation where Deployment Strategies comes up, with the interactive slides and demos.
Where it fits
Safely deploying new software versions
Coverage in the book
Covered in depth: multiple pages with explanations, examples and simulations.
