Books › Platform Engineer roadmap
Best books for Platform Engineers
This list is about the platform as a product: the infrastructure code it is built from, the delivery pipeline that carries changes to production, and the organizational design that decides who owns what. Nothing here teaches one cloud or one tool; you learn those by building a paved path. The books assume you can already run a service in a container and read a deployment log. They are the reading you need to design something other teams will choose to use, rather than something they must.
8 books in 3 stages, about 2,910 pages (73 hours of reading). The notes are ours, with no ratings or sales claims.
See the full Platform Engineer roadmap →Best courses for Platform Engineers →
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 · 1 books
Infrastructure as code. Read this first to learn how environments, state and drift are managed in code, the layer every platform sits on.
Jump to this stage ↓Doing the job · 4 books
The delivery and runtime layer: pipelines, Terraform, and the Kubernetes patterns you will turn into templates for developers. Read these while you build your first paved path.
Jump to this stage ↓Senior and leading · 3 books
Team design and delivery evidence. These books explain why a platform succeeds or fails on adoption, and how to measure it. Pick them up when you are choosing what the platform should and should not offer.
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
Infrastructure as Code
by Kief Morris · 2021
It covers the declarative layer that every later book assumes: state, environments, drift and testing. Once you know that, the Terraform and Kubernetes books make sense in order.
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 about to write a shared Terraform module that several teams will reuse
read Terraform (doing the job)
If you have to convince leadership that the platform team should exist, and what it should own
read Team Topologies (senior and leading)
If you need evidence for which delivery practices to standardize first
read Accelerate (senior and leading)
Set a time budget
| Stage | Books | Pages | Reading | At 3 hrs a week |
|---|---|---|---|---|
| Getting started | 1 | 350 | 9 hrs | 3 wks |
| Doing the job | 4 | 1,590 | 40 hrs | 13 wks |
| Senior and leading | 3 | 970 | 24 hrs | 8 wks |
| All 3 stages | 8 | 2,910 | 73 hrs | 24 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.
Judge any book before you buy it
Age
This list runs from 2010 (Continuous Delivery) to 2021 (Infrastructure as Code). 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, Continuous Delivery, runs about 510 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
Infrastructure as code. Read this first to learn how environments, state and drift are managed in code, the layer every platform sits on.
- Start here
Infrastructure as Code
by Kief Morris · 2021
~350 pages~9 hrs to read
Patterns for managing cloud infrastructure with code: environments, configuration drift, testing and secrets. It describes the declarative layer most platforms are built on.
View book →
Doing the job
The delivery and runtime layer: pipelines, Terraform, and the Kubernetes patterns you will turn into templates for developers. Read these while you build your first paved path.
Terraform: Up & Running
by Yevgeniy Brikman · 2017
~290 pages~7 hrs to read
A practical guide to Terraform state, modules and team workflows. Read the module chapters when you start writing building blocks that other teams will reuse.
View book →Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation
by Jez Humble, David Farley · 2010
~510 pages~13 hrs to read
The deployment pipeline as a concept: how any change gets from commit to production safely and repeatedly. Platform teams turn these ideas into the paved path developers actually use.
View book →Kubernetes Patterns: Reusable Elements for Designing Cloud-Native Applications
by Bilgin Ibryam, Roland Huß · 2019
~390 pages~10 hrs to read
Reusable design patterns for workloads on Kubernetes: how applications should be packaged, configured and scaled. Use it as the reference when you write the templates developers will copy.
View book →Cloud Native Patterns: Designing Change-Tolerant Software
by Cornelia Davis · 2019
~400 pages~10 hrs to read
How cloud-native systems are structured and operated across many services. Platform leads need this picture before they decide what to standardize and what to leave to teams.
View book →
Senior and leading
Team design and delivery evidence. These books explain why a platform succeeds or fails on adoption, and how to measure it. Pick them up when you are choosing what the platform should and should not offer.

Team Topologies
by Matthew Skelton, Manuel Pais · 2019
~240 pages~6 hrs to read
How to organize teams around the services and platforms they own, and why a platform team exists to reduce the cognitive load of the teams that use it. Read it before you design the interface your developers will use.
View book →
Accelerate: The Science of Lean Software and DevOps
by Nicole Forsgren, Jez Humble, Gene Kim · 2018
~290 pages~7 hrs to read
The research behind the DORA delivery metrics and the practices that predict speed and stability. Use it to choose what your platform measures and to argue for changes with evidence.
View book →The DevOps Handbook
by Gene Kim, Jez Humble, Patrick Debois, John Willis · 2016
~440 pages~11 hrs to read
Case studies and practices from high-performing delivery organizations, including the flow and feedback principles that platform work is meant to support.
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 Platform Engineer read first?
Infrastructure as Code by Kief Morris. It covers the declarative layer that every later book assumes: state, environments, drift and testing. Once you know that, the Terraform and Kubernetes books make sense in order.
Do I need to read all 8 books?
No. The list is a menu, not a syllabus. Find your stage (getting started: 1, doing the job: 4, senior and leading: 3), begin with one book (we suggest Infrastructure as Code), 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?
All 8 books add up to about 2,910 pages, roughly 73 hours at 1.5 minutes a page. At three hours a week that is about 24 weeks; at six hours a week, about 12. 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 2010 (Continuous Delivery) to 2021 (Infrastructure as Code). Older titles are included because they teach principles that have not changed; for tools and platforms, we favor 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.