Home › Key concepts › Versioning data, code and models

Key concept · Walk (intermediate) · the same on every platform

Versioning data, code and models

Be able to say exactly which data and code made which model.

What it is

Reproducing a model needs three things: the code version, the data version and the settings. Experiment tracking records them for each run; a model registry stores the resulting models with versions and approvals.

Why it matters

When a model misbehaves you must be able to rebuild it, compare it and roll it back.

An example

Model v14 was trained on the 1 October snapshot with commit a3f9; rolling back to v13 takes one click.

The common mistake

Saving models as model_final_v2_REAL.pkl on a laptop.

Where you meet it on each platform

The idea stays the same; only the product name changes.

JobAWSAzureGoogle CloudDatabricksOpen source
Experiment trackingremember which run, data and settings gave which scoreSageMaker MLflowAzure ML (MLflow)Vertex AI ExperimentsMLflowMLflow
Model registryversions, approvals and rollback for modelsSageMaker Model RegistryAzure ML registryVertex AI Model RegistryModels in Unity CatalogMLflow registry

Related ideas

Where it shows up

Part of the Walk level on these paths: ML Engineering (production ml).