HTTP/2 Multiplexing
HTTP/2 multiplexing allows multiple requests and responses to travel concurrently over a single TCP connection as interleaved streams. Unlike HTTP/1.1, which processes one request per connection at a time, HTTP/2 removes the need for many parallel connections and reduces latency.
Technical Architecture & Deep-Dive
With HTTP/1.1, browsers opened up to six connections per host and queued additional requests, causing head-of-line blocking at the HTTP layer. HTTP/2 splits messages into frames tagged with stream IDs, so slow responses no longer block fast ones on the same connection.
HTTP/2 still runs over TCP, so a single lost packet can stall all streams. HTTP/3 solves this with QUIC. Edge platforms negotiate the best protocol with each client automatically, while maintaining warm, multiplexed connections to upstream APIs.
Key Architectural Benefits
Implement HTTP/2 Multiplexing at the Edge
Deploy lightweight API aggregation, edge caching, and secret injection in minutes without Docker containers or complex servers.
Frequently Asked Questions
Q:Does HTTP/2 make API aggregation unnecessary?
No. Multiplexing reduces connection overhead, but each upstream call still costs a round trip and server processing. Aggregation at the edge still cuts total latency on mobile.
Related Architecture Concepts
HTTP/3 is the latest version of HTTP, built on QUIC, a transport protocol running over UDP. QUIC combines connection setup and TLS encryption into fewer round trips and handles each stream independently, so packet loss on one request does not stall others.
Connection pooling is maintaining a set of open, reusable connections to a database or upstream service so requests can borrow an existing connection instead of opening a new one. It avoids repeated TCP and TLS handshakes and prevents exhausting server connection limits.
A network request waterfall is a chain of HTTP requests that must happen one after another because each depends on data from the previous response. Each step adds a full round trip, so total load time grows with the length of the chain.