What is System Design?

A system design interview asks you to architect a large-scale distributed system from scratch like a URL shortener, a social feed, a ride-sharing backend. Unlike coding rounds, there's no single correct answer. The goal is to demonstrate structured thinking, awareness of trade-offs, and experience with real-world constraints.

1. Why System Design Matters

Most software runs at trivial scale. A single database on a single server handles millions of small apps just fine. But once a system needs to handle millions of requests per second, store petabytes of data, or guarantee five-nines uptime, every design decision compounds.

System design teaches you to ask the right questions before writing code:

• How many users? How much data? What are the read/write ratios?
• What consistency guarantees does the product actually need?
• Where are the bottlenecks, and which ones matter?

2. The Building Blocks

Every large system is assembled from a small set of primitives:

Understanding each primitive — when to use it, what it costs, where it breaks that is the foundation of every system design answer.

3. The Interview Framework

A reliable framework prevents you from going blank under pressure:

1. Clarify requirements — functional vs non-functional, scale estimates
2. Capacity estimation — QPS, storage, bandwidth back-of-the-envelope math
3. API design — define the contract before the internals
4. High-level design — draw the boxes: clients, servers, databases, caches
5. Deep dive — pick the hardest component and go deep
6. Trade-offs — explain what you'd change given more time or different constraints

4. Consistency vs Availability

The CAP theorem states that a distributed system can guarantee at most two of: Consistency, Availability, and Partition Tolerance. Since network partitions are unavoidable, real systems choose between CP and AP.

A CP system (like HBase) returns an error if it can't guarantee consistent data. An AP system (like Cassandra) returns potentially stale data but stays available.

Most consumer products choose eventual consistency like your Twitter feed being a few seconds stale is acceptable but your bank balance being stale is not.

5. Where to Go Next

The chapters ahead walk through each building block in depth — from how consistent hashing distributes keys across a cache cluster to how Kafka achieves millions of writes per second. Each chapter ends with a worked system design example that uses the concepts just covered.

Start with Networking Fundamentals if you're newer to distributed systems, or jump directly to Caching or Databases if you want to fill a specific gap.

Summary

System design is the discipline of making deliberate architectural choices under real-world constraints. The skills compound: each building block you understand becomes a tool you can reach for when architecting a new system or debugging a production incident.