gRPC over HTTP/3 is finally a thing | Backend Engineering Show

The gRPC team just submitted a proposal to support HTTP/3. This is big news and we have been waiting for a long time for this. In this show, I’ll discuss why would you want gRPC, why gRPC picked HTTP/2, what is actually wrong with HTTP/2 and what HTTP/3 solves. And Finally, I’ll discuss what is wrong with HTTP/3 and pitfalls that you as gRPC user might run into. Let us discuss!

0:00 Intro
1:30 why gRPC
5:20 gRPC & HTTP/2
7:30 gRPC & HTTP/3
8:50 What is wrong with HTTP/2
29:30 What is good about HTTP/3
37:00 What’s wrong with HTTP/3

Resources

Become a Member on YouTube

🔥 Members Only Content

Support my work on PayPal

🧑‍🏫 Courses I Teach

🏭 Backend Engineering Videos in Order

💾 Database Engineering Videos

🎙️Listen to the Backend Engineering Podcast

Gears and tools used on the Channel (affiliates)

🖼️ Slides and Thumbnail Design
Canva

🎙️ Mic Gear
Shure SM7B Cardioid Dynamic Microphone

Cloudlifter

XLR cables

Focusrite Audio Interface

📷 Camera Gear
Canon M50 Mark II

Micro HDMI to HDMI

Video capture card

AC Wall for constant power

Stay Awesome,
Hussein

[ansitun]

This is GOLD!
It's crazy how this video has only 17k views when you have 280k subs, that's around 6% of your subscribers who watched it.
Youtube need to push such content to s/w folks even more who waste time watching trendy/useless content!
By the way, I am taking your "Fundamentals of Backend Communications and Protocols" to support your passion and your knowledge. Know more and do better!

[BIELSIMON]

GRPC is not only used in cloud and high bandwidth scenarios. It is also used on applications over mobile networks, one of the situations where it makes the most sense. Reducing latency and bandwidth usage there is crucial for user experience, data usage and battery consumption

[exapsy]

Hussain you're the best at explaining in depth such concepts. Thank you. Reading the RFCs is always also the best kind of help, but you make excellent briefs.

[krozaine]

Thank you for your content! And take all the tangents you want, this is your unique show. There are very subtle, crisp and precise knowledge when you take tangents like the one where you talked about databases or hard disks. The fact that you are sub-consciously aware that you had to get back on the main track keeps the side lines very insightful, precise & relevant 😃

[hrahman]

Love the Arabic saying. When you dropped it I was like woah I had no idea you spoke Arabic. Keep up the great work man love your content ✌️🙏

[JohnZakaria]

I found it very enlightening to hear what the different http version actually do.
Never thought about anything he mentioned

[abhishekshrivastav]

I like to think deeply about systems working like you do. Kudos for good video.

[helmchen]

Hey i reached the end ;)
I find the HTTP/3 thing interesting, but as a web developer I would be happy if gRPC with HTTP/2 would be natively supported in the browser. I know there are proxies, but somehow it doesn't feel right.

[jaidewani]

I was dying on the floor laughing when I heard "arigato gozaimasu" out of no where 😂😂

[thesyd]

man you're awesome thanks for all :) au revoir =D

[shreyasjejurkar]

Just a small correction, the proposer James NetwonKing is not from GRPC team officially. He is a Principle SE from .NET team at Microsoft.
As with .NET 6, the Http3 and quic implementation is coming up, so grpc can benifit it, because of which he proposed that one, so that other language can implement it and grpc will be more good everywhere!

[elmarulian]

I reached the end, thanks for the info

[andreffrosa]

In HTTP2 the replys do jotnhave to come in the same order as the requests were sent. That is pipeling in http1.1. Head-of-line vlocking in http2 is only caused by lost segments/packets which block every "channel/stream". In addition, http2 suffers from other problems of TCP which QUIC resolves.

[AbdullaH]

I reached the end. like your content bro

[hamedghezelbash]

Thanks for ur high quality contents mate

[shaybs]

Hi,
Hussein Nasser could please elaborate on whether coders/developers will have to make massive changes for gRPC over HTTP/3 support when HTTP/3 is rolled out?
Shuaib

[ashutoshmuni]

Hussain i like these stuff
arigato gozaimasu!

[willytarreau]

Hey Hussein, keep in mind that H2's head of line blocking is not limited to TCP losses. It also happens when buffers fill due to the window-in-window nature of the protocol. There's stream-level flow-control but too small window destroy bandwidth (limiting it to the window/rtt) and increasing stream windows will freeze everyone as soon as the underneath TCP window is smaller or buffers get congested. *This* is the real problem H2 suffers from because it relies on an in-order protocol (TCP) that cannot lose extraneous packets that clog the buffers. That's why even in the datacenter where there are very few losses, H2 is rarely used on internal infrastructure. QUIC+H3 were designed to change that, time will tell if they make their way into the DC (I doubt it due to UDP not being welcome there).

[kanglei]

Hello, teacher, I am interested in distributed storage. Do you have any materials in this direction to learn and practice projects to become a distributed storage developer. Thanks!

[learntocode]

Hi Mr Hussein, Please note that I set up a basic asyncio gRPC server and client using python streaming from webcam to localhost client everything works fine but my i7 MacBook pro CPU Utilization 99% . and more than 2000 threads. Thanks Mr.