KnowSys

Every chapter

75 chapters in 8 parts, and 8 labs. Parts build on each other from the processor upward, but every chapter says what it assumes, so you can start wherever your problem is.

The Machine

7/7

The Operating System

10/10

Concurrency

5/5

Data & Storage Engines

10/10

Distributed Systems

7/7

Cloud Infrastructure

8/8

Designing & Running Systems

6/6

System Design Case Studies

22/22
49
Designing WhatsApp
A billion phones online at once, messages that arrive exactly where they should, and a server that can't read them.
50
Designing Uber
Millions of moving cars, one request, a match in two seconds: hexagons, road graphs and the assignment problem.
51
Designing YouTube
Upload once, play anywhere without a stall: resumable uploads, a transcoding DAG, caches inside ISPs, DASH manifests and buffer-based bitrate.
52
Designing Stripe
A tunnel eats the reply and she taps Pay again. Idempotency keys, double-entry ledgers and signed webhooks make sure she pays once.
53
Designing Zoom
Five people on four continents inside a fifth of a second: RTP, NAT traversal, SFUs, video layers, jitter buffers and congestion control.
54
Designing ChatGPT
Words streaming within a second: prefill and decode, continuous batching, PagedAttention, prefix caching and speculative decoding.
55
Designing Google Maps
Draw any part of the world instantly and route across a continent with live traffic: tile pyramids, contraction hierarchies and ETAs.
56
Designing a Distributed Job Scheduler
Forty thousand customers to charge at midnight, once, whatever breaks: timing wheels, leases, idempotent jobs and the midnight herd.
57
Designing Valorant
Two players fire within milliseconds. How a 128-tick authoritative server decides who hit whom first, when every screen shows an old world.
58
Designing Netflix Recommendations
Forty rows, the titles in each, a picture on every one, chosen in a second: embeddings, nearest-neighbour graphs, bandits and experiments.
64
Designing Figma
Two designers edit one file at once, one in a train tunnel: OT vs CRDTs, per-property last-writer-wins and fractional indexing.
65
Designing Twitter's Home Timeline
One post to 300 followers, another to 100 million: fan-out on write vs read, Redis timelines, Snowflake IDs, Earlybird and ranking.
66
Designing Dropbox
Save a 2 GB project, see it everywhere, never lose an offline edit: 4 MB blocks, rolling hashes, three trees, Magic Pocket.
67
Designing Ticketmaster
Millions of fans, 70,000 seats, 10:00 sharp: seat holds that expire, signed queue tokens, random pre-queues and cached seat maps.
68
Designing Discord
One message, a million people online in one server: Snowflake-bucketed partitions, ScyllaDB, request coalescing and Elixir relays.
69
Designing JioHotstar: Live Cricket at Scale
Dhoni walks out and millions tap Play at once. Live segments, request collapsing, multi-CDN steering and scaling before the crowd.
70
Designing UPI
₹20 for chai moves between two banks that share nothing, in two seconds. Switches, VPAs, debit-then-credit, deemed payments and reconciliation.
71
Designing Zerodha and the Stock Exchange
Meera taps Buy at 9:15. Follow her order through risk checks and leased lines into NSE's order book, and the price back out.
72
Designing Amazon's Cart and Checkout
Prime Day at midnight: a cart that never refuses a write, vector clocks, 1,000 deal units for a million taps, one order each.
73
Designing Cloudflare
A shop under a multi-terabit flood, a shopper who never notices: anycast, dosd fingerprints in XDP, Unimog, Pingora, isolates, Quicksilver.
74
Designing LeetCode
Two minutes left, a stranger's C++ hits the judge. Sandboxes from isolate to Firecracker, fair timing, checkers, rankings, winnowing.
75
Designing Notion
Everything is a block. A tree with parent-pointer permissions, Postgres sharded into 480 shards then tripled to 96 hosts, and SQLite in the browser.

The Labs

8/8