What is HTTP/3 and how does it make HTTP faster?

HTTP is the most popular foundation for designing and building APIs today. HTTP/1.1, first published in 1997, still provides the syntax and semantics of HTTP today. However, HTTP/2 (published in 2015) and HTTP/3 (finished and currently in the IETF publishing queue) change the way how HTTP works under the hoods.
HTTP/3 replaces the well-known foundations of TCP and TLS with a new protocol, QUIC. QUIC (which sits on top of UDP) avoids some of the problems that HTTP/2 still had and therefore allows HTTP to behave differently.
Listen to Robin Marx explaining what HTTP/3 is, how QUIC changes the way how the HTTP protocol stack functions, and what that means for API designers and developers.
Since HTTP syntax and semantics remain as they are, HTTP/3 (just like HTTP/2) is not a revolutionary or breaking change. But just like HTTP/2, HTTP/3 changes some of the constraints of HTTP, meaning that API designers and developers can take advantage of these improved capabilities of the HTTP protocol stack.

Article series on HTTP/3 and QUIC, with many technical details:

[shashankkhandelwal]

This was really great 🤩. Thanks for having such a great conversation about Http 3 from the perspective of API landscape.

[romandzhadan]

it's a wonderful talk, thank you guys for a brief overview :)