Skip to content
learn
  1. Learn
  2. High Level System Design
  3. Orientation

HLD-M00

Orientation

Start here: what system design is, what really happens when you load a web page, and how this track is organized.

3 lessonsabout 30 min

System design is the part of software engineering that happens before and around the code: deciding which pieces a product needs, what each piece is responsible for, and how requests and data move between them. It is what separates an app that works for ten friends from one that keeps working for ten million strangers.

This short module sets the stage. You will grow a toy app from one server to a global system and see why each new piece appears, follow a single page load hop by hop from your keyboard to a database and back, and get a map of the whole track so you know where every later lesson fits.

Lessons

  1. HLD-00.01 What is system design? A system is everything between a user's tap and the data that answers it: clients, servers, databases, caches, queues and the network joining them. Beginner 8 min
  2. HLD-00.02 What happens when you type a URL and press Enter When you press Enter, the browser checks its caches, then asks DNS to turn the hostname into an IP address. Beginner 15 min
  3. HLD-00.03 How to use this track The track runs from foundations (networks, latency, estimates) through building blocks (APIs, load balancers, caches, databases, queues) to distributed systems theory, reliability and full design case studies. Beginner 5 min

Start with lesson 1