Upgrade to Pro — share decks privately, control downloads, hide ads and more …



The announcement of HTTP/3 at the start of November 2018 may have come as a surprise for a lot of us.

Indeed, compared to the 18 years that separated HTTP/1.1 et HTTP/2, this announcement comes only 4 years after the release of HTTP/2.

But the biggest surprise is under the hood, with a replacement of the transport layer.

In this talk, we will explain why this version 3 of the HTTP protocol has been designed, especially around the latency topic.

We will cover as well how technically this version works, and what it will bring to our applications, and what are the challenges, that us, DevOps, we will need to address, in order to fully benefit from this version.

Benoit Jacquemont

June 07, 2019

More Decks by Benoit Jacquemont

Other Decks in Technology


  1. HTTP/3 HTTP/3 It's All About The Transport! It's All About

    The Transport! Benoit Jacquemont Benoit Jacquemont @bjacquemont @bjacquemont
  2. Chappe Telegraph A B C D E F Volume of

    data: 7 bit (92 symbols) Transport: light Speed: 3 symbols per minute
  3. Truck Full Of SSD Transport: 15 TB SSD in a

    container Volume of data: 3 exabyte, aka 3 millions of TB (200k disks)
  4. SSD Truck Performances Latency: 40 minutes (30 km at 50

    km/h average) Bandwidth: 10 Petabit/s (or 10.000 Tb/s)
  5. Bandwidth And Latency Evolution Medium Bandwidth Latency 56k modem 40

    Kbit/s 150ms ADSL 18 Mbit/s 50ms Optical Fiber 200 Mbit/s 10ms Bandwidth: 5000x Better Latency: 15x Better
  6. Should I Care About Latency? The 3 Important Time Limits

    In UX Source: Jakob Nielsen, "Usability Engineering" 1993; Miller 1968 0.1s: instantaneous feeling limit 1s: ow of thought limit 10s: user attention limit Latency Is The #1 Enemy Of Web UX!
  7. Initiator Receiver SYN ACK SYN-ACK Client Hello Server Hello Client

    Key Exchange Server Finished Client Finished HTTP Request HTTP Response TCP TLS HTTP Time
  8. HTTP/3: What's In It For Me? HTTP/3 = QUIC HTTP/3

    doesn't change HTTP/2 semantics HTTP/3 is mostly a drop-in replacement for HTTP/2 Main (only?) change for web dev: streams priority Code for HTTP/2 and bene t from HTTP/3 when it's out!
  9. QUIC Maturity Enabled by default in Chromium since 2013 Enabled

    on Chrome for Google web servers Ongoing standardisation by IETF 7 November 2018: rst interop connection between LiteSpeed and Facebook tools.ietf.org/html/draft-ietf-quic-http-24
  10. HTTP/3 Key Takeaways QUIC latency is far better than TCP+TLS

    HTTP/3 allows HTTP/2 to meet its full potential Final HTTP/3 release date not yet de ned... ... but already battle tested Still a lot of work to make it happen