Many developers can build features, ship APIs, and write solid code — but feel completely lost when the conversation shifts to infrastructure.
Terms like TLS termination, private endpoints, and edge providers start flying around… and suddenly nothing makes sense.
This video fixes that.
Instead of memorising tools or cloud services, you’ll learn a single mental model that makes system architecture intuitive:
Follow the request.
By tracing how a request actually moves through a system — from DNS to the edge, through routing, into your application, and beyond — you’ll finally understand what all those “boxes” are doing and why they exist.
In this video, you’ll learn:
- The one mental model that makes infrastructure click
- How requests actually flow through modern systems
- What “trust boundaries” are and why they matter
- Why infrastructure discussions feel confusing (and how to fix that)
- How to think like an engineer who understands systems, not just code
If you want to move beyond just writing code and start understanding how real production systems work — this is the missing piece.
Key concepts covered:
DNS, Edge Providers, TLS Termination, WAF, Load Balancers, Reverse Proxies, API Gateways, Trust Boundaries, Request Flow, System Design
