Deployment Strategies logopeterindia.net
Knowledge Hub

Deployment Strategies: Blue-Green, Canary, Rolling & Progressive Delivery

Blue-green, canary, rolling and other ways to release services safely — guides, Kubernetes and cloud tooling, feature flags and CI/CD platforms.

66 topics•7 categories•Updated October 2026

Strategy Guides & Concepts

16 entries

What each strategy is and when to use it.

01Blue-Green Deployment (Martin Fowler)Two identical environments, with traffic switched from the live one to the new one. 02Canary Release (Martin Fowler)Releasing a new version to a small subset of users first. 03Dark Launching (Martin Fowler)Releasing code to production without exposing it to users. 04Feature Toggles (Martin Fowler)Long-form guide to feature toggles and their types. 05Parallel Change (Martin Fowler)The expand-and-contract technique for changing interfaces and schemas safely. 06Strangler Fig Application (Martin Fowler)Incrementally replacing a legacy system. 07AWS: Deployment strategiesAWS whitepaper section on in-place, rolling, blue/green and canary strategies. 08Google SRE Workbook: Canarying ReleasesGoogle's guidance on canarying and judging canary results. 09Blue/green deployments (Octopus Deploy)Pros, cons and how blue/green works. 10Canary deployments (Octopus Deploy)Pros, cons and how canary releases work. 11Rolling deployments (Octopus Deploy)Pros, cons and how rolling deployments work. 12What is blue-green deployment? (Red Hat)Introduction to blue-green deployment. 13Blue-green deployment (Wikipedia)Overview of the technique. 14Feature toggle (Wikipedia)Overview of feature toggles. 15A/B testing (Wikipedia)Overview of controlled experiments. 16Software deployment (Wikipedia)Overview of deployment concepts.

Kubernetes & Progressive Delivery Tools

16 entries

Controllers and meshes that automate gradual rollouts.

17Kubernetes DeploymentsBuilt-in rolling updates and the Recreate strategy. 18Performing a rolling update (Kubernetes)Tutorial on updating an application with zero downtime. 19Argo RolloutsKubernetes controller for blue-green, canary and experiments. 20Argo Rollouts: Blue-GreenBlue-green strategy in Argo Rollouts. 21Argo Rollouts: CanaryCanary strategy in Argo Rollouts. 22FlaggerProgressive delivery operator that automates canary releases, A/B testing and blue-green on Kubernetes. 23Flagger documentationDocumentation for Flagger. 24Istio: Traffic ShiftingGradually shifting traffic between service versions. 25Istio: MirroringMirroring traffic to a new version for shadow testing. 26Gateway API: HTTP traffic splittingWeighted traffic splitting with the Gateway API. 27Linkerd: Traffic SplitSplitting traffic between service versions in Linkerd. 28Argo CDDeclarative GitOps continuous delivery for Kubernetes. 29FluxGitOps toolkit for Kubernetes; Flagger works with Flux. 30SpinnakerMulti-cloud continuous delivery platform with built-in deployment strategies. 31HarnessSoftware delivery platform with canary and blue-green deployment support. 32OpenGitOpsVendor-neutral principles for GitOps.

Cloud Deployment Services

10 entries

Managed services with built-in strategies.

33AWS CodeDeployAutomates deployments to EC2, Lambda, ECS and on-premises servers. 34AWS CodeDeploy deployment configurationsCanary, linear and all-at-once traffic shifting settings. 35Amazon ECS blue/green deploymentsBlue/green deployments for ECS services. 36AWS Lambda aliasesAliases with weighted routing between function versions. 37Azure App Service deployment slotsStaging slots that can be swapped into production. 38Azure Well-Architected: Safe deployment practicesGuidance on releasing changes safely on Azure. 39Google Cloud Deploy overviewManaged continuous delivery for GKE, Cloud Run and more. 40Google Cloud Deploy: canary strategyUsing a canary strategy with Cloud Deploy. 41Cloud Run: gradual rollouts and traffic migrationSplitting traffic between Cloud Run revisions. 42Cloud Foundry: blue-green deploymentBlue-green deployment with Cloud Foundry routes.

CI/CD Platforms

4 entries

Pipelines that run the rollouts.

43GitLab: Canary deploymentsCanary deployments in GitLab with Kubernetes. 44GitLab: Incremental rolloutsRolling out gradually with GitLab CI/CD. 45GitHub Actions: DeployingEnvironments and deployment controls in GitHub Actions. 46Octopus Deploy: Deployment patternsRolling, blue-green and canary patterns in Octopus Deploy.

Feature Flag Platforms

5 entries

Decouple release from deployment.

47LaunchDarklyFeature management and experimentation platform. 48UnleashOpen-source feature flag platform. 49OpenFeatureVendor-neutral open standard for feature flagging. 50FlagsmithOpen-source feature flag and remote config service. 51GrowthBookOpen-source feature flags and A/B testing.

Database Changes & Delivery Practice

7 entries

Schema changes and the practices around safe delivery.

52FlywayDatabase migration tool (flywaydb.org redirects to Redgate). 53LiquibaseDatabase change management tool. 54Continuous Delivery (Martin Fowler)Introduction to continuous delivery. 55Deployment Pipeline (Martin Fowler)The automated path from commit to production. 56Continuous delivery (Wikipedia)Overview of continuous delivery. 57DORAResearch on software delivery performance, including deployment frequency and change failure rate. 58DORA capabilitiesTechnical and cultural capabilities that drive delivery performance.

Related Pages

8 entries

Neighbouring pages on this site.

59DevOpsDevOps hub. 60CI/CD ToolsCI/CD tools directory. 61Continuous Deployment ToolsContinuous deployment tools. 62Kubernetes CI/CD ToolsCI/CD tools for Kubernetes. 63Site Reliability Engineering (SRE)SRE resources. 64Incident Management ToolsIncident response tools. 65Software Architecture PatternsArchitecture pattern catalog. 66Software EngineeringSoftware engineering hub.

Frequently Asked Questions

What is blue-green deployment?

Blue-green deployment runs two identical production environments. The new version is deployed to the idle one, tested, and traffic is then switched over, which allows near-instant rollback by switching back.

What is a canary deployment?

A canary deployment sends the new version to a small share of traffic or users first, watches health and business metrics, and expands the rollout only if the results are good.

How do rolling, recreate and shadow deployments differ?

A rolling deployment replaces instances gradually, a recreate deployment stops the old version before starting the new one and so causes downtime, and a shadow deployment mirrors live traffic to the new version without returning its responses to users.

How do feature flags relate to deployment strategies?

Feature flags separate deployment from release: code ships dark and is switched on gradually, for all users or specific groups, which supports canary-style rollouts and A/B tests without redeploying.

How current is this page?

Links were checked in October 2026. Cloud and tool documentation is reorganized often (several Google Cloud, GitLab and Octopus pages now redirect to new addresses, which are used here). Strategy names are used slightly differently by different vendors, so check each product's definition.