Six deployment strategies compared: rolling, blue-green, canary and more

JeremyCMorgan · x · 2026-11-19

A comparison of six deployment strategies and their operational tradeoffs:

Situation-based advice: small teams on Kubernetes/ECS → tuned rolling update; bad releases cost money within minutes → blue/green; high traffic with trusted metrics → canary with automated checks; risky feature in a normal release → feature flag; rewrite to test under real load → shadow; app that can't run two versions → recreate. The author's default: rolling update with a readiness probe plus feature flags on anything risky, covering most releases with 25% extra capacity. Verified against Kubernetes 1.37, Argo Rollouts v1.10.2, Flagger v1.45.0, Gateway API v1.7.0 docs.

Original post →

More from coding & agent

coding & agent channel →