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

HTTP/3

 HTTP/3

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
Tweet

More Decks by Benoit Jacquemont

Other Decks in Technology

Transcript

  1. HTTP/3
    HTTP/3
    It's All About The Transport!
    It's All About The Transport!
    Benoit Jacquemont
    Benoit Jacquemont
    @bjacquemont
    @bjacquemont

    View Slide

  2. But HTTP/2 Just Came
    Out!?
    HTTP/1.1: 1997 - HTTP/2: 2015 - HTTP/3: 2018 (announcement)

    View Slide

  3. HTTP/3
    =
    HTTP/2 Over QUIC
    Kwiiiick!

    View Slide

  4. HTTP/2 = TCP
    Application
    Transport
    HTTP/3 =
    QUIC

    View Slide

  5. What's The
    Problem With
    TCP?

    View Slide

  6. View Slide

  7. View Slide

  8. View Slide

  9. View Slide

  10. View Slide

  11. View Slide

  12. View Slide

  13. View Slide

  14. View Slide

  15. View Slide

  16. View Slide

  17. Hey, but latency sums up!

    View Slide

  18. Network Performance
    Latency &
    Bandwidth

    View Slide

  19. View Slide

  20. Chappe Telegraph
    A B C D E F
    Volume of data: 7 bit (92 symbols)
    Transport: light
    Speed: 3 symbols per minute

    View Slide

  21. View Slide

  22. View Slide

  23. Chappe Telegraph Performances
    Latency: 0.003 ms (light delay over 10km)
    Bandwidth: 0.4 bit/s

    View Slide

  24. Truck Full Of SSD
    Transport: 15 TB SSD in a container
    Volume of data: 3 exabyte, aka 3 millions of TB
    (200k disks)

    View Slide

  25. View Slide

  26. View Slide

  27. SSD Truck Performances
    Latency: 40 minutes (30 km at 50 km/h average)
    Bandwidth: 10 Petabit/s (or 10.000 Tb/s)

    View Slide

  28. Bandwidth Latency
    Chappe Telegraph 0.4 bit/s 0.003 ms
    SSD Truck 10 Pbit/s 40 minutes

    View Slide

  29. 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

    View Slide

  30. View Slide

  31. 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!

    View Slide

  32. HTTP: A History Of
    Battle Against Latency

    View Slide

  33. View Slide

  34. View Slide

  35. View Slide

  36. View Slide

  37. View Slide

  38. View Slide

  39. View Slide

  40. View Slide

  41. View Slide

  42. View Slide

  43. View Slide

  44. View Slide

  45. View Slide

  46. Hey, It Gets Worse!

    View Slide

  47. The TLS Handshake

    View Slide

  48. 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

    View Slide

  49. Introducing QUIC
    Previously Known As
    Quick UDP Internet Connections

    View Slide

  50. QUIC Handshake
    Initiator Receiver
    QUIC HELLO
    QUIC TOKEN
    QUIC HELLO + TOKEN

    View Slide

  51. QUIC
    =
    Transport And Encryption

    View Slide

  52. TCP/TLS Vs QUIC

    View Slide

  53. But Isn't UDP Unreliable?
    What Was The Point Of TCP, Again?

    View Slide

  54. View Slide

  55. View Slide

  56. View Slide

  57. View Slide

  58. View Slide

  59. View Slide

  60. View Slide

  61. View Slide

  62. View Slide

  63. View Slide

  64. View Slide

  65. View Slide

  66. View Slide

  67. View Slide

  68. View Slide

  69. View Slide

  70. But With
    UDP...

    View Slide

  71. my
    important
    message
    1 2 3 4 2 1 4
    But With
    UDP...

    View Slide

  72. QUIC Takes Care Of The
    Packets...
    ...At The Browser/Server
    Level

    View Slide

  73. View Slide

  74. View Slide

  75. View Slide

  76. View Slide

  77. View Slide

  78. View Slide

  79. View Slide

  80. View Slide

  81. View Slide

  82. View Slide

  83. View Slide

  84. View Slide

  85. TCP Is Strongly Coupled
    To The Network
    Connection

    View Slide

  86. View Slide

  87. View Slide

  88. View Slide

  89. View Slide

  90. View Slide

  91. View Slide

  92. View Slide

  93. View Slide

  94. View Slide

  95. QUIC Is Loosely Coupled
    To The Network
    Connection

    View Slide

  96. TCP And Head Of Line
    Blocking

    View Slide

  97. View Slide

  98. View Slide

  99. View Slide

  100. View Slide

  101. View Slide

  102. View Slide

  103. View Slide

  104. View Slide

  105. View Slide

  106. View Slide

  107. View Slide

  108. View Slide

  109. View Slide

  110. View Slide

  111. View Slide

  112. View Slide

  113. View Slide

  114. View Slide

  115. With Bad Connectivity, HTTP/2
    Streams Can Be Worse Than
    HTTP/1.1 Parallel Connections!

    View Slide

  116. View Slide

  117. View Slide

  118. View Slide

  119. View Slide

  120. View Slide

  121. View Slide

  122. View Slide

  123. View Slide

  124. View Slide

  125. View Slide

  126. View Slide

  127. View Slide

  128. View Slide

  129. View Slide

  130. View Slide

  131. View Slide

  132. View Slide

  133. View Slide

  134. View Slide

  135. View Slide

  136. QUIC Streams Are
    Independent From Each
    Other.
    No HOL Blocking

    View Slide

  137. 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!

    View Slide

  138. QUIC
    Challenges

    View Slide

  139. View Slide

  140. View Slide

  141. View Slide

  142. View Slide

  143. View Slide

  144. View Slide

  145. View Slide

  146. View Slide

  147. View Slide

  148. View Slide

  149. View Slide

  150. View Slide

  151. View Slide

  152. View Slide

  153. View Slide

  154. View Slide

  155. View Slide

  156. View Slide

  157. View Slide

  158. View Slide

  159. View Slide

  160. View Slide

  161. View Slide

  162. View Slide

  163. View Slide

  164. View Slide

  165. 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

    View Slide

  166. 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

    View Slide

  167. Thank You!
    Questions?
    For more information:
    @bjacquemont
    daniel.haxx.se/http3-explained/
    www.chromium.org/quic/

    View Slide