Architecture as Code

Chapter 1. The Intersections of Architecture

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 1st chapter of the final book. Please note that the GitHub repo will be made active later on.

If you’d like to be actively involved in reviewing and commenting on this draft, please reach out to the editor at [e-mail].

As inconvenient as it is, software architecture is highly synergistic with all the other parts of the software development process and ecosystem. In other words, as teams change different facets of the development process, it influences software architecture… and vice versa.

Software architecture doesn’t exist in a silo–it is highly interconnected with all the other parts of building software. However, software architects have a unique perspective. We understand the system’s overall structure, the development team’s capabilities, and the details of infrastructure, data, and lots of other things. We often make decisions in software architecture that affect how software is built, but one constant problem that software architects face is how to make sure that what we design is what teams actually implement. For example, an architect may design a loosely coupled microservices architecture, but the development team could end up tying all the services together ...