Home › Key concepts › Data contracts

Key concept · Walk (intermediate) · the same on every platform

Data contracts

A written agreement between the team that produces data and the teams that use it.

What it is

A data contract states the schema, meaning, quality rules and freshness a dataset promises, and who owns it. It is checked automatically, so a breaking change fails the producer's pull request instead of breaking a consumer's dashboard. ODCS is an open standard for writing them.

Why it matters

Most data breakages come from an upstream change nobody told you about.

An example

The app team renames 'amount' to 'total'; their CI fails against the contract before the change is merged.

The common mistake

A contract written once in a wiki and never checked by a machine.

Where you meet it on each platform

The idea stays the same; only the product name changes.

JobAWSAzureGoogle CloudDatabricksOpen source
Data qualitychecks that stop bad data before anyone uses itGlue Data QualityPurview data qualityDataplex data qualityPipeline expectationsGreat Expectations or Soda
CI/CDevery change is tested and shipped by a pipeline, not by handGitHub Actions + CodeDeployGitHub Actions or Azure PipelinesGitHub Actions + Cloud BuildGitHub Actions + bundlesGitHub Actions

Related ideas

Where it shows up

Part of the Walk level on these paths: Data Engineering (trusting data).