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.
Supported in partVerified against the work's full text
Robinson supports consumer-expectation tests as the remedy for contract coupling; he does not describe declared-vs-observed drift, sampling real responses, or normalization of deviance.
“The Schematron assertions in our example look very much like the kinds of tests that, if implemented by the provider, might help ensure the provider continues to meet its commitments to its clients.”
- 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¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:b16d831fddb6 · see in the full table