Reading List
The Architect's Library
39 books organised by topic and career stage, with annotations on reading order and what each book contributes. 11 marked as must-reads for the SA→EA transition.
Architecture Foundations
Start here. These books build the conceptual vocabulary and mental models that all advanced architecture thinking runs on.
Fundamentals of Software Architecture
Mark Richards & Neal Ford · O'Reilly
The clearest entry point into professional architecture thinking. Covers architectural characteristics, patterns (layered, microservices, event-driven, space-based), and the architect role. Read this before anything else on this list.
Clean Architecture
Robert C. Martin · Prentice Hall
The dependency rule and the stable abstractions principle are the two ideas that matter most here. The central argument — that business logic should be independent of frameworks, databases, and delivery mechanisms — is foundational for designing systems that survive technology change.
A Philosophy of Software Design
John Ousterhout · Yaknyam Press
Short and precise. The distinction between shallow and deep modules, and the idea that complexity is the primary enemy of good design, will change how you evaluate and critique architectures permanently.
Release It!
Michael Nygard · Pragmatic Bookshelf
Stability patterns for production systems: circuit breakers, timeouts, bulkheads, fail fast, handshaking. Written from post-mortem analysis of real production failures. Every distributed system architect should read this before going live.
Evolutionary & Enterprise Architecture
How to design architectures that change gracefully over time — and how to govern them at the enterprise scale.
Building Evolutionary Architectures
Neal Ford, Rebecca Parsons & Patrick Kua · O'Reilly
Introduces fitness functions — objective, measurable proxies for architectural characteristics you want to preserve. This is the book that makes architecture scientifically verifiable rather than aspirationally documented. Essential for anyone moving into an EA role.
Software Architecture: The Hard Parts
Neal Ford, Mark Richards, Pramod Sadalage & Zhamak Dehghani · O'Reilly
No best practices, only trade-offs. How to decompose a monolith, manage distributed data, handle sagas and workflows, and reason about coupling. The most practically useful book for architects working on real transformation programmes.
Enterprise Architecture as Strategy
Jeanne Ross, Peter Weill & David Robertson · Harvard Business Review Press
MIT CISR research on how operating model choices (diversification, coordination, replication, unification) determine the right EA approach. The link between business strategy and technology architecture is made explicit here with real enterprise evidence. Older but the research holds.
Patterns of Enterprise Application Architecture
Martin Fowler · Addison-Wesley
The source catalogue for most patterns you will encounter in enterprise application design: domain model, repository, unit of work, identity map, lazy loading. The patterns are named here. Knowing the names matters for precise communication.
Domain Design & Data Architecture
The two domains where most enterprise architecture complexity concentrates — how to model the business and how to manage the data.
Domain-Driven Design
Eric Evans · Addison-Wesley
Dense and slow to read, but the strategic patterns — bounded contexts, context maps, anti-corruption layers, ubiquitous language — are the primary vocabulary for drawing service boundaries. The tactical patterns (entities, aggregates, repositories) are secondary. Read Part I (Putting the Domain Model to Work) and Part IV (Strategic Design) first.
Implementing Domain-Driven Design
Vaughn Vernon · Addison-Wesley
The practical companion to Evans. Where Evans is conceptual, Vernon is hands-on. Read Evans for the why; read Vernon for the how. The chapters on aggregates and domain events are particularly precise.
Designing Data-Intensive Applications
Martin Kleppmann · O'Reilly
The authoritative guide to data systems at scale: replication, partitioning, transactions, consensus, stream processing, batch processing. The CAP theorem treatment and the chapter on the trouble with distributed systems are required reading before designing any system that spans multiple data stores.
Data Mesh
Zhamak Dehghani · O'Reilly
The case for applying domain ownership and product thinking to data. The four principles — domain ownership, data as a product, self-serve platform, federated governance — are a direct application of DDD and Team Topologies to the data layer. Essential for CDOs and architects working on data platform strategy.
The Data Warehouse Toolkit
Ralph Kimball & Margy Ross · Wiley
The dimensional modelling reference. If you advise on analytics architecture, this is the book that defines the vocabulary (fact tables, dimension tables, slowly changing dimensions, conformed dimensions). The third edition covers modern data warehouse platforms.
Integration & Distributed Systems
The vocabulary and patterns for designing systems that communicate — synchronously, asynchronously, at scale.
Enterprise Integration Patterns
Gregor Hohpe & Bobby Woolf · Addison-Wesley
The canonical vocabulary for messaging systems: channels, messages, routers, transformers, filters, endpoints. Every architect who works with event-driven architecture, service buses, or async messaging should know this vocabulary. The online companion at enterpriseintegrationpatterns.com is a useful reference.
Building Microservices
Sam Newman · O'Reilly
The most complete guide to microservices in practice: service decomposition, communication patterns, data management, security, testing, and deployment. The second edition adds significant content on Kubernetes and cloud native deployment. Read after Evans — the service boundary discussion makes more sense with DDD vocabulary.
Monolith to Microservices
Sam Newman · O'Reilly
Migration patterns for decomposing existing monoliths: strangler fig, branch by abstraction, parallel run. Directly applicable to any modernisation programme. More practical than theoretical — written from advisory experience.
Organisation Design & Delivery
Architecture is sociotechnical. These books explain why the team structure and the delivery model are architectural decisions.
Team Topologies
Matthew Skelton & Manuel Pais · IT Revolution
Four team types (stream-aligned, platform, enabling, complicated-subsystem) and three interaction modes (collaboration, X-as-a-service, facilitating). Operationalises Conway's Law as a design tool. The inverse Conway manoeuvre — restructuring teams to achieve the architecture you want — is the most powerful intervention available to an Enterprise Architect.
Accelerate
Nicole Forsgren, Jez Humble & Gene Kim · IT Revolution
The data behind software delivery performance. The four DORA metrics (deployment frequency, lead time, MTTR, change failure rate) are the fitness functions for delivery performance. The research on architecture — specifically that loosely coupled architectures enable higher DORA scores — is direct evidence for investment in architectural quality.
The Phoenix Project
Gene Kim, Kevin Behr & George Spafford · IT Revolution
A novel. Read it for the mental model it builds around flow, constraints, and the three ways of DevOps. The Goldratt theory of constraints applied to IT operations changes how you see bottlenecks in delivery pipelines. Useful for building empathy with operations teams.
Continuous Delivery
Jez Humble & Dave Farley · Addison-Wesley
The foundational text for deployment pipeline design. Defines the deployment pipeline, trunk-based development, feature toggles, and automated testing strategies. Older but still accurate — the principles have not changed even as the tools have.
Leadership & Influence
The career and leadership skills that distinguish Principal Architects from senior ones.
The Staff Engineer's Path
Tanya Reilly · O'Reilly
The best book on senior IC technical leadership: navigating ambiguity, sponsorship, visibility, influencing without authority, running projects across team boundaries. The chapter on being glue — doing essential coordination work that is invisible to promotion processes — is the most useful single chapter in the list for architects seeking principal-level roles.
Staff Engineer
Will Larson · Self-published
Interviews with 14 staff and principal engineers about how they do the job. Less conceptual than Reilly, more anecdotal — but the variety of archetypes (tech lead, solver, architect, right hand) is useful for understanding the different shapes the role takes in different organisations.
An Elegant Puzzle
Will Larson · Stripe Press
Engineering management, not architecture — but essential for architects who need to understand how engineering managers think. The hiring funnel model, succession planning, and organisational design sections are directly applicable to how EAs propose team structure changes.
Business Architecture & Strategy
The business-side vocabulary that enables architects to participate in strategy conversations.
Business Architecture: The Art and Practice of Business Transformation
William Ulrich & Neal McWhorter · Meghan-Kiffer Press
The primary reference for the BIZBOK approach to business architecture: capability maps, value streams, information maps, organisation maps. Dry but precise. The capability mapping methodology is directly applicable to enterprise investment prioritisation conversations.
Playing to Win
Roger Martin & A.G. Lafley · Harvard Business Review Press
Strategy as a cascading set of choices: winning aspiration, where to play, how to win, capabilities required, management systems required. The five-question framework is the clearest articulation of strategy available — and the direct input to a capability map. Architects who understand this framework can connect technology investments to strategic choices precisely.
Competitive Advantage
Michael Porter · Free Press
The value chain framework is still the most useful tool for identifying where technology investment creates margin. Chapters 2 and 3 (the value chain and competitive advantage) are the relevant sections. The rest is strategy theory that is less directly applicable to architecture conversations.
MarTech & Customer Experience Architecture
The domain-specific reading for architects working in marketing technology, customer data, and digital experience.
Hacking Marketing
Scott Brinker · Wiley
The argument that software development principles — agile, continuous delivery, platform thinking — apply directly to marketing management. The most useful framing for architects explaining to marketing stakeholders why their technology choices matter to delivery velocity.
Customer Data Platforms
David Raab · Wiley
The CDP market's founding document, written by the analyst who coined the category. Covers CDP architecture, use cases, evaluation criteria, and implementation patterns. Essential for any architect involved in customer data strategy.
Marketing Artificial Intelligence
Paul Roetzer & Mike Kaput · Marketing AI Institute
A practitioner's guide to AI in marketing: use case prioritisation, maturity model, team capability building. Less technical than you might want but accurate on the organisational change dimension of AI adoption in marketing.
Strategic Mapping & Systems Thinking
Frameworks for reasoning about strategic position, technology evolution, and systemic change — beyond the roadmap and the backlog.
Wardley Maps
Simon Wardley · Self-published (open access)
The foundational text for Wardley Mapping — situational awareness for technology strategy. The core insight is that components evolve from genesis through custom-built and product to commodity, and that failing to map where your components sit on this axis leads to systematically wrong build-versus-buy and investment decisions. The book is freely available online. Read chapters 2–5 first; the doctrine chapters reward a second reading once you have mapped a real system.
Read online →
The Value Flywheel Effect
David Anderson, Mark McCann & Michael O'Reilly · IT Revolution
The most practical application of Wardley Mapping to enterprise cloud and product strategy. Shows how AWS and leading engineering organisations use maps to identify where to invest for compounding advantage versus where to commoditise ruthlessly. The flywheel model — clarity of purpose, challenge and landscape, next best action, long-term innovation — connects mapping to execution in a way the original book does not.
Thinking in Systems
Donella H. Meadows · Chelsea Green Publishing
The clearest introduction to systems thinking: stocks, flows, feedback loops, delays, and leverage points. The mental models here — particularly archetypes like "fixes that fail" and "shifting the burden" — are directly applicable to diagnosing why architecture decisions produce unintended consequences. Meadows's leverage point hierarchy (from least to most effective) is one of the most useful frameworks for prioritising architectural interventions.
The Innovator's Dilemma
Clayton M. Christensen · Harvard Business Review Press
The theory of disruptive innovation maps directly onto the Wardley evolution axis: disruptors consistently enter at the commodity end, not the differentiated end. For architects advising on platform and product strategy, Christensen's framework explains why incumbent organisations systematically underinvest in commodity infrastructure and overinvest in differentiation — and how to use that pattern deliberately.
Good Strategy / Bad Strategy
Richard Rumelt · Profile Books
Rumelt's kernel of strategy — diagnosis, guiding policy, coherent actions — is the missing link between a Wardley Map and an architecture roadmap. Most "strategies" are actually goal lists or mission statements. This book makes the distinction precise and gives architects the vocabulary to challenge strategy documents that have no actual strategic logic in them.
Crossing the Chasm
Geoffrey A. Moore · Harper Business
The technology adoption lifecycle — innovators, early adopters, early majority, late majority, laggards — is the adoption-side complement to Wardley's supply-side evolution axis. The chasm between early adopters and early majority maps to the custom-built to product transition. Essential for architects advising on when to adopt emerging technologies versus when to wait for the market to settle.
Specifications & Free References
Authoritative technical specifications that are freely available and directly relevant to enterprise architecture practice.
TOGAF Standard, Version 10
The Open Group · The Open Group
The full TOGAF specification. Free to read via The Open Group website with registration; purchasable as a printed reference. The ADM chapter and the Architecture Content Framework section are the most-referenced in practice.
Read online →ArchiMate 3.2 Specification
The Open Group · The Open Group
The normative specification for the ArchiMate modelling language. Free download. Read alongside a tool like Archi to map notation concepts to visual representations.
Read online →AWS Well-Architected Framework
Amazon Web Services · AWS
The six-pillar framework (Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimisation, Sustainability). The individual pillar whitepapers are more useful than the overview. The Reliability and Security whitepapers contain the most architecture-relevant guidance.
Read online →
Site Reliability Engineering
Betsy Beyer, Chris Jones, Jennifer Petoff & Niall Richard Murphy (Google) · O'Reilly / Google
The SRE book defines SLOs, error budgets, toil, and the relationship between reliability and velocity that every architect who designs systems at scale needs to understand. Free to read online in full.
Read online →Continue exploring
This list is maintained by Santosh Pradhan and updated as new books earn their place. Missing a title that belongs here? Suggest it on LinkedIn.