Four Principles of the Data Mesh

  1. Domain-oriented decentralized data ownership and architecture: the ecosystem creating and consuming data can scale out as the number of sources of data, number of use cases, and diversity of access models to the data increases; simply increase the autonomous nodes on the mesh.
  2. Data as a product: data users can easily discover, understand and securely use high quality data with a delightful experience; data that is distributed across many domains.
  3. Self-serve data infrastructure as a platform: the domain teams can create and consume data products autonomously using the platform abstractions, hiding the complexity of building, executing and maintaining secure and interoperable data products.
  4. Federated computational governance: data users can get value from aggregation and correlation of independent data products — the mesh is behaving as an ecosystem following global interoperability standards; standards that are baked computationally into the platform.




Bass/BV @StornowayBand. DataCat @AstraZeneca. Consulting via StoneStreetProductions.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Performance Optimization in Clojure Using Reducers and Transducers — A FORMCEPT Exclusive

Learning and trying to reverse web assembly for fun!

How To Create An Elevator In Unity

ELK Logstash Filter writing for response time, request and response correlating

Application Framework

One Unexpected Way to Become a Better Programmer

Web App #Penetration Testing for Beginners:

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Oli Steadman

Oli Steadman

Bass/BV @StornowayBand. DataCat @AstraZeneca. Consulting via StoneStreetProductions.

More from Medium

Navigating the challenges of Metadata Management

New work mindset at Snowflake❄️

Data Quality and observability tools

Why are Data Warehouses evolving to Lake Houses? Part4 — Blend Relational and Big Data