HTTP/2 Multiplexing Under Load: Stream Prioritization, Head-of-Line Blocking, and the Connection Reuse Trap
HTTP/2 shipped with a promise: a single TCP connection, multiple concurrent streams, no more per-request connection overhead. For microservice clients making hundreds of short-lived RPC calls per second to a small set of upstream hosts, that promise looks compelling. In practice, the multiplexing model introduces a failure surface that HTTP/1.1's per-connection queue model does not have, and Go's net/http client exposes it through a combination of defaults that are reasonable for browser traffic but wrong for dense backend workloads.
The Multiplexing Model and Where It Breaks
HTTP/2 sends multiple request/response exchanges as streams over one TCP connection. Each stream is assigned an integer ID. The HPACK-compressed HEADERS frame opens a stream; DATA frames carry the body; RST_STREAM cancels it. From the client's perspective, all of this is concurrent.…