Skip to main content

Data products and data contracts

·1 min

Data contracts underpin data products.

With data contracts we are explicitly saying data should be treated as a product by those teams who produce the data. That data is then provided through a stable interface.

But that’s just the technical side of a data product.

There’s also the people/culture side where data producing teams (particular product engineering teams) are treating their data as a product.

They understand why the data is important, for who, and for what reasons.

They offer a migration path as the data evolves, and deprecate previous versions of the product.

Data contracts on its own can’t make teams treat data as a product.

They can’t change the culture.

Only people can.


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!)

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