System Design Foundations: From Idea to Execution Trace

Lesson promise

By the end of this lesson, the learner should be able to explain: what distinguishes a system from a single program, why latency is measured in distributions not averages, and how a single user request crosses multiple layers before reaching application code.

Narration draft

Start with the question: "What is a software system?" Contrast a single program with a system of components — each with its own boundary, responsibility, and failure mode. Then introduce the three metrics every system designer must carry: latency (cost of one operation), throughput (how often you can do it), and the coordination cost (what it takes to make multiple components agree).

Walk through the request flow: the browser resolves DNS, establishes a TCP connection, negotiates TLS, and sends an HTTP request. At each stage, name the layer (client, network, crypto, server) and the cost the user pays. Show how a cache hit avoids a database round-trip, and how a cache miss pays that cost plus the write-back.

The key insight: most system design decisions are visible in this trace. The choice of load balancer, the placement of caches, the number of regions — each adds or removes a hop on the critical path. A system designer reads the trace and asks, "where is the slowest hop, and can we remove it?"

Visual sequence

1. Draw a request path from a browser through DNS, TCP, TLS, HTTP, to a server. Label each hop with its estimated cost.
2. Zoom into the server: show the cache, the database, and the choice point between hit and miss.
3. Compare the latency of a cache hit (sub-millisecond) vs. a cache miss (1-10 ms) vs. no cache at all.
4. End with the estimation exercise: how long does a cross-country request take?

Companion material

Use the what-is-a-software-system article, latency and throughput article, browser request flow diagram, cache hit and miss trace, estimate latency practice, and the System Design Foundations learning path as written references. The video remains planned until media and transcript are produced.