Technical Evidence¶
Reviewer evidence
Technical evidence without the wall of links¶
This page is the short version. It is designed for a reviewer who wants to know what was actually built without being dropped into every ADR, API reference and deployment note at once.
Use it as a map: start with the summary, choose one review path, and open the deep dive only if you want the full technical archive.
Visual Evidence Shortcuts¶
Serving path
Live ML predictions¶

FastAPI prediction paths for the portfolio services, shown as a short visual review instead of another long code block.
Observability path
Monitoring under load¶

Grafana, Prometheus, Locust and MLflow evidence grouped for reviewers who want runtime behavior, not only architecture claims.
Cloud path
GKE and EKS parity¶

Side-by-side cloud evidence showing that the portfolio was exercised across Google Cloud and AWS Kubernetes environments.
Green Checks And Runtime Evidence¶
CI proof
GitHub Actions completed¶

Visible green checks reduce the time a technical reviewer spends wondering whether the 395+ tests are only a claim.
Smoke proof
API health checks passed¶

Health-check screenshots show that the APIs were exercised as running services, not only described in documentation.
Model lifecycle
MLflow experiment tracking¶

MLflow evidence makes model tracking tangible for reviewers who want to see experiment and model registry habits.
Observability
Grafana and load testing¶

The load-test evidence connects observability claims to measured runtime behavior.
Key Engineering Decisions¶
Serving
One worker per pod plus executor¶
Kubernetes handles horizontal scaling; the API avoids
uvicorn --workers N inside one pod and keeps the event loop free by
offloading CPU-bound inference work to asyncio.run_in_executor()
and ThreadPoolExecutor.
Cost control
Cloud evidence, not always-on waste¶
The portfolio preserves deployment proof while pausing live clusters when the monthly cost is not justified for a public showcase.
Template extraction
Lessons became guardrails¶
The reusable template turns repeated failure modes into documented defaults, rules and reviewable workflows.