Books › Cloud Architect roadmap
Best books for Cloud Architects
From one provider's services to system-wide design. It starts with a hands-on cloud guide, general architecture and cloud design patterns. The build set covers data systems, deeper architecture, service decomposition, failure design and infrastructure as code. The lead set is about communication across an organisation, cloud cost and evolution of systems over time.
12 books in 3 stages, about 4,390 pages (at least 110 hours of reading). The notes are ours, with no ratings or sales claims.
How to choose your books
A short method, so you read the right book for where you are instead of the longest list.
Find your stage
Getting started · 3 books
Cloud and architecture basics: a practical tour of one provider, general architecture and common patterns.
Jump to this stage ↓Doing the job · 5 books
Designing real systems: data trade-offs, architectural reasoning, service boundaries, failure and repeatable infrastructure.
Jump to this stage ↓Senior and leading · 4 books
Architecture as leadership: communicating across levels, managing cloud cost, evolving systems and setting strategy.
Jump to this stage ↓
If you are unsure, start one stage lower than you think. Books in a later stage assume the working knowledge the earlier ones give you.
Begin with one book
Our starting pick
Fundamentals of Software Architecture
by Mark Richards, Neal Ford · 2020
It gives you the vocabulary of architectural styles and trade-offs, so cloud services become options you reason about rather than a catalogue to memorise.
See the book ↓Then pick by your situation
Choose the next book by the problem in front of you, not by its place in the list.
If you are new to cloud and want hands-on practice with one provider
read Amazon Web Services in Action (getting started)
If you are designing for failure across several services
read Release It! (doing the job)
If the cloud bill is becoming a leadership problem
read Cloud FinOps (senior and leading)
Check it against what Cloud Architect postings ask for
These skills come from our analysis of live Cloud Architect job postings. If one is new to you, its book list sits one click away.
- Python Common
- SQL Common
- AWS Occasional
- Azure Occasional
- Kubernetes Rare
- Docker Rare
- Terraform Rare
- Go Rare
Each step on the scale reflects how often live job postings name the skill, tool or credential, based on our analysis of those postings.
Set a time budget
| Stage | Books | Pages | Reading | At 3 hrs a week |
|---|---|---|---|---|
| Getting started | 3 | 1,110 | 28 hrs | 9 wks |
| Doing the job | 5 | 2,140 | 54 hrs | 18 wks |
| Senior and leading | 4 | ≥ 1,140 | ≥ 29 hrs | ≥ 10 wks |
| All 3 stages | 12 | ≥ 4,390 | ≥ 110 hrs | ≥ 37 wks |
Treat this as a ceiling, not a target. Read one book at a time, apply it, then move on; read reference-style books in sections. Totals are approximate.
Judge any book before you buy it
Age
This list runs from 2007 (Release It!) to 2021 (Software Architecture). Older books earn their place by teaching principles that do not change. For tools and platforms, buy the latest edition.
Level
Check the stage before the title. A book from a later stage will make sense only once you have faced the problems it solves.
Format
The longest book here, Designing Data-Intensive Applications, runs about 620 pages. Read very long books as references: pick the chapter that matches the problem you have.
Fit
Ask what you will do differently the week after you finish. If you cannot answer, the book is for a different moment. Come back to it when the situation arrives.
Getting started
Cloud and architecture basics: a practical tour of one provider, general architecture and common patterns.
Amazon Web Services in Action
by Andreas Wittig, Michael Wittig · 2015
~500 pages~13 hrs to read
A hands-on tour of core AWS services: compute, storage, networking, databases and automation. A solid way to learn one platform properly before designing across several.
View book →
Start hereFundamentals of Software Architecture
by Mark Richards, Neal Ford · 2020
~430 pages~11 hrs to read
Surveys architecture styles, characteristics and the trade-offs between them, plus the architect's role. Read it early to get the vocabulary for explaining why one design fits and another does not.
View book →
Cloud Architecture Patterns
by Bill Wilder · 2012
~180 pages~5 hrs to read
Introduces patterns for scalability, availability and cost on cloud platforms, such as queues, sharding and eventual consistency. The examples centre on one provider but the patterns carry over.
View book →
Doing the job
Designing real systems: data trade-offs, architectural reasoning, service boundaries, failure and repeatable infrastructure.
Designing Data-Intensive Applications
by Martin Kleppmann · 2017
~620 pages~16 hrs to read
Explains how storage engines, replication, partitioning, transactions and stream processing work and where each breaks. The reference for judging database and messaging choices in a design.
View book →
Software Architecture: The Hard Parts
by Neal Ford, Mark Richards, Pramod Sadalage, Zhamak Dehghani · 2021
~450 pages~11 hrs to read
Works through decomposing systems, data ownership and service granularity using trade-off analysis. Read it when you face real decisions about splitting a monolith.
View book →
Building Microservices
by Sam Newman · 2015
~250 pages~6 hrs to read
Covers service boundaries, communication, deployment, testing and resilience. Useful when your designs involve many independently deployed services.
View book →
Release It!
by Michael T. Nygard · 2007
~380 pages~10 hrs to read
Catalogues the stability anti-patterns and patterns that decide whether a system survives production, from timeouts to bulkheads. Read it to design for failure instead of discovering it.
View book →Infrastructure as Code
by Kief Morris · 2016
~440 pages~11 hrs to read
Shows how to structure, test and deliver infrastructure definitions so large estates stay changeable. Helpful when you set standards for the teams building on your landing zone.
View book →
Senior and leading
Architecture as leadership: communicating across levels, managing cloud cost, evolving systems and setting strategy.
The Software Architect Elevator
by Gregor Hohpe · 2020
~370 pages~9 hrs to read
Describes how architects move between the engine room and the executive level, connecting technical choices to business decisions. Read it when your work shifts from designing systems to persuading organizations.
View book →
Cloud FinOps
by J. R. Storment, Mike Fuller · 2020
~450 pages~11 hrs to read
Explains how engineering, finance and product teams manage cloud spend together. Read it when cost becomes part of your design reviews.
View book →
Building Evolutionary Architectures
by Neal Ford, Rebecca Parsons, Patrick Kua, Pramod Sadalage · 2017
Introduces fitness functions and incremental change as ways to keep an architecture healthy as requirements move. Read it when you own the design of a system that must last years.
View book →
Good Strategy, Bad Strategy
by Richard P. Rumelt · 2011
~320 pages~8 hrs to read
Separates real strategy, a diagnosis with a coherent plan, from goals and slogans. Useful when you write migration or platform strategy and must defend it to leadership.
View book →
Book links go to Amazon and are affiliate links. As an Amazon Associate I earn from qualifying purchases.
Frequently asked questions
Which book should a Cloud Architect read first?
Fundamentals of Software Architecture by Mark Richards, Neal Ford. It gives you the vocabulary of architectural styles and trade-offs, so cloud services become options you reason about rather than a catalogue to memorise.
Do I need to read all 12 books?
No. The list is a menu, not a syllabus. Find your stage (getting started: 3, doing the job: 5, senior and leading: 4), begin with one book (we suggest Fundamentals of Software Architecture), then pick the next book by the problem you are facing at work. Come back to the others when the situation they cover arrives.
How long does it take to read these books?
The 11 books with a known page count add up to about 4,390 pages, roughly 110 hours at 1.5 minutes a page. At three hours a week that is about 37 weeks; at six hours a week, about 18. The list is meant to be read over time, one book at a time, not in one run.
Are these books up to date?
They range from 2007 (Release It!) to 2021 (Software Architecture). Older titles are included because they teach principles that have not changed; for tools and platforms, we favour recent editions. Check the edition before you buy.
Related reading
Some links are affiliate links: we earn a small commission if you buy, at no cost to you. It does not change what we list.