API Protocols — HTTP/1.1 vs. HTTP/2 vs. HTTP/3 (QUIC) vs. gRPC

1. What It Is & Why It Exists

The Core Problem: Network Inefficiency & Head-of-Line Blocking

In modern distributed systems and web architectures, network transport efficiency directly dictates user perceived latency, server thread utilization, and bandwidth costs:

1. HTTP/1.1 Inefficiencies: Textual wire format with verbose, uncompressed headers. Concurrency requires opening multiple TCP connections (browsers open up to 6 per origin). Suffers from Application-Layer Head-of-Line (HOL) Blocking—a slow request blocks all subsequent requests on that TCP connection.
2. HTTP/2 Breakthroughs & Transport HOL: Introduced binary framing, stream multiplexing over a single TCP connection, and HPACK header compression. However, because it runs on single-stream TCP, a single lost packet blocks all multiplexed streams until TCP retransmits and reorders the packet (Transport-Layer HOL Blocking).
3. HTTP/3 & QUIC (UDP): Eliminates Transport HOL blocking by running over UDP. Each multiplexed stream is independent. Combines the transport handshake and TLS 1.3 cryptographic handshake into a single roundtrip ($1\text{-RTT}$ or $0\text{-RTT}$ connection resumption) and provides native Connection Migration across network switches (e.g., Wi-Fi to 5G cellular).
4. gRPC & Protocol Buffers: High-performance, strongly-typed Remote Procedure Call (RPC) framework built on HTTP/2 transport (some implementations also support HTTP/3) using Protobuf binary serialization, bi-directional streaming, and client/server code generation.

Synthesizing vector architecture diagram...

2. Core Mechanics & Wire Protocol Comparison

Synthesizing vector architecture diagram...

Start at the top: the same payload is split into three streams, then sent down two different transports. In the "HTTP/2 over TCP" panel, all three streams share one TCP connection; TCP must deliver bytes in order, so when packet 2 is lost, packets for streams 1 and 3 that arrive after it are held in the buffer until packet 2 is resent, and every stream stalls. In the "HTTP/3 over QUIC" panel, each stream has its own ordering on top of UDP, so streams 1 and 3 are delivered at once and only stream 2 waits for its retransmission. This is head-of-line blocking: HTTP/2 removed it at the HTTP level but still suffers it at the TCP level, which hurts most on lossy mobile networks.

Comprehensive Protocol Comparison Matrix