Backend Deployment Cheat Sheet

Updated 2026-05-28

Next Topic: Backend Development Cheat Sheet

Backend deployment is the process of moving application code from development to production environments, a critical transition where planning, automation, and risk management converge. Modern deployment practices emphasize zero-downtime releases through strategies like blue-green and canary deployments, progressive delivery that incrementally exposes changes to users, and automated rollback mechanisms that restore service when issues arise. Understanding these patterns — from database migration techniques to supply chain security controls — separates deployments that cause outages from those that ship reliably at scale.

What This Cheat Sheet Covers

This topic spans 13 focused tables and 102 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.

Table 1: Core Deployment StrategiesTable 2: Zero-Downtime TechniquesTable 3: Traffic Management & ShiftingTable 4: Database Migration During DeploymentTable 5: Rollback StrategiesTable 6: Feature Flags & TogglesTable 7: CI/CD Deployment AutomationTable 8: Container Orchestration & Package ManagementTable 9: Deployment Verification & TestingTable 10: Deployment Monitoring & ObservabilityTable 11: Environment Management & PromotionTable 12: Supply Chain Security & Deployment GovernanceTable 13: Advanced Deployment Patterns

Table 1: Core Deployment Strategies

The choice of deployment strategy determines how risk, downtime, and blast radius are controlled when shipping new code. Ordered from the simplest to the most controlled, each strategy trades off speed, complexity, and rollback capability differently.

Strategy	Example	Description
Blue-Green Deployment	Two environments: Blue (live) and Green (new). Traffic switches instantly after validation.	• Maintains two identical production environments to eliminate downtime • instant rollback by reverting traffic to the previous environment.
Canary Deployment	Route 5% traffic to new version. Monitor metrics, then gradually increase to 100%.	• Gradually shifts traffic to new version starting with small percentage • limits blast radius if issues arise and enables real-world validation.
Rolling Update	Replace pods incrementally: 25% → 50% → 75% → 100%. Old and new versions coexist temporarily.	• Replaces instances incrementally without downtime • both versions run simultaneously during transition, requiring backward compatibility.
Progressive Delivery	Release to internal users → beta testers → 10% → 50% → 100%. Gate each phase on metrics passing thresholds.	• Controlled, incremental rollout with automated promotion based on success criteria • combines feature flags, canary releases, and observability.
Dark Launch	Deploy feature to production with feature flag disabled. Enable for internal team first, then gradually.	• Code is deployed but feature remains hidden behind toggle • allows production testing without user visibility before official release.

Table 1: Core Deployment Strategies

Strategy	Example	Description
Blue-Green Deployment	Two environments: Blue (live) and Green (new). Traffic switches instantly after validation.	• Maintains two identical production environments to eliminate downtime • instant rollback by reverting traffic to the previous environment.
Canary Deployment	Route 5% traffic to new version. Monitor metrics, then gradually increase to 100%.	• Gradually shifts traffic to new version starting with small percentage • limits blast radius if issues arise and enables real-world validation.
Rolling Update	Replace pods incrementally: 25% → 50% → 75% → 100%. Old and new versions coexist temporarily.	• Replaces instances incrementally without downtime • both versions run simultaneously during transition, requiring backward compatibility.
Progressive Delivery	Release to internal users → beta testers → 10% → 50% → 100%. Gate each phase on metrics passing thresholds.	• Controlled, incremental rollout with automated promotion based on success criteria • combines feature flags, canary releases, and observability.
Dark Launch	Deploy feature to production with feature flag disabled. Enable for internal team first, then gradually.	• Code is deployed but feature remains hidden behind toggle • allows production testing without user visibility before official release.