1.6. Treaty Relationships
If an organization's overall architecture could be described as a single fortress, we wouldn't need the software fortress model. We could use simple three-tier (or N-tier) diagrams to explain our architecture. The reason we need the software fortress model is that enterprises are not mono-lithic. They have many software fortresses. It is the relationship between these different fortresses that we are trying to model and understand.
When one or more fortresses work together to accomplish a higher-level activity, we say that the fortresses are allies of each other. They coordinate their work through treaty relationships.
The fact that the cooperating fortresses are allies doesn't mean that they trust each other. They still ...
Get Software Fortresses: Modeling Enterprise Architectures now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
