HTTP/3 Is Next Generation HTTP. Is It QUIC Enough?
summary
HTTP/3 moves HTTP over QUIC on UDP and claims real wins: independent streams remove TCP head‑of‑line blocking, zero RTT enables near‑instant requests, and Google/Facebook report measurable speedups though exact numbers vary. Deployment pain points include widespread UDP blocking, servers seeing QUIC traffic as DDoS, higher CPU costs today, and a notable OpenSSL delay in TLS support. Multiple browsers and CDNs (Chrome/Firefox nightly, Cloudflare) and tools like curl experimental already interoperate for testing, with standards expected around early 2021.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:50Agenda
- 1:32HTTP 1 to 2 to 3
- 6:17Problems
- 9:24Why QUIC and how it works
- 13:53HTTP/3
- 19:09Challenges
- 23:58Coming soon
- 28:55Takeaways
related talks
40mHTTP/3 - HTTP over QUIC is the next generation
37mHTTP/3: why and where are we?
34mHTTP/3 is coming
51mHTTP/3 and QUIC: Who, what, where, when and, WHY?
46mHTTP/3: It's all about the transport!
34mSecuring the Next Version of HTTP: How QUIC and HTTP/3 Compare to HTTP/2
34mQUIC and HTTP/3: Too Big to Fail?!
35mOn QUIC, HTTP/3 and tech stack unification