BACKEND SYSTEMS
Inception
Inception is a DevOps project centered around designing and deploying a complete multi-service infrastructure using Docker and Docker Compose.
YEAR
2023
ROLE
Designed • Developed • Shipped
STACK
01/PROBLEM → SOLUTION
PROBLEM
Services have startup dependencies, containers need DNS and ports, and database data must survive container recreation.
SOLUTION
Each service runs isolated in its own container; Docker Compose declares the stack, named volumes persist DB data, and an internal network handles service DNS.
02/SYSTEM ARCHITECTURE
How the system fits together
- External User
- →NGINX Container
- →WordPress Container
- →MariaDB Container
- →Docker Volume
- →Docker Network
Drag to pan or Hover to trace or Click to inspect
03/KEY ENGINEERING DECISIONS
Container Isolation
Every major service runs in its own container, preventing dependency conflicts and enabling independent updates.
Infrastructure as Code
Docker Compose declares the environment, making deployments reproducible and version-controlled.
Persistent Volumes
Named volumes survive container recreation, preventing data loss on rebuild.
04/IMPACT & TAKEAWAYS
Reproducible Stack. Full environment boots from one versioned Compose file.
TLS Terminated. NGINX terminates TLS on 443 and reverse-proxies to WordPress and MariaDB.
Isolated Networking. Services reach each other by internal hostname without host config.