Skip to main content

Data contracts as part of the workflow

·1 min

Data contracts, like any documentation or specification, will only be kept updated if they are part of the workflow.

That’s why it’s so important to know who will be owning and updating the data contract when designing the implementation.

Is it going to be software engineers? Allow them to define the data contract in code, alongside the rest of their code, and managed using the same source control.

Is it going to be data engineers? Extend the dbt model config to hold the extra metadata you need for your data contracts.

Is it going to be a Salesforce admin? Provide a custom UI that interacts with the Salesforce API so they can add the extra metadata and verify the changes they have made to Salesforce.

Whatever it is, ensure data contracts are part of the workflow.


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.