httpquichttp3

Is HTTP client side connection pooling still valid when QUIC, HTTP/3 is the major/all traffic expected?


As modern systems, especially for micro-services, connection pooling for HTTP client is quite often deployed. But with the QUIC + TLS1.3, it seems like to me that connection pooling would be useless as there is support for 0-RTT in QUIC.

Is any QUIC expert available to share more on this topic?


Solution

  • It's still valid, because:

    However since QUIC already provides multiplexing multiple requests on a stream the client should not be required to keep a full pool of connections around. A single connection is typically sufficient, as long as the server advertises being able to support a high enough number of streams.