Customer-supplier (upstream and downstream)
A relationship between two teams where the upstream team plans its changes with the needs of the downstream team that depends on it.
Upstream is the team whose model or API others consume; downstream is the team that has to live with what upstream ships. In a customer-supplier relationship the downstream team is treated like a customer: its needs go into upstream’s backlog, and changes that would break it are negotiated, not announced.
The agreement is cheapest to enforce in code: consumer-driven contracts fail upstream’s build when it breaks a consumer, and API versioning gives downstream time to move. When upstream has no reason to listen, the relationship degrades into conformist or the downstream team builds an anti-corruption layer. It is one of the labels on a context map.
Related terms
- Context map (DDD): A diagram of the bounded contexts in a system and the kind of relationship between each pair: who depends on whom and how models are translated.
- Conformist (DDD): A downstream team adopts the upstream system’s model as it is, without translating it, because it cannot influence it and translation is not worth it.
- Consumer-driven contracts (contract testing): Each consumer of an API writes down what it actually uses, and the provider’s build checks every change against those expectations before release.
- API versioning: Giving an API contract explicit versions so consumers can upgrade on their own schedule, and retiring old versions with notice.
