Skip to main content

Data contracts implement a data mesh

·1 min

Data contracts can be used to implement a data mesh.

Consider the four principles of data mesh:

  1. Domain ownership, where data is owned by those who generate it
  2. Data as a product, with data owners responsible for the data’s quality
  3. Self-serve data platform, providing the infrastructure so autonomous teams can build and manage their data products independently
  4. Federated data governance, balancing the need for central oversight with the autonomy of domain teams

Each of these can be delivered through data contracts, which:

  1. Define ownership and responsibilities, in the data contract and use it to encourage collaboration between the owner, in the domain, and the users outside the domain
  2. Enable discoverable and interoperable data products, by providing the interface that enables discoverable and interoperable data products
  3. Self-served platform that promotes autonomy, by building a contract-driven data platform
  4. Embedding data governance, automating data governance through that data platform

In fact, it would be difficult to implement a data mesh without data contracts.

P.S. Later today I’ll be doing an online talk with Data Mesh Learning called Data Quality: Prevention is better than the cure. Find out more on the meetup page and join us live on YouTube at:

  • 17:30 CET
  • 16:30 BST
  • 11:30 EST
  • 08:30 PST

Bring your hardest questions ready for the Q&A :)


Want great, practical advice on implementing data mesh, data products and data contracts?

In my weekly newsletter I share with you an original post and links to what's new and cool in the world of data mesh, data products, and data contracts.

I also include a little pun, because why not? 😅

(Don’t worry—I hate spam, too, and I’ll NEVER share your email address with anyone!)


Andrew Jones
Author
Andrew Jones
I build data platforms that reduce risk and drive revenue.