deployment-patterns

CI/CD pipelines, Docker containerization, deployment strategies, health checks, and production readiness for web applications. Production deployment workflows and CI/CD best practices. Replace instances gradually — old and new versions run simultaneously during rollout. Pros: Zero downtime, gradual rollout Cons: Two versions run simultaneously — requires backward-compatible changes Use when: Standard deployments, backward-compatible changes Run two identical environments. Switch traffic atomically. Pros: Instant rollback (switch back to blue), clean cutover Cons: Requires 2x infrastructure during deployment Use when: Critical services, zero-tolerance for issues Route a small percentage of traffic to the new version first. Pros: Catches issues with real traffic before full rollout Cons: Requires traffic splitting infrastructure, monitoring Use when: High-traffic services, risky changes, feature flags Before any production deployment: - Covers three deployment patterns: rolling (zero-downtime gradual updates), blue-green (atomic traffic switching), and canary (percentage-based rollout with monitoring) - Includes multi-stage Dockerfile examples for Node.js, Go, and Python with best practices for image size, non-root users, and health checks - Provides GitHub Actions pipeline templates, environment configuration via twelve-factor principles, and configuration validation with Zod -...