📙 Looking for more on data contracts? Check out my book! 📙 2024
What’s the right organisational structure for a successful data contracts implementation?
A question I received on a LinkedIn post about change management with data contracts asked (lightly edited for clarity):
Data governance initiatives often deliver a set of rules for people to follow when they create and manage data.
When it comes to data contracts I’m always talking about well structured data.
I was asked on LinkedIn how I might approach data contracts with dbt.
Many organisations have a data catalog as a part of their data stack.
The whole point of data mesh is to make data in an organisation more accessible.
To build reliable data products we need a data platform that provides us capabilities to do so.
I wrote yesterday about how important a data catalog becomes when you move to a decentralised and autonomous data architecture built on data contracts.
When you’ve successfully built an autonomous, contract-driven data platform, you’ll find the number of data contracts explode.
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? 😅
Enter your best email here:
(Don’t worry—I hate spam, too, and I’ll NEVER share your email address with anyone!)