Why This Portfolio Is Static First
A personal portfolio should optimize for speed, security, cost, and maintainability before introducing cloud infrastructure complexity.
Decision
This site is static first: HTML, CSS, JavaScript, and assets. That means there is no server to patch, no database to secure, no login flow, and no always-on compute bill.
Tradeoff
A cloud load balancer, WAF, managed backend, and Kubernetes deployment would be a fun infrastructure showcase, but not the cheapest or most efficient v1. For this use case, the architecture should be boring, reliable, and easy to deploy.
Next evolution
If the site later needs dynamic demos, search, newsletter workflows, or private dashboards, those can be added with serverless functions or a small backend. Until then, static hosting keeps the operational surface area low.