Why Use a QUIC Web Server? https://www.litespeedtech.com/images/logos/litespeed/ls-quic-logo.png 2017-11-17 20:21:06 QUIC is better than HTTP/2. It's faster, secure, available, and COOL! Learn more.

Why use QUIC

QUIC is better than HTTP/2. It's faster, secure, and available.

With QUIC, you can be on the cutting edge, and give your users a better experience at the same time.

QUIC is better than HTTP/2

QUIC is Better than HTTP/2

QUIC was designed as a replacement for HTTP/2 and a way to address some of the latter's inadequacies. QUIC improves upon HTTP/2 with:

  • Dramatically reduced connection-establishment time
  • Multiplexing without head-of-line blocking
  • Improved congestion control
  • Connection migration

QUIC is Faster

Reduce connection-establishment time for a speedier page load

Since the inception of the web, clients and servers have communicated using HTTP. This protocol has evolved to adapt to market demands by adding support for keepalive connections, virtual hosts, range requests, and many other performance-boosting mechanisms. Yet each version of HTTP has used TCP to deliver its packets.

Before the first HTTP request can be sent, a TCP connection must be established. The TCP handshake requires one round-trip. With the recent moves toward user privacy, many websites have switched to using HTTPS (HTTP Secure). The security does not come for free: TLS imposes its own handshake. That's two round-trips before the first HTTP request is even sent.

It is important to realize that a new connection occurs not only when a user first opens a website; a new connection is established any time a request is made after several seconds of inactivity. This is because keeping track of connections consumes server resources and it is common practice for web servers to close connections that have been idle for a few seconds. What this means is that for some usage patterns, a new connection is established nearly every time a user interacts with the web application! Now the rationale for using QUIC is even more apparent.

QUIC implements TCP-like reliability mechanisms in the protocol itself. This makes it feasible to use the unreliable UDP for data transfer, removing the TCP handshake penalty. To avoid the TLS penalty, QUIC provides its own handshaking mechanism, often allowing it to include the initial HTTP requests in the first set of packets that are sent out on a new connection.

Use multiplexing to avoid head-of-line blocking

HTTP/2 over TCP suffers from head-of-line blocking: when one packet is lost, all subsequent packets must wait for it to be retransmitted before the page can be loaded.

QUIC is designed to avoid such a problem. Multiplexing sends data across several streams, and when a packet is lost, it only impacts that one stream. The other streams will continue transmitting, and the page may continue loading. Under these circumstances, a lost packet is much less noticeable.

Improve congestion control for a better user experience

HTTP/2 and TCP rely on consecutive packets, which means the connection is stalled when one packet goes awry. QUIC and UDP, on the other hand, don't require packets to arrive in order, and as such, one missing packet can't tie up the stream's entire queue.

Effectively handle connection migration in a highly-variable network environment

Nowadays your users are not just sitting at their desks, typing away on a desktop computer with a dedicated line to the internet. They're reading your WordPress blog on the train on their way to work. They're shopping your Magento store on their mobile phone while riding the bus. More than half of today's internet users worldwide are on the go. They switch from Wi-Fi connection to Wi-Fi-connection to cellular data connection and back again as part of their mobile lifestyle. Traditional TCP-based protocols have had difficulty keeping up as connections are lost and resumed, but not so UDP and QUIC.

With QUIC powering your site, shop, or blog, packet loss is less crippling, and mobile user experience is much improved.

QUIC is faster
QUIC is secure

QUIC is Secure

In contrast to HTTP, the use of encryption is mandated in the QUIC protocol itself. With the exception of a few initial packets that carry handshake-specific messages, all QUIC payload is encrypted.

QUIC is Available

Since QUIC is enabled by default in Chrome and also available in Opera, the majority of the internet's traffic has the ability to experience QUIC. And, since Google's ample web presence has been QUIC-powered for the last five years, you can rest assured that it works.

QUIC is available
QUIC is cool

QUIC is COOL!

Google has been having all of the fun with their new protocol, but now you can get in on the QUIC action, too. Future-proof your sites. Make them QUIC-powered!

Get LiteSpeed Web Server