nw-deployment-strategies

# Deployment Strategies — Rollback, Risk, and Validation For deployment strategy patterns (canary, blue-green, rolling, progressive delivery), see `cicd-and-deployment` skill. This skill focuses on operational concerns: validation, rollback, risk, and post-deployment. ## Pre-Deployment Validation Before any deployment, validate: - Deployment scripts tested in staging | Database migrations tested with rollback scripts - Configuration management consistent across environments | Health checks and service discovery configured - Monitoring and alerting systems prepared | Backup and disaster recovery procedures validated ## Rollback Procedures ### Design Rollback First Every deployment plan starts with the rollback section: 1. **Database rollback**: migration revert scripts tested and verified 2. **Application rollback**: previous version tagged and deployable 3. **Configuration rollback**: previous config snapshots available 4. **Traffic rollback**: load balancer / feature flag kill switch ready 5. **Data rollback**: data consistency plan for partial rollback scenarios ### Automated Rollback Triggers Configure automatic rollback when: - Error rate exceeds baseline by >2x | P95 latency exceeds SLA threshold - Health check failures exceed threshold (e.g., 3 consecutive) | Business metric anomaly detected (e.g., conversion drop >10%) ### Manual Rollback Decision Criteria Stakeholder-reported functional issues | Security vulnerability discovered post-deploy | Data integrity con...