Architecture as Code · Whitepaper

Chapter 24 · Experience and Best Practices

Modern Best Practices and Lessons Learned

Key insights from Chapter 24 of "Architecture as Code"

Author Gunnar Nordqvist
Published 23 October 2025
Build number 2025.10
diagram-refresh governance-automation ai-collaboration
Figure 24.1 shows best practices for repository structure, module design, and versioning strategies.
Figure 24.1 shows best practices for repository structure, module design, and versioning strategies.

Architecture as Code practices evolve rapidly as teams balance platform stability, compliance expectations, and product agility. The most successful organisations pair disciplined engineering routines with human-centred ways of working, ensuring that automation never removes context or accountability. This chapter distils contemporary lessons learned from teams operating at scale across finance, public services, healthcare, media, and high-growth technology sectors. Every section emphasises globally applicable guidance while using British English terminology.

The following mind maps present the interconnected practice areas that underpin resilient Architecture as Code delivery, helping teams navigate improvements without treating topics in isolation.

The table below introduces the seven practice clusters explored throughout this chapter, and each mind map is read from top to bottom, emphasising the sequence in which many organisations layer their capabilities. The sections that follow provide narrative bridges between these themes so that teams can adapt the ideas to their own regulatory, cultural, and technological environments.

Primary topics explored

  1. A Holistic Landscape of Practice Areas
  2. Code Organisation and Modularity
  3. Security and Compliance Patterns
  4. Performance and Scalability Strategies
  5. Governance and Policy Enablement
  6. Talent Development and Skills Evolution

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.

Who should read this

IT architects, DevOps teams, developers, and decision-makers within organisations.

Portrait of Gunnar Nordqvist

Gunnar Nordqvist

Conceived, directed and published the books of The Transformed Architecture.

Continue with the full chapter

Read the full chapter online

Chapter 24: Best Practices and Lessons Learned 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.