
Already know some of this? A 2-minute test skips the lessons you know.
Take the placement testA free 20-lesson course built from Mohit Chhabra's 3h 45m of YouTube video. 3 days at 90 minutes a day, with study notes and a quiz in every lesson. A 2-minute placement test skips what you already know.
Taught by Mohit Chhabra on YouTube. Videos play in YouTube's own player, so the creator keeps every view.
Understand the roles of client, server, and database in an API interaction, and distinguish between API requests (client to server) and responses (server to client) using JSON over HTTP.
Explain how DNS translates human-readable domain names into IP addresses, and describe the hierarchical recursive resolution process from root to authoritative servers.
Identify the four-step DNS lookup chain (browser cache, OS cache, local hosts file, recursive resolver) and explain how TTL-based caching reduces latency.
Distinguish between public resolvers, authoritative DNS, and global root servers; explain the funding model where end users pay nothing but domain owners pay for authoritative and global DNS features.
Describe the TCP three-way handshake (SYN, SYN-ACK, ACK) that establishes a reliable, ordered, error-checked connection before any application data is sent.
Compare HTTP/1.1 (sequential reuse), HTTP/2 (parallel multiplexing), and HTTP/3 over QUIC/UDP (0-RTT handshake) for connection management and performance.
Explain the TLS 1.2 handshake (ClientHello, ServerHello+Certificate, KeyExchange, Finished) and how TLS 1.3 reduces it to one round-trip for faster secure connections.
Break down the structure of an HTTP request/response (method, URL, headers, body), show how TLS encrypts the serialized bytes into TCP packets, and identify key headers like Authorization and Content-Type.
Trace how IP packets travel from a local router through ISPs via BGP peering and internal OSPF shortest-path routing to reach the destination data center.
Contrast IPv4 (32-bit, dotted decimal, NAT-heavy) with IPv6 (128-bit, hex, vast address space eliminating NAT) and explain why IPv6 adoption is growing.
Differentiate L3 gateway (public-to-private IP translation, NAT) from L7 API gateway (JWT authentication, rate limiting, path-based routing, protocol translation) and list common implementations (NGINX, AWS API Gateway).
Contrast L4 load balancer (IP/port-based) with L7 load balancer (URL/header-based, consistent hashing) and explain how both perform health checks and failover to keep backend servers healthy.
Clarify that gateway handles security, routing, and protocol translation while load balancer solely distributes load across scaled servers; they are distinct network appliances (hardware or cloud services).
Assemble the complete request path from client through DNS resolution, TCP/TLS handshakes, and the security/scaling layers (firewall, L3 gateway, L4 LB, L7 gateway, L7 LB) to the target microservice and database.
Explain how responses follow the exact reverse hop-by-hop path using internal connection mappings (socket IDs) so the client receives data from the same gateway it called, preserving security and abstraction.
Contrast request-response REST with WebSocket duplex connections that let servers push real-time updates (e.g., chat) without client polling, and note gateway protocol translation between external WebSocket and internal REST.
Illustrate how each network hop (client→gateway→microservice) creates a new TCP connection with a unique internal socket ID, maps it to the previous hop's ID, and uses that map to route the response back.
Summarize the canonical architecture diagram for system design interviews: start with client, place L7 gateway for auth/rate-limit/routing, add L7 load balancer for scaling, show microservices with private IPs, and connect to databases.