HTTP/2 vs HTTP/3: Multiplexing, QUIC, and Real-World Performance
HTTP/2 vs HTTP/3 compares streams, head-of-line blocking, and QUIC so you can pick a protocol that stays fast when packets drop on real networks today.
Category
Networking in system design is how requests travel from a user’s device to your servers and between your services. It covers DNS resolution, TCP and TLS connections, HTTP versions, load balancers, CDNs and protocols such as REST, gRPC and WebSockets. Each hop adds latency and a failure point, so knowing these layers helps you place caches, set timeouts and rate limits, and pick the right protocol for each call.
12 articles
HTTP/2 vs HTTP/3 compares streams, head-of-line blocking, and QUIC so you can pick a protocol that stays fast when packets drop on real networks today.
gRPC vs REST compares protocol buffers, streaming, and JSON APIs so you can pick a contract that stays…
L4 vs L7 load balancing compared: the layer 4 load balancer's connection-level speed, the layer 7 load balancer's…
Long polling vs SSE compared: how server sent events work, where websockets fit, sse vs polling costs, and…
What are websockets: the websocket vs http comparison, the websocket connection lifecycle in six steps, and scaling websocket…
The rate limiting algorithms that matter (token bucket, leaky bucket, sliding window) how distributed enforcement works across a…
DNS for Backend Engineers shows how name lookups, caches, and TTL choices fail in production, and how you…
What an API gateway does (routing, authentication, rate limits, transformation) how it differs from a reverse proxy and…
How a CDN serves content from edge servers near users; cache hits, origin fetches, TTLs, cache hit ratio,…
What a reverse proxy is, what it does (TLS termination, routing, security) how it differs from a forward…
What a load balancer does, how L4 and L7 balancing differ, which algorithm to pick (round robin, least…
TCP vs UDP explains when you want reliable streams, when datagrams win, and how loss, latency, and head-of-line…