autochitect

Sockets: The Plumbing Behind Every Network Call

2026-05-12NetworkingSystem DesignPerformanceOS Internals

What a socket actually is, how the OS manages the full lifecycle of a connection, why unmanaged sockets drain CPU at scale, and how DNS prefetch and stale cache interact with socket behaviour.

Loading…

Engineering Notes

Sockets are the lowest-level abstraction most application developers touch. Every HTTP request, database query, and gRPC call is a sequence of socket syscalls. Understanding the socket lifecycle — including TIME_WAIT, file-descriptor limits, and the cost of blocking I/O — is the difference between an application that scales and one that silently degrades under load.

Prerequisites

◆IP addresses and ports — what they identify

◆TCP vs UDP — connection-oriented vs datagram

◆Unix file descriptors — how a process accesses OS resources

◆OSI or TCP/IP layer model — where L3 and L4 sit

Why Architects Need This

◆Connection pool sizing — how many sockets to keep open per service

◆L4 vs L7 load balancer selection — what each layer can see and do

◆Blocking I/O vs epoll/event-loop vs thread-per-connection trade-offs

◆DNS TTL tuning — how stale cache interacts with socket connect() failures

◆TIME_WAIT budget — why short-lived services exhaust ephemeral ports at scale

◆SO_REUSEPORT and kernel socket sharding for multi-core throughput

Related Concepts

◆TCP/IP 4-Layer Model

◆OSI Model

◆epoll / kqueue (Event Loop)

◆Connection Pooling

◆DNS Resolution

◆TLS Handshake

◆Load Balancing

◆Backpressure