contract drift

When the data a server actually sends slowly stops matching what its clients expect, usually without anyone noticing until something breaks.

In more detail

Drift happens when a field is renamed, removed or changes type on one side only. Sharing schemas, generating clients from one specification and validating outgoing responses in tests all catch drift before it reaches users.

Example

In this course: Drift goes unnoticed while each side's own tests stay green. Verifying the provider against consumer contracts on every build catches it before deployment.

Related terms

Taught in

References