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.
Conformist is the honest label for “we just use their API the way it is”. It is a reasonable choice when the upstream model is decent, the integration is small or the upstream is a big vendor that will never change for you: a payment provider, a national e-invoicing system, a cloud API.
The cost shows up later. Their names, statuses and quirks spread through your code, and when they change or you replace them, every place has to change. The alternative is an anti-corruption layer that translates at one border. If the upstream team does listen to you, aim for customer-supplier instead. All three are labels on a context map.
Related terms
- 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.
- Anti-corruption layer (ACL): A translation layer between your model and a legacy or external system, so its data shapes and quirks do not leak into your code.
- 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.
