Infrastructure¶
Ship a running instance safely across environments — containers, orchestration, deployment strategies, pipelines, infrastructure as code, and the network/scaling mechanics that keep it running.
Topics¶
| # | Topic | What you'll learn |
|---|---|---|
| 01 | Containers and Docker | Package an application into a container image and run it. |
| 02 | Kubernetes Orchestration | Run many containers together with Pods, Deployments, and Services. |
| 03 | Deployment Strategies | Replace a running version safely — rolling, blue-green, canary. |
| 04 | CI/CD Pipelines | Get code from commit to a deployable artifact and trigger a deploy. |
| 05 | Infrastructure as Code | Declare and provision infrastructure as version-controlled code. |
| 06 | Multi-Region Deployment | Run a service across regions — active-active vs. active-passive. |
| 07 | Autoscaling | Adjust running capacity automatically as load changes. |
| 08 | GitOps (Argo CD, Flux) | Drive delivery from a git repo as the pull-based source of truth. |
| 09 | Virtual Machine | Use VMs as a deployment unit and know when to choose them over containers. |
| 10 | Network | Understand the wire-level mechanics (TCP/UDP, TLS, HTTP evolution) and cloud network architecture (VPC) infrastructure runs on. |
How to use this section¶
Each topic has four depth levels — junior → middle → senior → professional. Start at your level and climb. Containers and Docker is the foundation everything else packages and runs; Kubernetes Orchestration and Deployment Strategies build on it; CI/CD Pipelines and Infrastructure as Code are how changes get there in the first place, with GitOps as a pull-based alternative to pipeline-driven delivery. Multi-Region Deployment and Autoscaling are the operational mechanics that keep a running system available under load, and Network (including cloud network architecture / VPC) is the substrate all of it runs on. Virtual Machine is the alternative deployment unit to containers, useful when isolation or compliance needs outweigh container density.
Recovering from a large-scale disaster (RPO/RTO, failover drills) now lives in Craftsmanship → On Production → Disaster Recovery, alongside the rest of the post-launch reliability practice.
Part of the Engineer Knowledge roadmap. See also On Production for what happens to a system once it's running on this infrastructure.