2024
David Jayatillake published an interesting post recently titled “We don’t need data contracts”.
If you want your users to use the tools you are building or onboarding, it’s important to implement them exactly where they expect them to be.
The definition and evolution of the data contract should be a collaboration between the data producers and the data consumers.
An article that has stayed with me since it was published back in 2015 is Dan McKinley’s Choose Boring Technology.
Robert Sahlin wrote a nice post on the data platform at MatHem, a Swedish retailer.
Over on Medium I’ve published a post about a contract-based data platform, which is an updated version of my post to this newsletter back in December.
A few months back Whatnot published a great post on how they are using data contracts.
Data contracts set the expectations for the data.
I mentioned yesterday that one way to reduce the amount of data transformations (and the costs of them) is to challenge the assumption we need to bring all data centrally before it can be useful.
Most of the problems we’re solving in our organisations are not unique to us:
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!)