MLOps vs DevOps
People often think MLOps is just DevOps used on a model. It takes a lot from DevOps, such as tests, version control and doing jobs by code. But a model also depends on its data. So MLOps has to track data versions, train again, and watch a live model for drift. A normal app does not get worse by itself when the world changes, but a model does.
MLOps
The tools and habits that keep an AI model working. They start once people use it.
MLOps is the set of habits and tools for running machine learning models in real use, not just training them once. It takes ideas from DevOps, such as tests, version control and doing jobs by code. Then it adds what models need. That means tracking data, training again, storing models, serving them and watching them once they are live. The goal is a model you can rebuild, check and update with no risk. Most models fail after launch for lack of this, not for lack of a good first try.
DevOps
A way of working. The people who build the code also run it.
DevOps is a way of working where the people who write code and run it are one team. Before, one group wrote the app and threw it over a wall to another group. Now the same team builds, tests, ships and watches its own code. Much of the work is done by tools that run on their own. The goal is small changes, shipped often, with fewer surprises.
In one line
- MLOps
- The tools and habits that keep an AI model working. They start once people use it.
- DevOps
- A way of working. The people who build the code also run it.
These live in different corners of the glossary (AI and Development), which is exactly why they get confused.