Architecture as Code

Part I. Architecture and Implementation

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 Part I 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].

Consider a typical 10-story office building. A building architect is responsible for that building’s structural integrity (its architecture). To ensure the building will be structurally sound, the architect, together with the structural engineer, takes into account loads, spans, stresses, weather, ground topology, building materials, and a variety of other factors. They document all of this in the building plans, which the construction contractors use to construct (or implement) the architecture. Those who work in the completed office building assume that the building plan was implemented according to the specifications and constraints the architect defined, so that the ceiling won’t suddenly collapse or the walls suddenly buckle under extreme load.

Now consider a software system or product. It also has an architect–a software architect–who creates a structure (an architecture) to ensure that the system meets certain critical capabilities, such as scalability, responsiveness, ...