Data contract¶
A data contract specifies a product's reusable producer promises: its interface, meaning, quality expectations, compatibility and change behaviour. Those promises should be versioned, testable and tied to an accountable producer.
A contract alone does not describe every consumer's purpose or obligations. A sharing agreement references the contract and connects it to a particular consumption relationship.
A schema check can verify shape. Contract validation also needs semantic and operational evidence where the promises require it.
Join the argument
Agree, challenge or add evidence
Architecture improves when its assumptions are challenged. Say which kind of contribution you're making:
- Challenge I disagree because…
- Evidence We've seen this too…
- Question How would this work when…?
- Alternative Another way to approach this…
- Extension This also implies…
Please keep clients, employers and colleagues unidentifiable. Strong contributions may be quoted and credited on this site. Read the contribution guidelines and the privacy notice.
Comments are provided by giscus and stored on GitHub. Posting requires a GitHub account.