Bring data teams together with data contracts
Key takeaways
- You will learn, how to use data contracts as a collaboration tool to discuss data requirements.
- You will also learn, how data contracts be used for automation, later in the development process.
- You will understand, that a data contract is more than just a schema.
- You will be able to write your first data contract as a YAML document.
In the world of software engineering, we know how important explicit, clearly documented, and stable interfaces are, and what effects unannounced breaking changes can have. We use Swagger, OpenAPI or AsyncAPI for this purpose, and on top of that tools for code generation or contract-based testing. In the world of data, there has never been anything comparable, and unannounced breaking changes, such as schema changes, are unfortunately common there.
Data contracts are something like OpenAPI, but for data. Data contracts bring the producer of data and their consumers together. Data Contracts allow the specification of the structure of the data, and its quality requirements. Data contracts contain sample data, and a semantic description. Data contracts specify terms of use for the data. Consumers can rely on data contracts.
In this talk, I want to introduce the Data Contract Specification (datacontract.com) in more detail. I want to show how interfaces are described in the world of data, and how this interface documentation differs from the world of software engineering. We will design an interface together in Data Contract Studio (studio.datacontract.com), and then use the Data Contract CLI (github.com/datacontract/cli) to simulate detecting a breaking change.
- Date
- 2023-11-10
- Time
- 08:30 - 09:30
- Conference / Event
- Øredev Developer Conference
- Venue
- Malmö Mässan, Exhibition & Conference Center, Malmö