Why Use LiteSpeed's QUIC Server? https://www.litespeedtech.com/images/logos/litespeed/ls-quic-logo.png 2017-11-17 20:21:30 With LiteSpeed QUIC you get production-quality, availability to millions of websites, Anti-DDoS expertise, and more.

Why use LiteSpeed’s QUIC

LiteSpeed's QUIC web server implementation is special.

You get production-quality, availability to millions of websites, Anti-DDoS expertise, and more.

LiteSpeed QUIC Logo

Delivering Cutting-Edge Technology

Staying at the forefront of web technologies is what we do. We were the first to support SPDY/3.1. We were the first to support HTTP/2, at one point powering 96.5% of all HTTP/2-enabled websites.

Our customers demand cutting-edge technologies such as QUIC. We are happy to deliver.

If you are already using LiteSpeed Web Server, all you need is the 5.2+ release, as QUIC is enabled by default. (There are also finer-grained controls to configure QUIC per listener, per vhost, and so on.) If you are thinking about switching to LiteSpeed, good! Did you know that it is a drop-in Apache replacement?

LiteSpeed QUIC is production-quality and available to millions of websites.

At the time of this writing, we only know of four working server-side QUIC implementations:

Here at LiteSpeed, we pride ourselves on the proven performance of our products, in particular that of the web server and web ADC. Our QUIC implementation is built using the same principles and runs using the same speedy framework.

Production Quality
Anti-DDos at UDP

LiteSpeed's anti-DDoS expertise is vital when using UDP, which is prone to DDoS attack.

UDP's simplified handshake implementation makes it more vulnerable to DDoS attack, when compared to TCP. LiteSpeed's anti-DDoS expertise offers an important level of protection.

Because LSWS's event-driven architecture handles all connections with a single process (or a few processes), LiteSpeed is easily able to gather data about the number of connections or amount of bandwidth an IP is using. This allows the server to impose limits in an efficient manner.

Other process-based servers have trouble implementing features like this because they need to collect information from their many processes. By the time they know which IP to block, it's too late.

LiteSpeed's Multi-process, event-driven architecture scales well.

The QUIC protocol is CPU bound, as it needs to encrypt the traffic. Throughput can be maximized through the use of multiple CPU/cores.

Many processes use the same UDP port to receive and send QUIC packets. Because connection state is stored in a single process, a packet may need to be rerouted after it is read. This poses a challenge to the effective handling of packets that are received on the same port by different processes. LiteSpeed's multi-process, event-driven architecture rises to this challenge nicely. In order to route a packet to its designated process, LiteSpeed uses lightweight IPC mechanisms: shared memory and signals. Deep copies of packet data and expensive socket API calls are completely avoided.

LiteSpeed's QUIC implementation scales up with the number of CPU cores.

Multi-Process and Event Driven
Server Push

LiteSpeed QUIC supports server push.

QUIC server push allows you to send information to the user's browser without waiting for it to be requested. In some cases, this can make pages load twice as fast! LiteSpeed's QUIC implementation supports server push, but Caddy's does not.

LiteSpeed QUIC is faster!

LiteSpeed's QUIC implementation is on average 3.5 times faster than Caddy's.

LiteSpeed as Proxy

LiteSpeed QUIC can be used as a proxy

You can use LiteSpeed Web ADC as a QUIC-to-HTTP proxy in front of your website. In addition to the performance boost provided by QUIC, your site will get the benefit of ADC caching.

Get LiteSpeed Web Server