Production Deployment¶

🚀 Learning Objectives

Deploy containers to production
Implement deployment strategies
Set up monitoring and logging
Create backup and recovery plans

Deploy Docker containers to production environments.

Production Checklist

Before deploying: security scanning, resource limits, health checks, logging, monitoring, backups, and rollback plans. Never deploy without these in place.

Deployment Strategies

Blue-Green: Zero downtime, easy rollback, requires double resources
Rolling Updates: Gradual rollout, less resource overhead
Canary: Test with small traffic, safest for critical systems Choose based on your requirements and infrastructure.

Production Checklist¶

Pre-Deployment¶

Deployment Strategies¶

Blue-Green Deployment¶

# Deploy new version (green)
docker-compose -f docker-compose.green.yml up -d

# Test green deployment
curl http://green.example.com/health

# Switch traffic (update load balancer)
# Stop blue
docker-compose -f docker-compose.blue.yml down

Rolling Updates¶

# docker-compose.yml
services:
  web:
    image: myapp:v2
    deploy:
      update_config:
        parallelism: 2
        delay: 10s
        failure_action: rollback

Canary Deployment¶

# Deploy canary (10% traffic)
docker run -d --name app-canary \
  -p 8081:80 \
  myapp:v2

# Monitor canary
# If successful, deploy to all
docker-compose up -d --scale web=10

Orchestration¶

Docker Swarm¶

# Initialize swarm
docker swarm init

# Create service
docker service create \
  --name web \
  --replicas 3 \
  --publish 80:80 \
  myapp:latest

# Update service
docker service update --image myapp:v2 web

# Rollback
docker service rollback web

Kubernetes (Basic)¶

# deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: myapp
spec:
  replicas: 3
  selector:
    matchLabels:
      app: myapp
  template:
    metadata:
      labels:
        app: myapp
    spec:
      containers:
      - name: myapp
        image: myapp:v1
        ports:
        - containerPort: 80

Monitoring¶

Logging¶

# docker-compose.yml
services:
  app:
    image: myapp
    logging:
      driver: "json-file"
      options:
        max-size: "10m"
        max-file: "3"

Health Checks¶

services:
  app:
    image: myapp
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost/health"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 40s

Metrics¶

# Export metrics
docker stats --format "table {{.Container}}\t{{.CPUPerc}}\t{{.MemUsage}}"

# Use Prometheus
docker run -d \
  --name prometheus \
  -p 9090:9090 \
  -v prometheus.yml:/etc/prometheus/prometheus.yml \
  prom/prometheus

CI/CD Integration¶

GitHub Actions¶

# .github/workflows/deploy.yml
name: Deploy
on:
  push:
    branches: [main]
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Build image
        run: docker build -t myapp:${{ github.sha }} .
      - name: Push to registry
        run: docker push myapp:${{ github.sha }}
      - name: Deploy
        run: |
          docker-compose pull
          docker-compose up -d

Backup and Recovery¶

Database Backup¶

# Backup script
#!/bin/bash
BACKUP_DIR="/backups"
DATE=$(date +%Y%m%d_%H%M%S)

docker exec postgres pg_dump -U postgres mydb > \
  ${BACKUP_DIR}/mydb_${DATE}.sql

# Restore
docker exec -i postgres psql -U postgres mydb < \
  ${BACKUP_DIR}/mydb_20231108_120000.sql

Volume Backup¶

# Backup volume
docker run --rm \
  -v mydata:/data \
  -v $(pwd):/backup \
  alpine tar czf /backup/backup_$(date +%Y%m%d).tar.gz /data

Disaster Recovery¶

Recovery Plan¶

Identify failure: Monitor and alerting
Isolate issue: Stop affected services
Restore from backup: Database and volumes
Redeploy: Use last known good version
Verify: Health checks and monitoring
Document: Post-mortem analysis

Best Practices¶

Use orchestration for production (Swarm/Kubernetes)
Implement health checks for all services
Set resource limits to prevent resource exhaustion
Enable logging with rotation
Monitor metrics continuously
Automate deployments with CI/CD
Test rollback procedures regularly
Document runbooks for common issues

Exercises¶

Set up a production deployment with health checks
Configure automated backups
Create a CI/CD pipeline for deployment
Test a rollback procedure

Previous: Performance Optimization | Next: System Troubleshooting