HTTP/1 to HTTP/2 to HTTP/3

Checkout our bestselling System Design Interview books:

Other things we made:

Animation tools: Illustrator and After Effects

ABOUT US:
Covering topics and trends in large-scale system design, from the authors of the best-selling System Design Interview series.

[iuriena]

Minor correction about HTTP/2 server push: it's not for updating a resource in the client side. It's a way to proactively send a resource known to be used on the requested resource (like sending a js when a request to an html is made), to avoid one round trip

[BrianThorstad]

Learned something new…so I subscribed.
Quality, no fluff, presentation.

[Calslock]

Just yesterday I tried to find simple answer to this topic, but I couldn't on any site I've visited, and today this video just popped in my recommendations, and explained everything better in just 4 minutes. Thank you ☺💕

[andressolar]

those are excellent tutorials. clear, short and straight to the point. the best find in years.

[mahendra]

Your explanation and animations are simply amazing. They are crystal clear and straight to the point.Thanks a ton for sharing your knowledge. 👏👏👏

[ColinRichardson]

I learnt so much from this short video..
The history of HTTP made understanding the reasons for its successors to be specced and made this a great progression video rather than just a simple DATA DUMP..
Thank you for making this..

[der.Schtefan]

HTTP is older than 1996. The first version named 0.9 was released in 1991, when the WWW was created at CERN by Tim Berner-Lee. Before the FORMAL release of HTTP/1, most features were available far before that in various draft states. I would say the HTTP/1 that most of us know and love was shaped around 1994.

[ReflectionOcean]

Http/1/1.1/2 are built on TCP

Http/1.1 introduces "keep-alive" which allows a connection to reuse and avoid the expensive 3 way handshake

Http/2: Http streams and (server) push capability

Http/3 introduces QUIC protocol based on UDP to make stream first class in transportation layer, replacing TCP usage for mobile devices

[andreylebedenko]

The HTTP/3 looks perfect for exceptionally precise user tracking, especially with a direct inbound UDP connection on an end-user device.

[Mutual_Information]

Wow, just discovered this channel. Beautifully animated and on a subject I know very little about. Excellent! Subscribed

[nulla]

This 4 minute video is more understandable than the 90 minute lecture I had about this

[KRICHAN_Technologies]

What a efficient content within in 4 min and this is unbelievable. Great work team and Thank you for sharing such great content

[stoneshou]

Been very looking forward to this, and thank you so much for doing this so clear and concise

[ayush_walia]

One question, if we are moving to UDP based protocol in HTTP/3, isn't that a problem for reliability? I mean in TCP we have concept of ack for it. Doesn't UDP based protocol have issue with packet loss?

[CppExpedition]

Such an animated presentation! :D

i'm inverting the color video because dark > white for our eyes!

[wilfred-almeida]

Apart from the content, the animations and thumbnail are quite good. Cheers to the editor!

[gaburiru]

Thank you for the clear explanation! Also it's unbelievable that http/3 has been released while /2 merely been used for some years 🤣

[mortified]

So happy to finally find a straight forward explainer on this and why it's important. I'll likely be sharing this and I'm definitely subbing.

[languagemodeler]

This is the best channel. Look forward to every new video.

[Dr_Larken]

New sub here! This is my first video & followed you on twitter!

This channel is going places!