Phase 1 · Fundamentals
Requirements, estimation and the vocabulary of scale.
- Scaling One App from 1 User to 1 Million (and Beyond): One Indian D2C store on NestJS + Postgres, taken stage by stage from a single VM to multi-region. Each stage gives the metric that forces the change, the change itself, what it costs or breaks, and a diagram.
- Scalability, Availability, Reliability, Latency & Throughput: The vocabulary of scale: how systems grow, how they fail, how to do availability math, and why p99 (not the average) decides your architecture.
- Capacity, Storage, Bandwidth & Peak Estimation: Guesstimates — quick, rounded maths that drives real design decisions: DAU → QPS → peak, storage over 5 years with replication, ingress/egress, cache memory, and server counts.
- Requirements & The Interview Framework: Turn a one-line prompt into scoped functional requirements, measurable SLO-style NFRs, an API contract and a 45-minute plan you actually control.
- OS & Kernel for Backend Engineers: Processes, Memory, I/O & the Durability Path: What the kernel is really doing under your NestJS service, Postgres and Redis: fork and copy-on-write, scheduling and CFS throttling, page faults and the OOM killer, file descriptors, epoll/io_uring, libuv, socket buffers, acceptor patterns with SO_REUSEPORT, and the full write() → fsync → device-cache → media path.