📙 Looking for more on data contracts? Check out my book! 📙 2024
I was giving a talk a few weeks ago on data contracts, and through it one audience member seemed particularly engaged, nodding along throughout.
Many data engineering teams spend a lot of their time struggling to deal with upstream data.
Following on from yesterday’s note on the API Mandate and data contracts, I wan’t to be clear you don’t need to mandate data contracts to get adoption.
In 2002 Jeff Bezos issued the now infamous API Mandate which stated the following:
Every workflow and process you have has a cost, including the following:
I wrote yesterday how it’s best to validate as early as possible.
It’s always best to do your data validation as early as possible as that:
As a software engineer, we would never make our database directly available to consumers.
I see data contracts as being at the cross-section of best practices.
I mentioned yesterday how by using friction we can influence how users behave and how the business is organised.
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!)