In the complete Engineering cycle of this niche platform (for supporting the monitoring by Doulas and Pregnant Women), I was tasked with consolidating the DevOps and Deployments Architecture for the entire team. The SRE goal was to parameterize the networks, uniting completely independent architectures (Backend API, Frontend PWA, and a Strapi Headless CMS) under a single portable infrastructure.

The Challenge of Resilient Orchestration

The production software requires an analytical engine (Single-point of Truth) via a relational database (PostgreSQL 14) handling simultaneously: - Web Backend transactions (corporate API built in Java / Spring Boot). - Massive loads in CMS images, Front requests, and dynamically managed publications using the curatorial content port (Strapi v5). - Single-Page Interface consuming heterogeneously under Vue.js and Vite.

Centralized Docker Compose Manifesto and Virtual Networks

The management of containers and the interconnection of closed virtual hostnames were vital to mitigate server costs and prevent the leakage of database ports to the WAN.

# Excerpt from the Isolated Infrastructural Integration
services:
  backend:
    image: evslopes7/maedaprole-backend
    environment:
      - SPRING_DATASOURCE_URL=jdbc:postgresql://postgres:5432/mae_da_prole_dev
      - SPRING_PROFILES_ACTIVE=dev
    depends_on: [postgres]
    networks: [maedaprole_network]

  strapi:
    image: evslopes7/maedaprole-cms
    environment:
      DATABASE_CLIENT: postgres
    depends_on: [postgres]

  frontend:
    image: evslopes7/maedaprole-frontend
    depends_on: [backend]

Security & E2E CI/CD Automation

We obfuscated all critical keys (Admin JWT Secrets, SMTP Nodes, Build environment variables). The entire assembly of final assets is injected remotely by automated repositories in GitHub Actions (ci.yml). Multi-repo tests were performed using End-to-end integration tests with Cypress for the Frontend, ensuring the cluster bridged the interfaces even in local simulations.