DevOps
55 boards, 50 lessons, 436 review questions and 14 narrated videos, in 10 chapters. Read them in order. Each chapter builds on the one before.
Start here → The Shipping Container (Docker)
Contents
Part one · Build
1Containers & Docker5 lessons
A container from first principles - what the shipping-container analogy gets right, running one, writing the recipe that builds it, and running many at once.
2Kubernetes13 lessons
From one crate to a fleet - the cluster, pods and deployments, self-healing and autoscaling, and how traffic actually gets in through services and ingress.
- 01From One Crate to a Fleet (why Kubernetes)9 Q
- 02VM vs Kubernetes, and what a cluster actually is8 Q
- 03The Harbor Master (pods, deployments, services)11 Q
- 04Pods, ReplicaSets & Deployments (the ownership chain)8 Q
- 05Self-Healing & Autoscaling9 Q
- 06Config, Secrets & Storage9 Q
- 07The Restore Nobody Tested8 Q
- 08Getting Traffic In (Services & Ingress)9 Q
- 09Services & Ingress, from the inside8 Q
- 10Under the Hood (Kubernetes Internals)9 Q
- 11The cluster that won't sail (Kubernetes troubleshooting)7 Q
- 12Where a ship may berth8 Q
- 13The Sandbox Architecture8 Q
Part two · Scale
3Regions, networks and doors7 lessons
Where your code actually lives when it 'runs in the cloud', and who may reach it - regions, private networks, routes, firewalls, peering, load balancers and IAM, on one map.
4One machine, one proxy, one bucket3 lessons
The same ground at the size of one box: a VM and SSH, an EC2 instance, nginx in front of it, and a bucket behind a CDN.
5Who may do what6 lessons
The two planes, why IAM has so many boxes, a folder-level lock on a bucket, and borrowed passes across accounts - IRSA, OIDC and a Lambda writing next door.
6Rooms someone else runs3 lessons
The services a cloud runs for you - a database, a queue, a function - then the same harbour on your laptop with LocalStack, then the bill nobody reads.
7CI/CD, IaC & Operations8 lessons
Provisioning as code and one cargo plan for three ports, the assembly line that ships a commit and the parts it trusts, and the watchtower and least-privilege habits that keep it safe once it's there.
- 01Git: the ledger every change signs (commits, branches, merge and rebase)8 Q
- 02Infrastructure as Code & GitOps9 Q
- 03One cargo plan, three ports7 Q
- 04The Assembly Line (CI/CD)11 Q
- 05The Watchtower (Observability)9 Q
- 06The Page at 3 a.m. (Incident Response)8 Q
- 07Least Privilege & the 12-Factor App9 Q
- 08The part someone else made8 Q
8Ship it3 lessons
One small app taken all the way: tested, built, scanned and signed on the line, synced to a cluster from git and rolled back the same way, then watched until an alarm fires on a broken promise.
9AI/ML Ops1 lesson
What it takes to keep an AI model answering millions of people without getting slower or dumber - serving engines, GPUs on Kubernetes, training at scale, retrieval plumbing, and the evals that catch drift before a user does.
Part three · Depth
10The Paved Road1 lesson
How Netflix, Spotify and Airbnb built the internal platform that runs their product - one opinionated, pre-wired path so most teams never touch raw infrastructure.
Borrowed from other tracks (16)
You don't need to take those tracks. These are the only lessons this track uses from them, and each is linked where it is needed.
- Processes, Threads & the KernelHow Computers Work · needed for Running a Container for Real
- The whisper code (how a call goes private)Networking · needed for Getting Traffic In (Services & Ingress)
- Who holds the pen (consensus & Raft)System Design · needed for Under the Hood (Kubernetes Internals)
- Inference at Scale (why an LLM is fast, and cheap)AI · needed for AI/ML Ops - the deep-dive set
- Evaluating Models (how do you *know* it's good?)AI · needed for AI/ML Ops - the deep-dive set
- AuthenticationSecurity · needed for The Badge Machine - IRSA end to end
- Cryptography FoundationsSecurity · needed for OIDC - the Passport & the Stamp-Book
- One address, a thousand doorsNetworking · needed for VPC & Subnets
- TCP vs UDP, and the 3-way handshakeNetworking · needed for Security Groups vs Network ACLs
- DNS ResolutionNetworking · needed for Load Balancing & DNS (the operator's half)
- DNS on the wireNetworking · needed for Load Balancing & DNS (the operator's half)
- The chai stall that got famous (load balancing)System Design · needed for Load Balancing & DNS (the operator's half)
- S2 · Build a Load BalancerPortfolio Projects · needed for Load Balancing & DNS (the operator's half)
- How the web outgrew the phone callNetworking · needed for Services & Ingress, from the inside
- WAL & RecoveryDatabase Internals · needed for The Restore Nobody Tested
- Application HardeningSecurity · needed for The part someone else made