🏠 Portfolio Home

🚂 Same Journey, Different Tracks

Infrastructure as Code: The patterns you already know

📦
Current Stack (Finance SaaS)
Vercel
Frontend
🚂
Railway
Backend
Supabase
Database
🪣
AWS S3
Storage
🐙
GitHub
CI/CD
⇅ Same pattern, different vendors
☁️
Terraform + Azure
🌐
Static Site
Frontend
λ
Functions
Backend
🌍
CosmosDB
Database
💾
Blob Storage
Storage
🔐
Key Vault
Secrets

💡 Transferable Architecture Knowledge

The same cloud architecture patterns apply across platforms — frontend hosting, serverless compute, managed databases, object storage, and CI/CD automation. Terraform provides a unified way to define and deploy these resources consistently.

The Journey from Platform Configs to Infrastructure as Code

01

Building with Modern Platforms

When building a Financial SaaS application, I chose best-in-class platforms: Vercel for fast frontend deployments, Railway for scalable backend services, Supabase for managed PostgreSQL, and AWS S3 for reliable storage. Each platform has its own configuration — vercel.json, railway.toml, environment variables scattered across dashboards.

02

Recognizing the Pattern

Every cloud architecture follows the same fundamental pattern: compute, storage, database, and automation. Whether it's Vercel + Supabase or Azure Functions + CosmosDB, the architectural thinking remains identical. The services are interchangeable pieces solving the same problems.

03

Terraform: One Language for All Infrastructure

Terraform takes this insight further — instead of managing configurations across multiple dashboards, everything lives in code. A single .tf file can define your entire infrastructure, version-controlled in Git, reviewed like any other code change, and deployed consistently every time.

04

Skills That Transfer

Understanding how to architect applications with Vercel, Railway, and Supabase means understanding how to architect with Azure, AWS, or GCP. The mental model is the same — Terraform is simply learning a new syntax for concepts I already use every day.