
Unifying fragmented infrastructure to track ML lineage and business impact across domains.
This article explores Netflix's journey in building a Metadata Service (MDS) to solve the complexity of its ML ecosystem. It details how they used a graph-based approach to make every ML asset discoverable and understandable across the company.
Highly recommended for platform engineers struggling with fragmented data infrastructure or senior developers looking to design large-scale MLOps systems.
As Netflix expanded ML across domains like Personalization, Studio, and Payments, fragmented tech stacks turned models into 'black boxes,' hindering cross-team collaboration and asset discovery.
Netflix built a Metadata Service (MDS) that implements a Model Lifecycle Graph using a URI-based addressing scheme, Kafka-based ingestion, Datomic for graph relationships, and Elasticsearch for search.
By connecting ML assets into a navigable graph, Netflix enabled real-time visibility into lineage and impact—from upstream data sources to downstream A/B tests—fostering cross-domain asset reuse.
Trade-off
The hydration process places additional read load on source systems, requiring deliberate rate limiting, and the asynchronous enrichment introduces a short delay in relationship visibility.
A data structure that visualizes and connects the entire ML lifecycle, including pipelines, datasets, models, and A/B tests.
An immutable, facts-based database optimized for complex joins and navigational queries across entity relationships.
The process of fetching full metadata from source systems based on minimal event triggers to build a complete view of an entity.









