Skip to main content

Interfaces, communication, and data

·1 min

When:

  • One team provides infrastructure for another
  • One team provides code libraries for another
  • One team provides an API for another
  • One team provides data for another

Each of those are a product being delivered by one team to the next, and that product must meet the consumers requirements.

That requires communication, and eventually an agreement on what’s being delivered, at what performance, at what reliability, etc.

The delivery for each is an interface. For example, a new public method in the code library, or a new endpoint in the API.

There’s no reason data, or data products, need to be treated differently, if the data is as important to the business as those other products.


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

    Newsletter

    (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.