Skip to main content

Data contracts enable data products

·1 min

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.

Then once they have access, they need to understand the data they are accessing. That includes the structure of the data, the semantics, the version, and so on.

They also need to know what to expect from the data. How timely is it? How dependable is it? Are there any SLOs?

Without knowing these, they can’t use the data product with confidence.

All of these are key parts of a data contract.

In fact, I’d say if these are not defined, you don’t have a data product.

Or put another way, you don’t have a data product if you don’t have a data contract around it.


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? 😅

(Don’t worry—I hate spam, too, and I’ll NEVER share your email address with anyone!)


Andrew Jones
Author
Andrew Jones
I build data platforms that reduce risk and drive revenue.