Large-Scale C++ Volume I: Process and Architecture

In a large C++ codebase, architecture is shaped not only by abstractions, but also by the physical organization of components, files, and dependencies. Large-Scale C++ Volume I: Process and Architecture by John Lakos makes that often-overlooked side of software design its central concern, connecting C++ language and build-system details to the structure of real projects.

Architecture you can see in the build

Lakos starts with the goals and trade-offs behind large-scale development, including the relationship between application and library software, collaboration and reuse, and the role of physical design. From there, he examines how compiling, linking, declarations, definitions, and headers influence component design. The result is a close look at why architectural decisions show up in everyday engineering work—not just in diagrams.

From components to coherent systems

The book develops a component-based approach and follows it through packaging and design rules. It considers physical aggregation, source-code organization, packages and package groups, and the alignment of logical structure with physical structure. These topics help readers reason about how software belongs together—and how to keep that organization understandable as a system grows.

Managing dependencies at scale

A substantial section focuses on physical design and factoring: avoiding poor modularity, reducing unnecessary compile-time and link-time dependencies, preventing cycles, and comparing lateral with layered architectures. Rather than treating these as abstract concerns, Lakos relates them to the practical mechanics of building and evolving C++ software.

A detailed reference for C++ practitioners

With chapters on motivation, compilers and linkers, packaging, and physical design, this first volume is suited to experienced C++ developers, software architects, and project leaders who need to make design decisions across a codebase. Its emphasis is specific: understanding how components and dependencies affect the maintainability and architecture of large C++ systems.

For readers who want to think beyond individual classes and consider how a whole C++ project is assembled, this volume offers a thorough, engineering-focused perspective.