Course contentsShow
← Software Engineering
Lesson 718 of 1,93322. Continuous Delivery and DeploymentFree lesson

Choosing a Deployment Strategy

Select the appropriate strategy based on risk tolerance, infrastructure capabilities, and business requirements.

Choosing a Deployment Strategy

What you'll learn: How to select the right deployment approach for your specific application, team, and business context.

There's no one-size-fits-all deployment strategy. You've now learned about blue-green, canary, rolling deployments, feature toggles, shadow deployment, and A/B testing—but which should you actually use? The answer depends on three critical factors: risk tolerance, infrastructure capabilities, and business requirements.

Risk Tolerance

Ask yourself: How catastrophic is downtime or a bad release? A banking application might demand zero-downtime blue-green deployments with instant rollback capability. A blog platform might tolerate brief downtime during a rolling deployment. High-stakes environments favor strategies with easy rollback (blue-green) or gradual exposure (canary).

Infrastructure Capabilities

Your infrastructure constrains your options. Blue-green requires double the production resources—can you afford that? Canary releases need sophisticated traffic splitting and monitoring—do you have load balancers that support weighted routing? Rolling deployments need orchestration tools. If you're resource-constrained or working with legacy systems, simpler strategies might be your only realistic option.

Business Requirements

Does marketing need to coordinate a launch announcement with the release? Use feature toggles to deploy code early but control visibility. Need to test user behavior between two designs? A/B testing deployments fit naturally. Require regulatory audit trails? Blue-green's clear cut-over provides cleaner documentation than gradual rollouts.

Combining Strategies

Many teams layer strategies: deploy with blue-green for safety, use feature toggles to control release timing, and apply canary patterns for high-risk features. Start simple and evolve as your needs and capabilities grow.

Key Takeaway: Choose your deployment strategy by honestly assessing your risk tolerance, available infrastructure, and business needs—not by following trends or copying others blindly.