Part II. Structure

Part I defined the mechanics of evolutionary architecture—​how teams build fitness functions, deployment pipelines, and other mechanisms to govern and evolve software projects.

Part II concerns the structure of architecture. The topology of a software system has a huge impact on its evolvability. Structural design is a huge portion of the architect’s job, and certain principles allow for cleaner evolution over time when designed correctly.

Modern systems have forced architects to consider the impact of data and its evolution alongside architecture, reflected in our chapters about that overlap.