Networking
posts (23)
The OSI Model in the Cluster and the Cloud: Who Sees What When You Open a Page
L3, L4 and L7 are shorthand for how deeply a piece of infrastructure looks into traffic. One request, from clicking "Pay" to the payments pod, layer by layer.
- The Layers of HTTP in the Browser: From fetch() to QUIC9/9
From fetch() to the First Byte
The whole lifecycle in one place: browser policies, cache, connection, wire format, headers and body. Only with that model does the Network panel answer…
- The Layers of HTTP in the Browser: From fetch() to QUIC8/9
HTTP/3 and QUIC: Same HTTP, Different Transport
QUIC removes transport-level head-of-line blocking and sets up a session more cheaply, but it does not fix the dependencies the frontend creates in its own…
- Kubernetes from the Inside: Cluster Architecture Basics5/7
DNS and CoreDNS in Kubernetes
A Pod's IP address is a poor interface for applications, because it changes. CoreDNS turns a stable name into a Service IP, and only then the datapath delivers…
- Kubernetes from the Inside: Cluster Architecture Basics4/7
Networking in Kubernetes
CNI gives Pods their addresses and connectivity, while kube-proxy or an eBPF datapath makes traffic sent to a Service's virtual address reach the right…
- The Layers of HTTP in the Browser: From fetch() to QUIC7/9
HTTP/2: Multiplexing Changed the Frontend Network Model
The same HTTP semantics, a different wire format. Many parallel requests do not mean many sockets, and stream independence ends at TCP.
- series · 7 parts
Kubernetes from the Inside: Cluster Architecture Basics
A series about what actually makes a Kubernetes cluster work - from kube-apiserver and etcd, through kubelet and CNI, to the managed vs self-managed choice and…
- The Layers of HTTP in the Browser: From fetch() to QUIC6/9
HTTP/1.1: Where Waterfalls and Bundling Came From
Bundling, sprite sheets and domain sharding were answers to the cost of many requests. Frontend architecture adapted itself to the limits of the protocol.
- The Layers of HTTP in the Browser: From fetch() to QUIC5/9
Connections: Why One fetch() Does Not Mean One Connection
A request and a connection have different lifecycles. The connection pool belongs to the browser, and the frontend influences it only through the architecture…
- series · 9 parts
The Layers of HTTP in the Browser: From fetch() to QUIC
Two lines of fetch() cover several layers: the browser API, HTTP semantics, the wire protocol and the transport. This series separates them so the Network…