For years, the phrase "as code" has been tightly associated with hard, technically defined artifacts such as infrastructure, pipelines, and configurations. In recent years the same operating model has entered the softer domains of an organisation. When we speak about compliance as code, Architecture as Code, documentation as code, knowledge as code, and culture as code, we point to the same underlying ambition: describing complex, often human-dependent processes in machine-readable, version-controlled, and executable formats. This chapter explores how the disciplines overlap, the synergies they create, and how organisations can benefit from their combined strength.
By the end of this chapter, you will be able to:
The following mind maps illustrate the key concepts and relationships within the soft "as code" ecosystem. They visualise how the different disciplines connect through their shared DNA, each playing distinct roles while reinforcing one another to create organisational synergies.
Primary topics explored
- Introduction
- Learning Objectives
- A Shared DNA
- Compliance as Code as the Quality Engine
- Architecture as Code as the Hub
- Documentation as Code as the Communication Layer
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 23: The Interplay Between Soft As Code Disciplines in Architecture as Code gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “Experience and Best Practices” and is one of 38 drawn from the manuscript.