Back to All Terms
AI Definition
MLOps
The engineering discipline that takes a trained machine learning model from a notebook to reliable production use.
MLOps (Machine Learning Operations) is the set of practices, tools, and organizational habits that connect data science experimentation to reliable, monitored production systems. A model that performs well in a Jupyter notebook is not yet useful to a business: it needs a repeatable pipeline for training, versioning, testing, deployment, and monitoring, along with a plan for what happens when real-world data drifts away from the data the model was trained on. MLOps borrows heavily from DevOps (continuous integration, continuous deployment, infrastructure as code) but adds ML-specific concerns: dataset versioning, model versioning, experiment tracking, automated retraining triggers, and drift/performance monitoring once a model is serving live traffic.
Practical Implementation & Example
A Typical MLOps Pipeline:
- Experiment Tracking: Every training run logs its hyperparameters, dataset version, and metrics (using tools like MLflow or Weights & Biases) so results are reproducible.
- CI/CD for Models: A new model version is automatically tested against a validation set and a set of business rules before it's allowed to deploy.
- Containerized Serving: The model is packaged (often with Docker) and served through an API endpoint, frequently behind a feature flag for gradual rollout.
- Drift Monitoring: Production input data is continuously compared against training data distributions; when they diverge significantly, an alert triggers a retraining job.
- Rollback Plan: If the new model underperforms in production, the pipeline can instantly roll back to the previous stable version.
Why It Matters:
A model with 95% offline accuracy that silently degrades to 80% in production, undetected for months, is a far bigger business risk than a lower-accuracy model with proper monitoring in place.