Terraform in Production
Operating a Terraform estate as a production system: state as a database with locking and corruption modes, blast radius and the arithmetic that sets the state boundary, drift and the plan that does not match the apply, refactoring live infrastructure, modules across many teams, and who is allowed to apply. Lifetime updates included.
What you'll learn
Curriculum
9 modules · 35 lessonsState Is a Database You Operate
The state file as a system with consistency, locking and corruption modes, rather than a file you never look at.
Blast Radius and the State Boundary
How you split state decides what one mistake can destroy, and the arithmetic that sets the boundary.
The Plan Is a Prediction
What the plan is actually claiming, and the several ways reality declines to match it.
Dependencies and Apply Order
The graph Terraform builds, the edges it cannot see, and what a partial apply leaves behind.
Modules at Organisation Scale
Sharing infrastructure definitions across many teams without a registry full of things nobody can change.
Refactoring Live Infrastructure
Changing the shape of the code without changing what is running, which the tool does not do for you.
Testing and Policy
What can be verified before an apply, and what can only be verified by applying.
Running It for Many Teams
The platform side: bootstrapping, account structure, who is allowed to apply, and staying current.
Capstone
A complete Terraform estate design combining every module, with explicit tradeoffs.
About the Author

Sharon Sahadevan
AI Infrastructure Engineer
Building production GPU clusters on Kubernetes. H100s, large-scale model serving, and end-to-end ML infrastructure across Azure and AWS.
10+ years designing cloud-native platforms with deep expertise in Kubernetes orchestration, GitOps (Argo CD), Terraform, and MLOps pipelines for LLM deployment.
Author of KubeNatives, a weekly newsletter read by 3,000+ DevOps and ML engineers for production insights on K8s internals, GPU scheduling, and model-serving patterns.