Partnership and separate ways (DDD)
Two context-map patterns: two teams that plan and release together because they succeed or fail together, or two contexts that do not integrate at all.
In a partnership neither team is upstream: their bounded contexts depend on each other, so they coordinate plans, interfaces and releases. It works for two teams launching one feature; it gets expensive as a permanent arrangement, and often turns into a shared kernel or a customer-supplier relationship.
Separate ways is the decision not to integrate: the value is too small for the cost, so each side does its own thing, even if it means duplicated data or a manual step. Both are labels on a context map, described in the Evans DDD Reference. By Conway’s law, the label usually follows how the teams actually work.
Sources
- Domain Language: DDD Reference domainlanguage.com
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.
- 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.
- Shared kernel (DDD): A small part of the domain model that two teams own together and change only by agreement, such as shared types or a common library.
- Conway’s law: Systems end up shaped like the communication structure of the organization that builds them.
