📙 Looking for more on data contracts? Check out my book! 📙 2024
The initial idea for data contracts was to create an interface through which reliable and well-structured data could be made available to consumers.
Welcome to my new and improved newsletter!
Following on from yesterdays post, perhaps the key point is to make the impact of data issues visible.
Yesterday I talked to software engineers about data quality.
Miro recently wrote up their adoption of data contracts in Data Products Reliability: The Power of Metadata.
Barr Moses, Co-Founder & CEO at Monte Carlo, posted some interesting data on data incidents on LinkedIn.
Some people argue data contracts won’t work in their organisation.
Traditionally, data governance has been implemented using people and processes.
I joined Ryan Collingwood and Lilly Ryan on the Thoughtworks Technology Podcast to talk about data contracts, what they are, and why they matter.
Data contracts are often viewed as part of a data mesh implementation, but you don’t need to be transforming to a data mesh architecture to benefit from data contracts.
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!)