lcbp3/specs/05-decisions/ADR-015-deployment-infrastructure.md

ADR-015: Deployment & Infrastructure Strategy

Status: ✅ Accepted Date: 2025-12-01 Decision Makers: DevOps Team, System Architect Related Documents: ADR-005: Technology Stack, Operations Guide

---

Context and Problem Statement

LCBP3-DMS ต้อง Deploy บน QNAP Container Station โดยใช้ Docker แต่ต้องเลือกกลย modularุทธ์การ Deploy, การจัดการ Environment, และการ Scale ที่เหมาะสม

ปัญหาที่ต้องแก้:

1. Container Orchestration: ใช้ Docker Compose หรือ Kubernetes
2. Environment Management: จัดการ Environment Variables อย่างไร
3. Deployment Strategy: Blue-Green, Rolling Update, หรือ Recreate
4. Scaling: แผน Scale horizontal/vertical
5. Persistence: จัดการ Data persistence อย่างไร

---

Decision Drivers

• 🎯 Simplicity: ง่ายต่อการ Deploy และ Maintain
• 🔒 Security: Secrets management ปลอดภัย
• ⚡ Zero Downtime: Deploy ได้โดยไม่มี Downtime
• 📦 Resource Efficiency: ใช้ทรัพยากร QNAP อย่างคุ้มค่า
• 🔄 Rollback Capability: Rollback ได้เมื่อมีปัญหา

---

Considered Options

Option 1: Docker Compose (Single Server)

Deployment:

version: '3.8'

services:
  backend:
    image: lcbp3-backend:latest
    environment:
      - NODE_ENV=production
    env_file:
      - .env.production
    volumes:
      - ./uploads:/app/uploads
      - ./logs:/app/logs
    depends_on:
      - mariadb
      - redis
    networks:
      - lcbp3-network

  frontend:
    image: lcbp3-frontend:latest
    depends_on:
      - backend
    networks:
      - lcbp3-network

  mariadb:
    image: mariadb:10.11
    volumes:
      - mariadb-data:/var/lib/mysql
    networks:
      - lcbp3-network

  redis:
    image: redis:7.2-alpine
    volumes:
      - redis-data:/data
    networks:
      - lcbp3-network

  elasticsearch:
    image: elasticsearch:8.11.0
    volumes:
      - elastic-data:/usr/share/elasticsearch/data
    networks:
      - lcbp3-network

  nginx:
    image: nginx:alpine
    volumes:
      - ./nginx.conf:/etc/nginx/nginx.conf
      - ./ssl:/etc/nginx/ssl
    ports:
      - '80:80'
      - '443:443'
    depends_on:
      - backend
      - frontend
    networks:
      - lcbp3-network

volumes:
  mariadb-data:
  redis-data:
  elastic-data:

networks:
  lcbp3-network:

Pros:

• ✅ Simple และเข้าใจง่าย
• ✅ พอดีกับ QNAP Container Station
• ✅ Resource requirement ต่ำ
• ✅ Debugging ง่าย

Cons:

• ❌ Single point of failure
• ❌ ไม่มี Auto-scaling
• ❌ Service discovery manual

Option 2: Kubernetes (k3s)

Pros:

• ✅ Auto-scaling
• ✅ Self-healing
• ✅ Service discovery

Cons:

• ❌ ซับซ้อนเกินความจำเป็น
• ❌ Resource overhead สูง
• ❌ Learning curve สูง
• ❌ Overkill สำหรับ Single server

---

Decision Outcome

Chosen Option: Docker Compose with Blue-Green Deployment Strategy

Rationale

1. Appropriate Complexity: เหมาะกับ Scale และทีมของโปรเจกต์
2. QNAP Compatibility: รองรับโดย QNAP Container Station
3. Resource Efficiency: ใช้ทรัพยากรน้อยกว่า K8s
4. Team Familiarity: ทีม DevOps คุ้นเคยกับ Docker Compose
5. Easy Rollback: Rollback ได้ง่ายด้วย Tagged images

---

Implementation Details

1. Directory Structure

/volume1/lcbp3/
├── blue/
│   ├── docker-compose.yml
│   ├── .env.production
│   └── nginx.conf
│
├── green/
│   ├── docker-compose.yml
│   ├── .env.production
│   └── nginx.conf
│
├── nginx-proxy/
│   ├── docker-compose.yml
│   └── nginx.conf (routes to blue or green)
│
├── shared/
│   ├── uploads/
│   ├── logs/
│   └── backups/
│
└── volumes/
    ├── mariadb-data/
    ├── redis-data/
    └── elastic-data/

2. Blue-Green Deployment Process

#!/bin/bash
# File: scripts/deploy.sh

CURRENT=$(cat /volume1/lcbp3/current)
TARGET=$([[ "$CURRENT" == "blue" ]] && echo "green" || echo "blue")

echo "Current environment: $CURRENT"
echo "Deploying to: $TARGET"

cd /volume1/lcbp3/$TARGET

# 1. Pull latest images
docker-compose pull

# 2. Start new environment
docker-compose up -d

# 3. Run database migrations
docker exec lcbp3-${TARGET}-backend npm run migration:run

# 4. Health check
for i in {1..30}; do
  if curl -f http://localhost:${TARGET}_PORT/health; then
    echo "Health check passed"
    break
  fi
  sleep 2
done

# 5. Switch nginx to new environment
sed -i "s/$CURRENT/$TARGET/g" /volume1/lcbp3/nginx-proxy/nginx.conf
docker exec lcbp3-nginx nginx -s reload

# 6. Update current pointer
echo "$TARGET" > /volume1/lcbp3/current

# 7. Stop old environment (keep data)
cd /volume1/lcbp3/$CURRENT
docker-compose down

echo "Deployment complete: $TARGET is now active"

3. Environment Variables Management

# File: .env.production (NOT in Git)
NODE_ENV=production

# Database
DB_HOST=mariadb
DB_PORT=3306
DB_USERNAME=lcbp3_user
DB_PASSWORD=<secret>
DB_DATABASE=lcbp3_dms

# Redis
REDIS_HOST=redis
REDIS_PORT=6379
REDIS_PASSWORD=<secret>

# JWT
JWT_SECRET=<secret>
JWT_EXPIRES_IN=7d

# File Storage
UPLOAD_PATH=/app/uploads
ALLOWED_FILE_TYPES=.pdf,.doc,.docx,.xls,.xlsx,.dwg

# Email
SMTP_HOST=smtp.example.com
SMTP_PORT=587
SMTP_USERNAME=<secret>
SMTP_PASSWORD=<secret>

Secrets Management:

• Production .env files stored on QNAP only (NOT in Git)
• Use docker-compose.override.yml for local development
• Validate required env vars at application startup

4. Volume Management

volumes:
  # Persistent data (survives container recreation)
  mariadb-data:
    driver: local
    driver_opts:
      type: none
      device: /volume1/lcbp3/volumes/mariadb-data
      o: bind

  # Shared uploads across blue/green
  uploads:
    driver: local
    driver_opts:
      type: none
      device: /volume1/lcbp3/shared/uploads
      o: bind

  # Logs
  logs:
    driver: local
    driver_opts:
      type: none
      device: /volume1/lcbp3/shared/logs
      o: bind

5. NGINX Reverse Proxy

# File: nginx-proxy/nginx.conf
upstream backend {
    server lcbp3-blue-backend:3000;  # Switch to green during deployment
}

upstream frontend {
    server lcbp3-blue-frontend:3000;
}

server {
    listen 80;
    server_name lcbp3-dms.example.com;
    return 301 https://$server_name$request_uri;
}

server {
    listen 443 ssl http2;
    server_name lcbp3-dms.example.com;

    ssl_certificate /etc/nginx/ssl/cert.pem;
    ssl_certificate_key /etc/nginx/ssl/key.pem;

    # Frontend
    location / {
        proxy_pass http://frontend;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
    }

    # Backend API
    location /api {
        proxy_pass http://backend;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;

        # Timeouts for file uploads
        client_max_body_size 50M;
        proxy_read_timeout 300s;
    }

    # Health check
    location /health {
        proxy_pass http://backend/health;
        access_log off;
    }
}

---

Scaling Strategy

Vertical Scaling (Phase 1)

Current Recommendation:

• Backend: 2 CPU cores, 4GB RAM
• Frontend: 1 CPU core, 2GB RAM
• MariaDB: 2 CPU cores, 8GB RAM
• Redis: 1 CPU core, 2GB RAM
• Elasticsearch: 2 CPU cores, 4GB RAM

Upgrade Path:

• Increase CPU/RAM ตาม Load
• Monitor with Prometheus/Grafana

Horizontal Scaling (Phase 2 - Future)

If needed:

• Load Balancer หน้า Backend (multiple replicas)
• Database Read Replicas
• Redis Cluster
• Elasticsearch Cluster

Prerequisite:

• Stateless application (sessions in Redis)
• Shared file storage (NFS/S3)

---

Deployment Checklist

### Pre-Deployment

- [ ] Backup database
- [ ] Tag Docker images
- [ ] Update .env file
- [ ] Review migration scripts
- [ ] Notify stakeholders

### Deployment

- [ ] Pull latest images
- [ ] Start target environment (blue/green)
- [ ] Run migrations
- [ ] Health check passes
- [ ] Switch NGINX proxy
- [ ] Verify application working

### Post-Deployment

- [ ] Monitor logs for errors
- [ ] Check performance metrics
- [ ] Verify all features working
- [ ] Stop old environment
- [ ] Update deployment log

---

Consequences

Positive Consequences

1. ✅ Simple Deployment: Docker Compose เข้าใจง่าย
2. ✅ Zero Downtime: Blue-Green Deployment ไม่มี Downtime
3. ✅ Easy Rollback: Rollback = Switch NGINX back
4. ✅ Cost Effective: ไม่ต้อง Kubernetes overhead
5. ✅ QNAP Compatible: ใช้ได้กับ Container Station

Negative Consequences

1. ❌ Manual Scaling: ต้อง Scale manual
2. ❌ Single Server: ไม่มี High Availability
3. ❌ Limited Auto-healing: ต้อง Monitor และ Restart manual

Mitigation Strategies

• Monitoring: Setup Prometheus + Alertmanager
• Automated Backups: Cron jobs สำหรับ Database backups
• Documentation: เขียน Runbook สำหรับ Common issues
• Health Checks: Implement comprehensive health endpoints

---

Related ADRs

• ADR-005: Technology Stack
• ADR-009: Database Migration Strategy

---

References

• Docker Compose Documentation
• Blue-Green Deployment
• QNAP Container Station

---

Last Updated: 2025-12-01 Next Review: 2026-06-01