Blue-green and canary deploys
How to release new versions without downtime or big-bang risk: rolling updates, blue-green deployments with instant rollback, canary releases with gradual traffic shifting and automated analysis, feature flags, database changes that keep both versions working, and choosing a strategy.
CodexBash, , 5 min read
The riskiest moment for any software is the moment a new version meets real users. A bug that slipped through testing, a configuration difference in production, or traffic patterns nobody anticipated can take the whole service down. Deployment strategies reduce that risk by controlling how the new version replaces the old one: all at once, a few servers at a time, side by side, or to a small slice of users first. This article explains rolling updates, blue-green and canary deployments, and the database discipline they all depend on.
Sign in to read the rest
The whole 5 minute article is free with an account, along with every problem, lesson and tutorial. No card.