“Computer Networks” is valuable because it turns networking into one coherent engineering picture, from loss and routing to transmission reliability and wireless constraints.
In practice, it helps you read a request path without magic: where latency comes from, why throughput drops, and whether degradation originates in protocol behavior, topology, or the channel itself.
In interviews and design discussions, it makes conversations about network reliability and system performance rest on mechanisms rather than intuition.
Practical value of this chapter
Network intuition
Builds practical understanding of latency, loss, and throughput across request paths.
Protocol layering
Enables layer-by-layer incident analysis to locate true degradation sources faster.
Design implications
Turns network theory into concrete retry, timeout, pooling, and backpressure decisions.
Interview confidence
Strengthens responses on network reliability and performance in distributed systems.
Official page
Computer Networks
Book page on Pearson.
Computer Networks
Authors: Andrew S. Tanenbaum, David J. Wetherall
Publisher: Pearson, 2021 (6th Edition)
Length: ~960 pages
Network stack layers, routing, transmission reliability, TLS, and wireless constraints through a classic networking textbook.
This book is valuable because it turns networking into one coherent engineering picture: from encapsulation and routing to latency budgets, throughput, and packet loss. It helps you read a request path as a system rather than as a pile of isolated protocols.
For systems design, that matters because RTT, congestion control, flow control, retries, timeouts, and backpressure sit next to DNS, BGP, and TLS in one mental model. That makes it much easier to reason about reliability, performance, and operational trade-offs in real distributed systems.
Key topics
Models and protocols
OSI/TCP/IP, encapsulation, addressing, and the role of each layer in a request path.
Routing
BGP and OSPF at the conceptual level, including path metrics and route stability.
Transmission reliability
Loss, retransmissions, windows, congestion control, and QoS.
Network applications
HTTP/HTTPS, DNS, email, RPC, and recurring network application patterns.
Security
TLS, certificates, authentication, core threat models, and basic protections.
Wireless networks
Wi-Fi, LTE/5G, and the way transmission media affects stability and latency.
Related chapter
OSI model
A seven-layer map that helps you trace a request through the network stack.
Network stack and request path
The book treats a request as movement through layers. That framing helps you see much faster where delay, loss, or misconfiguration really enters the path.
Application
HTTP, DNS, gRPC, WebSocket, data formats, and interaction semantics.
Transport
TCP/UDP/QUIC, congestion control, reliable delivery, and ordering.
Network
IP, addressing, routing, NAT, MTU, and fragmentation.
Link / Physical
Ethernet, Wi-Fi, mobile networks, signal quality, and loss.
Latency budget
Metrics worth keeping in mind
How the book is organized
Part 1
Physical and link layers
Signals, coding, error detection, and the foundations of local networking.
Part 2
Network and transport layers
IP, routing, TCP/UDP/QUIC, congestion control, and reliable delivery.
Part 3
Application protocols
DNS, HTTP, email, and the architecture of network-facing applications.
Part 4
Security and wireless networks
TLS, threat models, cryptography, and the constraints of Wi-Fi and mobile networking.
What is genuinely useful in systems design
- Estimating RTT and seeing where the network begins to consume the latency budget.
- How TCP, UDP, and QUIC shape service behavior and architectural choices.
- How routing and geography influence availability and global traffic behavior.
- Where the transport layer ends, where the application begins, and when TLS belongs in the design.
Why this matters for systems design
- Understanding delay and protocol behavior makes performance estimates less hand-wavy.
- Knowledge of routing is crucial for architectures that serve users across regions.
- Network failure modes are central to the reliability of distributed systems.
- Protocols shape retries, timeouts, load balancing, and graceful degradation choices.
Who the book is for
Backend engineers, SREs, and anyone designing network services, protocols, or systems with meaningful traffic and availability demands.
Related chapters
- Computer networks: principles, technologies, protocols (short summary) - A side-by-side view of two classic networking books with different strengths and teaching styles.
- OSI model - A practical map of layers and responsibility boundaries inside the network stack.
- TCP protocol - Reliable delivery, window management, and the cost of congestion control in real systems.
- UDP protocol - A low-overhead transport choice for paths where latency matters more than strict reliability.
- Domain Name System (DNS) - Name resolution, caching, and the way DNS shapes request paths and failover behavior.
- HTTP protocol - HTTP evolution and the way application protocols reshape caching, retries, and service design.