- Learn
- High Level System Design
- Computer and Network Foundations
HLD-M01
Computer and Network Foundations
The physical facts every design rests on: how slow disks and networks really are, how servers juggle many requests, and how bytes travel from one machine to another.
Every architecture diagram is drawn on top of a few physical facts. Memory is fast and disks are slow. A packet between continents takes about as long as a blink. A server can only do so much at once, and the way it waits for I/O decides how many users it can hold. The protocols that move bytes, IP, TCP, UDP, DNS, HTTP and TLS, each add their own costs and guarantees.
This module turns those facts into intuition. You will learn the latency numbers well enough to estimate without a calculator, see why event loops can hold thousands of idle connections, watch a lost packet stall a TCP stream, follow a DNS lookup through its four servers, load a page under three versions of HTTP, and see what TLS is protecting. Later modules assume all of it.
Lessons
- HLD-01.01 Latency numbers every engineer should know Reading from CPU cache takes about a nanosecond, main memory about 100 nanoseconds, an SSD about 100 microseconds, a round trip inside a data center about half a millisecond and a round trip across continents around 150 milliseconds. Beginner 10 min
- HLD-01.02 Processes, threads and concurrency A process is a running program with its own memory; threads are lighter units of execution that share a process's memory. Beginner 12 min
- HLD-01.03 Networking basics: IP, TCP, UDP and ports IP moves packets between machines using addresses, with no promise of delivery or order. Beginner 14 min
- HLD-01.04 DNS in depth DNS translates names like example.com into IP addresses through a chain: your resolver asks a root server, then the top-level domain server, then the domain's authoritative server, caching answers along the way for their TTL. Beginner 12 min
- HLD-01.05 HTTP/1.1, HTTP/2 and HTTP/3 HTTP is a request and response protocol: a method such as GET or POST, a path, headers and an optional body, answered with a status code, headers and a body. Beginner 14 min
- HLD-01.06 TLS and HTTPS TLS encrypts traffic and proves the server's identity using a certificate signed by a trusted certificate authority. Beginner 10 min