📙 Looking for more on data contracts? Check out my book! 📙 2024
When building a (data) platform you end up thinking a lot about the abstractions you are providing, and the trade-offs they cause.
What key business processes depend on your data?
On the latest episode of the Data & AI podcast I joined Deepak and Dan as we demystified data contracts.
When building a data platform I’m often thinking about how to reduce friction for my users.
Many data platforms start with a change data capture (CDC) service to extract data from an organisations transactional databases - the source of truth for their most valuable data.
There is strong alignment between the goals of data mesh and data contracts.
I enjoyed this post by Ryan Collingwood on what the 🤬 is a Data Contract?
Data evolves over time, and as such a data contract needs to support that.
While data products are for people, they still require an interface that allows people to access them - usually through a system such as a database, an analytics tool, a notebook, and so on.
Data is at the heart of every meaningful service, and it’s the effective use of that data which builds a product, and a business.
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!)