Learning Path
Every module, lab, and PDF is tagged to these six mental models. Work through each principle to make cloud-native intuition second nature.
Design blast radius before success path.
Train yourself to see every architecture as a graph of failure domains. Every stateful hop is a consistency boundary; every shared network is a collision domain.
Modules
Concepts from PDFs
- LAN vs WAN vs WLAN: broadcast domains and failure containment.
- NIC, MAC, IP: identify which failure domain breaks when one layer fails.
- Ethernet frames, IP packets, TCP segments: know which layer owns retry vs reroute.
- Routers and switches: CAM tables, routing tables, and what happens when they diverge.
- DHCP/APIPA/NAT/PAT: automatic recovery paths and single points of failure.
Backing Sources
Module Evidence
Trade-offs over defaults.
Bad architects pick the shiny tool. Great architects write the 1-page decision doc: context, options, trade-offs, chosen path, rollback plan.
Modules
Concepts from PDFs
- IaaS vs PaaS vs SaaS: who owns the failure surface?
- Hypervisor isolation: Type 1 vs Type 2 for security and performance.
- Multitasking vs multiprocessing: when to partition workload vs time-share.
- VLAN and subnetting: design trade-offs between broadcast containment and routing complexity.
Backing Sources
Module Evidence
Measure before you guess.
No optimization without instrumentation. No scaling without load data. Define SLOs first; error budgets force priorities better than any roadmap.
Modules
Concepts from PDFs
- Metrics, logs, traces: the three pillars of production debugging.
- SLOs and error budgets: quantitative guardrails for change velocity.
- Health probes and readiness gates: observability as deployment control.
- DHCP lease times, NAT table exhaustion: invisible state that breaks availability.
Backing Sources
Module Evidence
Zero trust, least privilege.
Every boundary is a security boundary. mTLS everywhere, short-lived credentials, encryption in transit and at rest, audit everything.
Modules
Concepts from PDFs
- BIOS/UEFI Secure Boot: firmware as trust anchor.
- Partition isolation: recovery partitions, encrypted volumes, attack surface reduction.
- IP classes, NAT, PAT: obscurity vs isolation; why private IPs alone are not security.
- Stateful inspection: firewall rules are policy codified as code.
Backing Sources
Module Evidence
If you can’t redeploy from scratch in one command, it’s broken.
If a task is manual, it’s already broken. Infrastructure as code, pipelines as code, secrets in vaults, immutable artifacts.
Modules
Concepts from PDFs
- Virtualization: Type 1 hypervisors as the foundation of cloud elasticity.
- Boot process: immutable server patterns vs traditional patch management.
- Container networking: overlay networks, service discovery, and failure isolation.
- Rollback undo: the repeatable path must have a tested reverse path.
Backing Sources
Module Evidence
Every byte and compute-hour has a price.
Does this architecture cost more than the business value it creates? Right-size before you scale; optimize data path before you optimize compute.
Modules
Concepts from PDFs
- Storage hierarchy: cache vs RAM vs SSD vs object store — cost and latency trade-offs.
- CPU core counts and GHz: right-sizing instances before scaling out.
- IaaS vs PaaS vs SaaS: operational cost vs control trade-offs.
- Data transfer costs: east-west vs north-south traffic; why topology affects bill.
Backing Sources
Module Evidence