2024
Data contracts are great for declaratively describing the data and the infrastructure you need to make that data available to others and manage it in line with your governance requirements.
The more autonomy your data platform promotes, the more our users can get done without involving us directly.
Your data contract tooling should be designed for data producers.
While a lot of people associate data contracts with data quality (and I did call my book Driving Data Quality with Data Contracts!
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?
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.
How many alerts do you get every day?
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!)