Skip to main content
Back to E-commerce Dictionary

Data Mesh

Data managementAdvanced Level

A data mesh is a decentralized data architecture where business domains own and publish their data as products, following shared governance rules.

Image by · CC BY 4.0

What is Data Mesh?

A data mesh is a decentralized approach to data architecture in which business domains own, publish and maintain their own data as products, instead of sending everything to one central data team. Zhamak Dehghani introduced the idea in 2019. It rests on four principles: domain ownership, data as a product, a self-serve data platform, and federated governance, meaning shared standards every domain follows. A data lake or data warehouse is a storage technology; a data mesh is an organizational model that can still use them underneath. For product information, the team that knows the products best owns the product data and publishes it in an agreed form. Clear data governance is what keeps a mesh from turning into new silos.

Why Data Mesh matters for e-commerce

Large retailers have many data domains: products, prices, stock, orders, customers and marketing. When one central team has to model and clean all of it, requests queue up, and the people who know the data best are not the ones fixing it. A data mesh moves that responsibility to the domains. The product team owns product data quality, logistics owns stock data, and each publishes data other teams can rely on. It suits large organizations with several capable teams. For smaller shops, one central system with a clear owner per data type is usually simpler.

Examples of Data Mesh

  • 1Domain: Product, Owner: product content team, Data product: enriched product data in the PIM
  • 2Domain: Inventory, Owner: logistics, Data product: stock levels per warehouse through an API
  • 3Domain: Marketing, Owner: marketing analytics, Data product: campaign and attribution tables
  • 4Domain: Customer, Owner: CRM team, Data product: customer segments shared with sales
Image by · CC BY 4.0

How WISEPIM Helps

  • WISEPIM can be the product domain's tool in a data mesh: the product team owns attributes, descriptions and images there.
  • Quality Guard rules make the product domain's quality standards explicit and checkable.
  • Exports and platform connections publish product data to the channels and systems that use it.
  • Attribute management keeps one agreed structure for product data across categories.

Common mistakes with Data Mesh

  • Treating a data mesh as a software purchase instead of a change in ownership.
  • Giving domains ownership without shared standards, which creates new silos.
  • Adopting a mesh in a small organization where one central team works fine.
  • Skipping the self-serve platform, so each domain builds its own tooling.

Tips for Data Mesh

  • Start with one domain that has a clear owner and clear users of its data.
  • Define what makes a data product usable: schema, owner, quality checks and documentation.
  • Compare the roles of PIM and master data management in the PIM vs MDM guide.

Trends around Data Mesh

  • Data contracts: written agreements on schema and quality between data producers and consumers.
  • Data catalogs that make domain data products easy to find.
  • AI tools that check data products against quality rules automatically.

Tools for Data Mesh

  • WISEPIM: a PIM the product domain can use to own product data.
  • Snowflake: a data cloud for sharing data products.
  • Databricks: a lakehouse platform used for domain data products.
  • Starburst: a query engine across distributed data sources.
  • Confluent: event streaming for sharing data between domains.

Related Terms

Attribute CollisionCanonical Data ModelCircular Economy Data ModelCross-Border Trade (CBT) AttributesData ContractData Decay

Also Known As

Decentralized data architectureDomain-oriented data architectureFederated data architecture

Frequently Asked Questions

A data mesh is a data architecture where business domains own and publish their own data as products, supported by a shared self-serve platform and common governance rules. It replaces a single central data team as the owner of all data.

A data lake is a storage place for raw data, usually run by a central team. A data mesh is an organizational model that spreads ownership across domains. A mesh can still use data lakes or warehouses underneath.

Domain ownership, data as a product, a self-serve data platform and federated computational governance. Together they let domains publish data on their own while following shared standards.

Yes. In a mesh, the PIM is a natural tool for the product domain: the product team owns the data there and publishes it to channels and other domains. The mesh rules decide which formats and quality checks that product data must meet.

Still have questions?

Can't find the answer you're looking for? Please get in touch with our team.

Contact Support

Keep exploring

Hand-picked next steps to go deeper.