Terraform at Scale
Yuki Tanabe
State layout, module boundaries, drift, and the organizational patterns that keep Terraform usable past fifty engineers.
Reading track
Everything needed to build and run an internal platform on managed Kubernetes and Terraform without losing your users.
Four titles, $226 separately — $189 together. You save $37. Every title is delivered DRM-free in PDF and EPUB, and updates to a new edition are included.
Four complete titles. Each one is also sold separately, at the price shown, if you only need part of the track.
Yuki Tanabe
State layout, module boundaries, drift, and the organizational patterns that keep Terraform usable past fifty engineers.
Sam Okonkwo and Yuki Tanabe
What EKS and GKE do differently, where the managed control plane ends, and who owns the parts in between.
Yuki Tanabe and Aaron Whitfield
The narrow path between too much abstraction and none at all, from someone maintaining a platform for four thousand engineers.
Sam Okonkwo
How to instrument a cloud system so that during an incident the data answers your question instead of describing your dashboards.
Our editors sequenced this track. You can read it in any order you like, but this is the path where each title pays for the next.
Practitioner · Multi-cloud · 338 pages
State layout and module boundaries come first — the cheapest decisions to make now and the most expensive to revisit once a platform has users.
Practitioner · Multi-cloud · 364 pages
The runtime your golden paths will target. Node lifecycle, cluster networking, and workload identity, as EKS and GKE actually implement them.
Advanced · Multi-cloud · 340 pages
The synthesis: escapable golden paths, interfaces that degrade to the raw provider, and adoption measured by something other than a mandate.
Practitioner · Multi-cloud · 322 pages
Before you invite users, make the platform legible. A platform nobody can debug is a platform nobody will trust with a production workload.