System Design

Learn System Design

How to Learn System Design?

Scalability

Availability

Latency and Performance

Concurrency and Coordination

Monitoring and Observability

Resilience and Error Handling

Fault Tolerance vs. High Availability

Flashcards Review

Chapter Assessment

Network Essentials

HTTP vs. HTTPS

TCP vs. UDP

HTTP: 1.0 vs. 1.1 vs 2.0 vs. 3.0

URL vs. URI vs. URN

What Happens When You Type a URL into the Browser

Flashcards Review

Chapter Assessment

Introduction to Real-Time Communication

What is Long-Polling?

What is WebSocket?

What are Server-Sent Events?

Difference Between Long-Polling, WebSockets, and Server-Sent Events

Flashcards Review

Chapter Assessment

Introduction to DNS

DNS Resolution Process

DNS Load Balancing and High Availability

Flashcards Review

Chapter Assessment

What is a Proxy Server?

Uses of Proxies

VPN vs. Proxy Server

Flashcards Review

Chapter Assessment

Introduction to Load Balancing

Load Balancing Algorithms

Uses of Load Balancing

Load Balancer Types

Stateless vs. Stateful Load Balancing

High Availability and Fault Tolerance

Scalability and Performance

Challenges of Load Balancers

Flashcards Review

Chapter Assessment

Introduction to API Gateway

Usage of API gateway

Advantages and disadvantages of using API gateway

Flashcards Review

Chapter Assessment

What Is an API?

What Are REST APIs?

Resources, Not Actions

HTTP Methods and Their Semantics

URL Design

Request and Response Shapes

Status Codes and Error Design

Pagination from the Consumer's View

Idempotency Keys

Versioning and Backward Compatibility

Concurrency and Conditional Requests

REST vs gRPC vs GraphQL

Flashcards Review

Chapter Assessment

What Is Rate Limiting

Rate Limiting Algorithms

Distributed Rate Limiting

Rate Limiting in Practice

Flashcards Review

Chapter Assessment

Introduction to Caching

Why is Caching Important?

Types of Caching

Cache Replacement Policies

Cache Invalidation

Cache Read Strategies

Cache Coherence and Consistency Models

Caching Challenges

Cache Performance Metrics

Flashcards Review

Chapter Assessment

What is CDN?

Origin Server vs. Edge Server

CDN Architecture

Push CDN vs. Pull CDN

Flashcards Review

Chapter Assessment

Introduction to Data Partitioning

Partitioning Methods

Data Sharding Techniques

Benefits of Data Partitioning

Common Problems Associated with Data Partitioning

Flashcards Review

Chapter Assessment

What is Redundancy?

What is Replication?

Replication Methods

Data Backup vs. Disaster Recovery

Flashcards Review

Chapter Assessment

Introduction to CAP Theorem

Components of CAP Theorem

Trade-offs in CAP Theorem

Examples of CAP Theorem in Practice

Beyond CAP Theorem

System Design Trade-offs in Interviews

Flashcards Review

Chapter Assessment

Introduction to Databases

SQL Databases

NoSQL Databases

SQL vs. NoSQL

ACID vs BASE Properties

Real-World Examples and Case Studies

SQL Normalization and Denormalization

In-Memory Database vs. On-Disk Database

Data Replication vs. Data Mirroring

Database Federation

Flashcards Review

Chapter Assessment

What are Indexes?

How a B-Tree Index Works

Types of Indexes

B-Tree vs. LSM Tree

Indexes in Distributed Systems

Flashcards Review

Chapter Assessment

Introduction to Bloom Filters

Benefits & Limitations of Bloom Filters

Variants and Extensions of Bloom Filters

Applications of Bloom Filters

Flashcards Review

Chapter Assessment

Why Quorum?

What is Quorum?

Flashcards Review

Chapter Assessment

What is Leader and Follower Pattern?

Flashcards Review

Chapter Assessment

What is Heartbeat?

Flashcards Review

Chapter Assessment

What is Checksum?

Uses of Checksum

Flashcards Review

Chapter Assessment

Introduction to Messaging System

Introduction to Kafka

Messaging patterns

Popular Messaging Queue Systems

RabbitMQ vs. Kafka vs. ActiveMQ

Scalability and Performance

Flashcards Review

Chapter Assessment

What is a Distributed File System?

Architecture of a Distributed File System

Key Components of a DFS

Flashcards Review

Chapter Assessment

What is Security and Privacy?

What is Authentication?

What is Authorization?

Authentication vs. Authorization

OAuth vs. JWT for Authentication

What is Encryption?

What are DDoS Attacks?

Flashcards Review

Chapter Assessment

Batch Processing vs. Stream Processing

XML vs. JSON

Synchronous vs. Asynchronous Communication

Push vs. Pull Notification Systems

Microservices vs. Serverless Architecture

Message Queues vs. Service Bus

Stateful vs. Stateless Architecture

Event-Driven vs. Polling Architecture

Flashcards Review

Chapter Assessment

Quiz

Importance of Discussing Trade-offs

Strong vs Eventual Consistency

Latency vs Throughput

ACID vs BASE Properties in Databases

Read-Through vs Write-Through Cache

Batch Processing vs Stream Processing

Load Balancer vs. API Gateway

API Gateway vs Direct Service Exposure

Proxy vs. Reverse Proxy

API Gateway vs. Reverse Proxy

SQL vs. NoSQL

Primary-Replica vs Peer-to-Peer Replication

Data Compression vs Data Deduplication

Server-Side Caching vs Client-Side Caching

REST vs RPC

Polling vs. Long-Polling vs. WebSockets vs. Webhooks

CDN Usage vs Direct Server Serving

Serverless Architecture vs Traditional Server-based

Stateful vs Stateless Architecture

Hybrid Cloud Storage vs All-Cloud Storage

Token Bucket vs Leaky Bucket

Read Heavy vs Write Heavy System

Quiz

System Design Interviews - A step by step guide

Functional vs. Non-functional Requirements

What are Back-of-the-Envelope Estimations?

Things to Avoid During System Design Interview

System Design Master Template

Quiz

Designing a URL Shortening Service like TinyURL

Quiz - Designing URL Shortner

Designing Pastebin

Quiz - Designing Pastebin

Designing Instagram

Quiz - Designing Instagram

Designing Dropbox

Quiz - Designing Dropbox

Designing Facebook Messenger

Quiz - Designing Facebook Messenger

Designing Twitter

Quiz - Designing Twitter

Designing Youtube or Netflix

Quiz - Designing Youtube

Designing Typeahead Suggestion

Quiz - Designing Typeahead Suggestion

Designing an API Rate Limiter

Quiz - Designing an API Rate Limiter

Designing Twitter Search

Quiz - Designing Twitter Search

Designing a Web Crawler

Quiz - Designing a Web Crawler

Designing Facebook’s Newsfeed

Quiz - Designing Facebook’s Newsfeed

Designing Yelp or Nearby Friends

Quiz - Designing Yelp or Nearby Friends

Designing Uber backend

Quiz - Designing Uber backend

Designing Ticketmaster

Quiz - Designing Ticketmaster

Dynamo: Introduction

High-Level Architecture

Data Partitioning

Replication

Vector Clocks and Conflicting Data

The Life of Dynamo’s put() & get() Operations

Anti-entropy Through Merkle Trees

Gossip Protocol

Dynamo Characteristics and Criticism

Summary: Dynamo

Quiz: Dynamo

Mock Interview: Dynamo

YouTube Likes Counter

Quiz

Cassandra: Introduction

High-level Architecture

Replication

Cassandra Consistency Levels

Gossiper

Anatomy of Cassandra's Write Operation

Anatomy of Cassandra's Read Operation

Compaction

Tombstones

Summary: Cassandra

Quiz: Cassandra

Mock Interview: Cassandra

Messaging Systems: Introduction

Kafka: Introduction

High-level Architecture

Kafka: Deep Dive

Consumer Groups

Kafka Workflow

Role of ZooKeeper

Controller Broker

Kafka Delivery Semantics

Kafka Characteristics

Summary: Kafka

Quiz: Kafka

Mock Interview: Kafka

Chubby: Introduction

High-level Architecture

Design Rationale

How Chubby Works

File, Directories, and Handles

Locks, Sequencers, and Lock-delays

Sessions and Events

Master Election and Chubby Events

Caching

Database

Scaling Chubby

Summary: Chubby

Quiz: Chubby

Mock Interview: Chubby

Hadoop Distributed File System: Introduction

High-level Architecture

Deep Dive

Anatomy of a Read Operation

Anatomy of a Write Operation

Data Integrity & Caching

Fault Tolerance

HDFS High Availability (HA)

HDFS Characteristics

Summary: HDFS

Quiz: HDFS

Mock Interview: HDFS

Google File System: Introduction

High-level Architecture

Single Master and Large Chunk Size

Metadata

Master Operations

Anatomy of a Read Operation

Anatomy of a Write Operation

Anatomy of an Append Operation

GFS Consistency Model and Snapshotting

Fault Tolerance, High Availability, and Data Integrity

Garbage Collection

Criticism on GFS

Summary: GFS

Quiz: GFS

Mock Interview: GFS

BigTable: Introduction

BigTable Data Model

System APIs

Partitioning and High-level Architecture

SSTable

GFS and Chubby

Bigtable Components

Working with Tablets

The Life of BigTable's Read & Write Operations

Fault Tolerance and Compaction

BigTable Refinements

BigTable Characteristics

Summary: BigTable

Quiz: BigTable

Mock Interview: BigTable

Design Reddit

Quiz

Designing a Notification System

Quiz

Design Google calendar (Medium)

Quiz

Design a Recommendation System for Netflix

Quiz

Design Gmail

Quiz

Design Google News, a Global News Aggregator System (Medium)

Quiz

Design Unique ID Generator (Easy)

Quiz

Design Code Judging System like LeetCode (Medium)

Quiz

Design Payment System

Quiz

Design a Flash Sale for an E-commerce Site (Hard)

Quiz

Design a Reminder Alert System

Quiz

Introduction: System Design Patterns

1. Bloom Filters

2. Consistent Hashing

3. Quorum

4. Leader and Follower

5. Write-ahead Log

6. Segmented Log

7. High-Water Mark

8. Lease

9. Heartbeat

10. Gossip Protocol

11. Phi Accrual Failure Detection

12. Split Brain

13. Fencing

14. Checksum

15. Vector Clocks

16. CAP Theorem

17. PACELC Theorem

18. Hinted Handoff

19. Read Repair

20. Merkle Trees

Quiz

HTTP: 1.0 vs. 1.1 vs 2.0 vs. 3.0

HTTP: 1.0 vs. 1.1 vs 2.0 vs. 3.0

http

tcp

udp

network protocols

+3

hard
·
5 min
·Updated Jul 2026·Credit: System Design Fundamentals

HTTP has been through four versions. Each one fixed a bottleneck the previous one created, so the story is easiest to follow as a chain of problems rather than a list of features.

HTTP/1.0

Every request opens a new TCP connection, and that connection closes once the response arrives.

The protocol is stateless, so no session information is kept between requests. Messages are text-based, with basic headers for content negotiation and caching.

For a page that is one document with almost nothing else on it, that is fine. For anything with images, stylesheets and scripts, it means paying for a fresh connection over and over.

The bottleneck: connection setup, repeated for every single resource.

HTTP/1.1

Persistent connections. The TCP connection stays open across multiple requests and responses. That removes the repeated setup cost, and it is why HTTP/1.1 loads a page of many resources with far less latency than HTTP/1.0.

Chunked transfer encoding. Data can be sent in chunks, so a server can start sending a response before it knows the total size.

Better caching. Improved headers allow more useful caching strategies.

The Host header. A request now says which host it is for, which lets many domains share a single IP address. That is what makes virtual hosting possible.

Image
HTTP/1.0 opens and closes a connection for every resource, while HTTP/1.1 keeps one connection open and sends the requests through it in turn

Pipelining, sending the next request before the previous response arrives, was allowed but rarely worked well in practice.

The bottleneck: the requests still go through the connection one at a time. A slow response blocks the ones behind it. That is head-of-line blocking.

HTTP/2.0

A binary protocol. Messages are encoded in a binary format rather than text, which is more efficient to parse and less error-prone.

Multiplexing. Many requests and responses can be in flight at the same time over a single connection, which is what ends head-of-line blocking at the HTTP layer. Nothing has to wait for the response in front of it.

Header compression (HPACK). HTTP headers repeat heavily from request to request. Compressing them cuts bandwidth.

Server push. The server can send a resource to the client proactively, before the client asks, anticipating what it will need next.

Image
Under HTTP/1.1 the responses queue behind each other on one connection, and under HTTP/2.0 they are interleaved so a slow one blocks nothing

The bottleneck: HTTP/2.0 still runs on TCP. TCP guarantees ordered delivery of its own stream, so one lost packet stalls every multiplexed stream sharing that connection. The blocking moved down a layer rather than disappearing.

HTTP/3.0

Built on QUIC. HTTP/3.0 replaces TCP with QUIC (Quick UDP Internet Connections), which runs over UDP. That is the change everything else follows from.

Faster connection setup. QUIC establishes connections more quickly, including a zero round trip time (0-RTT) handshake for a repeat connection.

Better handling of packet loss. Because QUIC is not bound by TCP's single ordered stream, a lost packet affects only the stream it belonged to. This is why HTTP/3.0 holds up better than HTTP/2.0 in real conditions with loss.

Encryption built in. QUIC integrates TLS 1.3, so transport encryption is part of the protocol rather than a layer added on top.

Header compression (QPACK). The same idea as HPACK, adapted for QUIC's independent streams.

Image
HTTP/2.0 multiplexes over TCP so one lost packet stalls every stream, while HTTP/3.0 multiplexes over QUIC on UDP so a loss affects only its own stream

The Whole Chain

HTTP/1.0HTTP/1.1HTTP/2.0HTTP/3.0
ConnectionNew per requestPersistentMultiplexed over oneQUIC over UDP
EncodingTextTextBinaryBinary
Header compressionNoLimitedHPACKQPACK
EncryptionOptionalOptionalUsually with TLSBuilt in, TLS 1.3
Under packet lossPoorPoorBetterBest
SuitsSimple static pagesDynamic sitesHigh-traffic interactive appsReal-time and streaming

Read it left to right and the pattern is one bottleneck at a time: connection setup, then request queueing, then transport-level blocking.

💡 The detail worth knowing for an interview is that HTTP/2.0 did not eliminate head-of-line blocking, it moved it. Saying "HTTP/2 fixed head-of-line blocking at the HTTP layer, but TCP's ordered stream reintroduced it, which is why HTTP/3 went to QUIC" is a complete explanation of why a third rewrite was needed.

Key takeaway: HTTP/1.0 opens a new TCP connection per request. HTTP/1.1 keeps the connection persistent, adds chunked transfer and the Host header that lets many domains share one IP, but requests still queue. HTTP/2.0 goes binary, multiplexes many streams over one connection, compresses headers with HPACK and can push resources. HTTP/3.0 moves to QUIC over UDP, which sets up faster, survives packet loss better, and builds in TLS 1.3.

The next lesson, URL vs. URI vs. URN, sorts out three terms that get used as if they meant the same thing.

Discussion
Have a question or insight about this topic? Share it with the community.
Reading Progress
0%

On This Page