Consumer-Driven Contracts: A Service Evolution Pattern¶
Robinson, I. (2006). Consumer-Driven Contracts: A Service Evolution Pattern: A Service Evolution Pattern.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Nominal vs. Actual Control
- The software instance is structurally identical: the nominal register is the declared API schema, the actual register is the observed response behaviour, and consumers "code to the actual" — depending on what the endpoint really returns rather than what the spec promises — so the gap between declared and observed behaviour is the same nominal/actual split, recognisable as normalization of deviance under another name, and remediated by contract-testing that samples the actual responses rather than the documentation.
This sourceDescribes API contract drift between a provider's declared schema and its actual responses, and consumer-driven contract testing that samples actual interactions rather than the documentation — the software instance and its remedy.
- The software instance is structurally identical: the nominal register is the declared API schema, the actual register is the observed response behaviour, and consumers "code to the actual" — depending on what the endpoint really returns rather than what the spec promises — so the gap between declared and observed behaviour is the same nominal/actual split, recognisable as normalization of deviance under another name, and remediated by contract-testing that samples the actual responses rather than the documentation.
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:b16d831fddb6 · see in the full table