Week 1: CI/CD for ML, Feature Stores & Model Monitoring
Deploy and maintain ML systems in production: CI/CD pipelines, feature stores, model registries, A/B testing frameworks, and drift detection.
- Build an end-to-end ML CI/CD pipeline with GitHub Actions
- Implement a feature store using Feast or Tecton
- Set up model monitoring with drift detection alerts
- Design and analyze an A/B test for model deployment
This first lecture establishes the foundational framework for MLOps & Production Systems. By the end of this session, you will have the conceptual grounding and practical starting point needed for the rest of the course.
Key Concepts
The lecture introduces the four main pillars of this course: ML CI/CD with GitHub Actions, Feature Stores: Feast, Tecton, Model Monitoring & Drift Detection, Canary Deployments & A/B Testing. Each will be explored in depth over the 14-week curriculum, with hands-on projects reinforcing theory at every stage.
This Week's Focus
Focus on mastering: ML CI/CD with GitHub Actions and Feature Stores: Feast, Tecton. These are the prerequisites for everything in Week 2. The concepts build on each other — do not skip the practice exercises.
DS506 Project 1: Production ML Platform
Build a complete MLOps platform for a classification model: automated retraining pipeline, feature store, model registry, monitoring dashboard, and canary deployment.
- CI/CD pipeline (GitHub Actions or MLflow)
- Feature store integration (Feast or Hopsworks)
- Monitoring dashboard with drift alerts
- Canary deployment with A/B test analysis
These represent the style and difficulty of questions you'll see on the midterm and final. Start thinking about them now.
What is the difference between data drift and concept drift? How do you detect each?
Describe the components of a feature store. Why is a feature store important for large ML teams?
How do you design a statistically valid A/B test for comparing two ML models in production?