Architecture models how the system and its elements hang together. Yet the true complexity of architectural dependencies can be highly elusive. We share architectural information when we build integrated systems creating complex and hard to find dependencies. This article introduces a simple modelling approach to analyse of architectural dependencies within complex technology environments.
Every developer has had to integrate with another system, API or component at one point or another. And, often, a business feature must span systems. If you’ve been on a project like this or have one in the pipeline then this article provides strategies to handle the change. Also, this article covers separating system boundaries and what that means for your technical design.