Infrastructure & DevOps Architecture by Phase
This document defines deployment architecture, CI/CD, monitoring, and backup strategies for each phase.
Phase A: WordPress Theme Redesign
Deployment Architecture
┌────────────────────────────────────────────────┐
│ Production Environment │
│ │
│ ┌──────────────┐ ┌─────────────────┐ │
│ │ CDN │◀────────│ Web Server │ │
│ │ (Cloudflare) │ │ - Nginx/Apache │ │
│ └──────────────┘ │ - PHP-FPM │ │
│ │ - WordPress │ │
│ └────────┬────────┘ │
│ │ │
│ ┌──────────────┐ ┌────────▼────────┐ │
│ │ Redis │◀────────│ MySQL │ │
│ │ (Cache) │ │ (Database) │ │
│ └──────────────┘ └─────────────────┘ │
└────────────────────────────────────────────────┘
CI/CD Pipeline
- Git push → Build theme assets (Bud.js) → Lint → Upload to staging → Smoke tests → Manual approval → Deploy to production
- Artifacts: versioned assets with cache-busting
Monitoring & Observability
- Uptime: UptimeRobot/Pingdom
- Error logging: WP debug logs + Sentry (optional)
- Performance: Lighthouse CI baseline per release
Backups
- DB: nightly full + 7-day retention, weekly snapshot + 4-week retention
- Files: nightly uploads backup + 30-day retention
Phase B: Headless + Monorepo (Next.js + Expo) + Laravel API
Deployment Architecture
┌─────────────────────────────────────────────────────────┐
│ Public Edge │
│ ┌─────────────┐ ┌──────────────┐ ┌──────────┐ │
│ │ Vercel │◀────│ Cloudflare │────▶│ Users │ │
│ │ (Next.js) │ └──────────────┘ └──────────┘ │
│ └─────┬───────┘ │
│ │SSR/ISR │
│ ┌─────▼─────────────────┐ ┌─────────────────────┐ │
│ │ Laravel API (VPS) │◀────▶│ Redis (Managed) │ │
│ │ Nginx + PHP-FPM │ └─────────────────────┘ │
│ │ Horizon (queues) │ ┌─────────────────────┐ │
│ └──────────┬────────────┘ │ MySQL (Managed) │ │
│ │ └─────────────────────┘ │
│ │ Webhooks │
│ ┌─────▼───────┐ │
│ │ WordPress │ (Headless CMS) │
│ └──────────────┘ │
└─────────────────────────────────────────────────────────────┘
CI/CD Pipeline
- API: Git push → CI (lint, tests) → Build → Deploy to staging → E2E → Manual approval → Prod deploy
- Web: Git push → Vercel Preview → QA → Merge → Prod
- Mobile: EAS builds → TestFlight/Closed testing → Store release; OTA via EAS Update
Monitoring & Observability
- API APM: New Relic/Datadog
- Error tracking: Sentry (API/Web/Mobile)
- Logs: Papertrail/CloudWatch
- Metrics: Uptime, latency, error rate, cache hit ratio
Backups
- Managed DB backups + point-in-time recovery
- Nightly file backups (if any local assets)
Phase C: Full Laravel Platform
Deployment Architecture
┌─────────────────────────────────────────────────────────┐
│ Edge/CDN │
│ Vercel (Web) | API Gateway/ALB | WAF | CDN │
└──────────┬──────────────────────────────────────────────┘
│
┌──────────▼───────────┐ ┌───────────────────────────┐
│ Laravel App (ASG/ECS)│◀───▶│ Redis (Cache & Queues) │
└──────────┬───────────┘ └───────────────────────────┘
│ ┌───────────────────────┐
▼ │ Search (Algolia/ES) │
┌──────────────┐ └───────────────────────┘
│ MySQL Cluster│
└──────────────┘
CI/CD
- Blue/green or canary deployments for API
- Infrastructure as Code (Terraform/CloudFormation)
Observability
- SLOs and error budgets (e.g., 99.9% API uptime)
- Distributed tracing (OpenTelemetry)
Disaster Recovery
- Cross-region DB replicas (RPO < 15 min)
- Automated failover runbooks