📙 Looking for more on data contracts? Check out my book! 📙 2024
Yesterday I wrote about Conway’s law and the challenges it causes in organisations where data teams are placed in a separate part of the organisation to where the data is generated.
Unless the data contract is being used, no one is going to put effort into creating or maintaining it.
Yesterday I wrote how data teams often start with accessibility, which helps you get started, but leads to a number of problems:
I wrote yesterday about the patterns of data contracts, giving a small example.
Data contracts is really a set of patterns you can apply to your organisation, once you have data contracts defined and containing sufficient information to drive those patterns.
JSON Schema is the most widely adopted representation of JSON APIs.
Data contracts, like any documentation or specification, will only be kept updated if they are part of the workflow.
One of the benefits of data contracts is the amount of automation they unlock.
Software engineers invest significantly to prevent bugs being deployed to production environments using techniques and tools such as:
When starting your data contracts implementation, plan for scale, but start small.
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!)