Video lesson: Start System Design With a Workload Model

Lesson promise

By the end, the learner should be able to explain the core model for start system design with a workload model, apply it to a concrete input, and identify when its usual shortcut or guarantee stops applying. This is a recording brief; publish it as a playable lesson after the narration and visual sequence have been produced and reviewed.

Narration draft

A workload model describes request rates, payload sizes, read/write mix, burstiness, and latency goals. Capacity estimates are useful when they expose assumptions and identify dominant resource costs; a single total-user count rarely predicts the load a system must handle.

If one million users each make two requests per day, the average is far below the peak if activity clusters around a short window. Estimate average and peak requests per second, then multiply by bytes, storage retention, and downstream calls. State whether retries and background jobs are included.

Back-of-the-envelope numbers are ranges, not promises. Cache hit rate, hot keys, payload distribution, and fan-out can change capacity sharply. Averages hide tail latency and bursts, so design headroom and measure the real workload before purchasing or sharding capacity.

Visual sequence

1. Put the input and assumptions on screen. Ask the learner to predict the next state before revealing it.
2. Animate the representation and show the operation one transition at a time.
3. Pause at the boundary case in the companion article and compare the result with the invariant.
4. End with the exercise prompt: Estimate storage for event records given an arrival rate, average encoded size, and retention period. Then name two additional factors needed before sizing the database.

Companion material

Use the article, trace, and interactive concept flow as the learner’s written and visual references. The video remains planned until an actual playable media URL and reviewed transcript are available.