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.
Ben Watson at Nandos, a South African restaurant chain operating in 30 countries, has a great write up on their modern data platform with data mesh and data contracts.
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.
I wrote yesterday how it’s best to validate as early as possible.
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.
Yesterday I wrote about Conway’s law and the challenges it causes in organisations where data teams are placed in a separate part of the organisation to where the data is generated.
A self-serve data platform is one where its users can autonomously create, manage and consume data.
A data platform is one of those terms that can have a different meaning for different people.
The change of focus from accessibility to dependability is a business transformation, and like any transformation it is going to take some time.
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!)