Skip to main content

Courses About Pricing Educators

Sign in Get started

Courses About Pricing Educators

Get started Sign in

Loading courses

Loading lessons

The Request's Journey: System Design: Uncharted

Courses System DesignThe Request's Journey

The Request's Journey

Follow a tap through DNS, HTTP, application logic, and durable data, then draw the path yourself.

System Design
Unit 1 of 12
20 lessons
151 min
420 XP

Every lesson is open. Sign in when you are ready to begin.

Sign in to start

Lessons

20 total

1What Happens When You TapTrace a tap from the client request through a service response to the pixels rendered on screen.InteractiveConcept7 min20 XPOpen
2Clients Ask, Servers AnswerIdentify client and server roles by who initiates and who answers an exchange, regardless of device type.InteractiveConcept7 min20 XPOpen
3The Internet's Address BookExplain how DNS supplies a routable address and when a cached result can skip a fresh lookup.InteractiveConcept7 min20 XPOpen
4Speaking HTTPRelate GET, POST, PUT, and DELETE to the resource operation each method conventionally requests.InteractiveConcept7 min20 XPOpen
5Order the JourneySequence DNS resolution, connection setup, HTTP exchange, and rendering by their causal dependencies.InteractiveConcept7 min20 XPOpen
6Status Codes Tell StoriesInterpret common HTTP status codes as success, redirection, client error, or temporary and internal server failure.InteractiveConcept7 min20 XPOpen
7Your First BlueprintModel the smallest request path in which a user reaches application logic that consults durable data.DiagramConcept10 min20 XPOpen
8The Backend, Cut AwayDistinguish web serving, application rules, and durable storage as separate backend responsibilities.InteractiveConcept7 min20 XPOpen
9Where the Time GoesCompare orders of magnitude for memory, disk, and network latency to spot the wait that dominates a request.InteractiveConcept7 min20 XPOpen
10Napkin Math DebutTurn daily users and requests per user into an average request rate and its nearest order of magnitude.InteractiveConcept7 min20 XPOpen
11The Forgetful ServerExplain why shared session state lets login survive process restarts and routing to another instance.InteractiveConcept7 min20 XPOpen
12The One-Box BakeryRepresent a bakery order crossing the application boundary before becoming durable in the orders database.DiagramConcept10 min20 XPOpen
13The Database Is Not the ServerSeparate business-rule changes in the service from record persistence in the database.InteractiveConcept7 min20 XPOpen
14APIs Are MenusRecognize a stable API as a documented contract over resource paths, requests, and response shapes.InteractiveConcept7 min20 XPOpen
15Payloads and ScreensSelect a response shape that gives a screen the fields it needs without exposing or shipping whole records.InteractiveConcept7 min20 XPOpen
16When the Box Fills UpDiagnose rising queues, latency, and timeouts as signs that a single server is nearing capacity.InteractiveConcept7 min20 XPOpen
17Read the Latency ChartFind the endpoint whose median latency is an actionable outlier among comparable requests.InteractiveConcept8 min20 XPOpen
18Blueprint VocabularyRead architecture symbols by the responsibility each node performs rather than by a vendor name.InteractiveConcept7 min20 XPOpen
19Explain the JourneyGive a causal account of how name lookup, application logic, durable data, and rendering turn a tap into a result.InteractiveConcept8 min20 XPOpen
20The Journey Mastery CheckConstruct an end-to-end request path that keeps web serving, application logic, and durable storage distinct.DiagramMastery check10 min40 XPOpen