Six Deployment Strategies and How Teams Choose Among Them

A deployment strategy determines how many users receive a new software version before its reliability is confirmed. The article outlines six approaches: recreate, rolling update, blue/green, canary, shadow, and feature flags. It argues most teams only need two of them, and suggests choosing based on circumstances such as team size, infrastructure, and the cost of a bad release. A key distinction is drawn between deploying code and releasing new behavior to users, with feature flags governing the latter. The piece compares strategies by who receives the update first, the extra capacity required, and how rollbacks work, and recommends a rolling update with readiness probes plus feature flags for risky changes as a common default for startups.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in