FrontendHaltNetworking·Intermediate·Conceptual·1 min read
What problem did HTTP/2 multiplexing solve?
Short interview answer
Under HTTP/1.1 a connection handled one request at a time, and browsers opened only about six connections per origin, so many resources queued. HTTP/2 lets many request-response streams share one connection concurrently, removing that per-connection serialization and the need for as many connections.
Key takeaway
Explain the underlying mental model clearly, then support it with a concrete example and its trade-offs.