Complex final Software Architecture project (FIAP Postgraduate). The microsystem was surgically focused on the corporate premises most requested by Tier-1 companies: Clean Architecture, SRE (Reliability), Cloud-Native Deployment, and Microservices.

Architectural Evolution

Developed in Spring Boot, the ecosystem was methodically evolved across modular leaps of distributed architecture: 1. Core Modeling (Clean Architecture): Firm isolation of the corporate domain from infrastructure details using Dependency Inversion. 2. Hybrid Cloud Infrastructure: Decoupling of the relational DB (PostgreSQL) vis-a-vis high-scale Non-Relational Databases (DynamoDB). Simulation of the AWS deployment on the workstation executed locally with containers and the LocalStack stack. 3. API Gateway & Routers: Configurations in fase3-infra-apigateway, separating public interfaces from restricted networks (Private VPC). 4. Atomic Breakdown (Scale-out): Isolation of the base ecosystem into four autonomous asynchronous microservices: Customers, Payment Processing, Order Management, and Production Control.

SRE & DevOps (Infrastructure as Code)

Employing Terraform (AWS) for provisioning via state repository (IaC) and Kubernetes descriptors for replication and auto-scaling orchestration:

# Abstracted K8s deployment providing resilience to request spikes
apiVersion: apps/v1
kind: Deployment
metadata:
  name: ms-payment
  # Focused on HPA (Horizontal Pod Autoscaling) and strict SLAs

The entire pipeline was automated using GitHub Actions (CI/CD / .github/workflows) to promote the build, static inspection, and delivery of the Java container image with Docker directly to Elastic repositories.