Architecture / 05

Separate the proof from the platform.

The portfolio stays simple and static. The map below makes that delivery path explicit, then shows the cloud patterns I understand without pretending they are needed here.

static runtime / cloud literacy

Diagram 01 / actual runtime

This portfolio

The real production boundary for this site is a source-controlled static export delivered to a browser.

Interactive map
01

Static delivery path

The actual hosting model for this portfolio: source control in, static pages out.

Selected layerGitHub

The repository stores the Next.js source, local content, workflow, and configuration.

This is the architecture used to host the portfolio: GitHub → GitHub Actions → Next.js static export → GitHub Pages → visitor browser.

Diagram 02 / knowledge map

Cloud patterns I understand

Six conceptual examples cover virtual-machine hosting, GitHub-to-ECS delivery, container runtime, RDS-backed data, WHM-managed hosting, and serverless requests.

Interactive map
01

EC2 / Docker host

A conceptual virtual-machine deployment pattern I understand; it is not used for this site.

02

Containerized delivery

A conceptual image-to-orchestrator path for container-based applications.

03

GitHub to ECS delivery

A conceptual AWS CI/CD and container deployment path based on the supplied diagram; it is not used for this static site.

04

RDS-backed application

A conceptual managed relational database pattern I understand; it is not used for this static site.

05

WHM-managed hosting

A conceptual WebHost Manager and cPanel hosting administration path I understand; it is not used for this static site.

06

Serverless request path

A conceptual managed API path where the function is invoked by an HTTP request.

Selected layerInternet

Traffic reaches the cloud-hosted entry point.

These are architecture and technology demonstrations only. They are not services required to host this static portfolio.

Boundary

Use the smallest platform that tells the truth.

The project demonstrates frontend architecture, source control, automated delivery, and cloud fluency without adding a backend, server-side database, authentication system, API endpoint, or AWS hosting dependency.