Heart Disease Prediction — End-to-End MLOps System
Problem Statement
Heart disease prediction models are commonly trained in isolation — but rarely deployed reliably. The challenge: build a full MLOps lifecycle, not just a model, that can be reproduced, versioned, deployed, and monitored in a real infrastructure environment.
What I Built — Architecture
Key Technical Decisions
- ▸ Chose MLflow over manual artifact tracking for full reproducibility — any experiment can be re-run identically
- ▸ FastAPI over Flask for async support, built-in OpenAPI docs, and Pydantic validation — production-appropriate choice
- ▸ Kubernetes even on Minikube to prove the manifests work in a real orchestration environment
Outcome & Learnings
Delivered a fully containerised, observable ML inference system with automated deployment — demonstrating the complete MLOps lifecycle from raw data to production monitoring. Key learning: observability is not optional; you need to know your model is behaving correctly in production.