Architecture as Code is founded on core principles that enable successful implementation of codified system architecture. These principles span the entire system landscape and provide a holistic view of architecture management.
The diagram illustrates the key dimensions of Architecture as Code covered in this chapter, including declarative architecture definition, holistic codification, immutable patterns, testability, and documentation as code.
The declarative approach in Architecture as Code describes the desired system state at every level – from application components to infrastructure. This contrasts with imperative programming, where each step must be specified explicitly. Infrastructure as Code tooling draws the same distinction between declarative and imperative approaches (Source [29]).
Primary topics explored
- Declarative architecture definition
- Holistic perspective on codification
- Implementation timeline for Architecture as Code
- Architecture as a single source of truth
- Immutable architecture patterns
- Testability at the architecture level
About Architecture as Code
Infrastructure as Code represents a fundamental change in how we manage and develop IT infrastructure. This book provides organisations with practical guidance for implementing IaC principles whilst fulfilling local compliance requirements and optimising costs.
The book covers everything from fundamental principles and tools to advanced implementation strategies, security aspects, and organisational changes required for successful IaC adoption.
IT architects, DevOps teams, developers, and decision-makers within organisations.
Gunnar Nordqvist
Conceived, directed and published the books of The Transformed Architecture.
Continue with the full chapter
Chapter 2: Fundamental Principles of Architecture as Code in Architecture as Code gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “Foundations” and is one of 38 drawn from the manuscript.