SYSTEM Cited by 1 source
Netflix Data Mesh¶
Netflix Data Mesh is Netflix's internal "general purpose data movement and processing platform for moving data between Netflix systems at scale" (as characterised in the UDA post) (Source: sources/2025-06-14-netflix-model-once-represent-everywhere-uda).
Terminology note. Netflix's Data Mesh is a specific platform, not the architectural pattern (concepts/data-mesh) coined by Zhamak Dehghani. The platform is a data-movement pipeline layer; the pattern is a decentralised-ownership organisational approach. These two usages coexist on this wiki.
Role inside UDA¶
In UDA's data-container taxonomy, Data Mesh sources are canonical data containers — listed alongside GraphQL type resolvers and Iceberg tables as the named projection targets for domain-model mappings.
The UDA post also names Data Mesh as a pipeline provisioning target: "Move data faithfully between data containers, such as from federated GraphQL entities to Data Mesh … Change Data Capture (CDC) sources to joinable Iceberg Data Products." UDA + Upper-authored domain models + container mappings auto-generate the Data Mesh movement configuration that would otherwise be hand-configured.
Status on the wiki¶
Stub page — flagged for expansion when Netflix's dedicated "Data Mesh: A Data Movement and Processing Platform" post is ingested.
Seen in¶
- sources/2025-06-14-netflix-model-once-represent-everywhere-uda — Data Mesh named as a canonical UDA data container + pipeline target.
Related¶
- systems/netflix-uda — Data Mesh sources are a UDA container type.
- systems/apache-iceberg — sibling container type in UDA's taxonomy; also named as a CDC-driven pipeline target.
- concepts/data-container — UDA's unifying abstraction.
- concepts/data-mesh — the architectural pattern (different from Netflix's platform of the same name).
- concepts/change-data-capture — CDC is named as a source that UDA + Data Mesh pipe into Iceberg data products.
- companies/netflix — Tier-1 source.