Get my Fundamentals of Networking for Effective Backends udemy course Head to network.husseinnasser.com for a discount coupon (link redirects to udemy with coupon applied)
@umeshshetty06052 жыл бұрын
I am a Network Engineer but I love the backend Engineering stuff that you show and it makes it easier for me to understand application problems while troubleshooting the network side of it. Thank You and Keep posting !!!
@hnasr2 жыл бұрын
Thanks!! Glad to see more network engineers in the channel. Cheers
@whereismypipey4 жыл бұрын
I loved the picture grid loading example to nicely visualize the performance and difference in number of connections.
@allisonmachado4 жыл бұрын
Netflix for developers :)
@hnasr4 жыл бұрын
❤️
@ScarzChosenspokesmen3 жыл бұрын
LOL great comment
@nadertarek48223 жыл бұрын
HAHA! literally
@andile59452 жыл бұрын
And you don’t have to use someone else’s account
@nateengedal79392 жыл бұрын
hard pass on the chill
@balramverma48733 жыл бұрын
This channel is to addictive that even in the period I’m focusing on front end stuff i end up watching these.
@dean60464 жыл бұрын
thank you Hussein! I want you to understand that this is great content and I love the way you deliver it with such energy and excitement. I frequently download videos from KZbin for offline use and I just downloaded this one because I think it's great content.
@omriterem64484 жыл бұрын
One of the best KZbin channels for programmers...
@amsterdenko98543 жыл бұрын
First time on your channel. Subscribed after this first video. I like your style of content delivery. Such a themes become much more entertantaining. Thank You!
@mohamad54973 жыл бұрын
Your content is great! Thanks Hussein!
@andikakurniawan41882 жыл бұрын
I like this guy. This guy is smart and also have talent to be teacher...
@subhamthemusicalguy88514 жыл бұрын
Joined your channel to support you. Excellent work
@hnasr4 жыл бұрын
❤️ thanks Subham ! Appreciate your support
@fraollemecha3 жыл бұрын
HTTP/2: We gotta do it fast. Michael Scott: That's what she said.
@이유창-w4z4 жыл бұрын
excellent!! very clear provocation and easy to understand.
@hnasr4 жыл бұрын
Thank you 🙏
@TimothyNyota2 жыл бұрын
Subscribed!! Great content, man!!
@natarajboina75254 жыл бұрын
This was very insightful. Thanks for this video.
@hnasr4 жыл бұрын
Thanks for your comment Nataraj
@Esmi_here Жыл бұрын
It was so fun watching!!
@danielkrajnik38174 жыл бұрын
the more I learn about software, the more I find that every next upgrade boils down to parallelization
@SateeshBandi5 жыл бұрын
Very good demo.. I loved it.
@ankitsah28194 жыл бұрын
Awesome explanation 👍🏻
@SatishKumar-jb9qm4 жыл бұрын
Your content is great! Thank you for posting.
@mageshp59985 жыл бұрын
Liked your demo!!
@shubhampawar22074 жыл бұрын
Awesome Presentation!...
@hnasr4 жыл бұрын
😊🙏 thanks
@longtranbao41772 жыл бұрын
Thanks you! In school people don't teach about this stuff.
@hozay65523 жыл бұрын
So many advances for the internet that I was not aware of!
@oah84654 жыл бұрын
More reasons to love. L4 LBs. Thx Hussein.
@kaleemullah2472 жыл бұрын
Loved the demo.
@AbuBakrSadiqi-b7t29 күн бұрын
very nice and informative video, thanks for it.
@GauravJain1083 жыл бұрын
Thanks, Hussein! :)
@smohammadhn3 жыл бұрын
Fantastic explanation, loved it
@romantsyupryk30094 жыл бұрын
Thanks so much for this video tutorial.
@amrudeshs4 жыл бұрын
Hei. Great info. Thnx. Can you also make a comparison between HTTP2 server push and Websockets based push messages? I understand that they dont serve the same purposes but a short video on it explaining when to use what would be great.
@romantsyupryk30094 жыл бұрын
Amazing demo HTTP/1.1 and HTTP/2.0 Thanks you very very very much.
@hnasr4 жыл бұрын
thanks Roman for all the love and comments!!!
@romantsyupryk30094 жыл бұрын
@@hnasr 😃😉
@Lucasmont0014 жыл бұрын
excellent video! Thanks! ;)
@bharat6395 жыл бұрын
I have watched a lot of your videos. Thank you very much for sharing your knowledge.
@AwesomeMetalBands4 жыл бұрын
Seriously great content very very interesting!!@
@palaniappanrm62774 жыл бұрын
How to host a server in local with HTTP/2 support? Does node http-server, apache tomcat support it?
@hnasr4 жыл бұрын
Palaniappan RM sure all of those support it! Check out this video where I show h2 on caddy because its the easiest Getting started with Caddy the HTTPS Web Server from scratch kzbin.info/www/bejne/qmXRkn98iNF1prM
@rahulmalu67414 жыл бұрын
Hi @husseon Nassar: In the demo for http2, did you used the server push mechanism to push the 100 images or only the protocol was set to http2 (without enabling the server push)?
@harshg20034 жыл бұрын
How can I check if my web server supports Http/1.1 or H/2 or H/3? How can I force H1 and H2 on either client side or server side, if they supports both?
@hnasr4 жыл бұрын
Hey Harash, I recommend chrome dev tools. Good idea ill make a video on this
@saumyapandey2182 жыл бұрын
What happens when a file is already cached in the client but the server pushes the file because of its configuration?
@waagnermann2 жыл бұрын
when you showed benchmarks where it was written that there was 6 TCP connections? in network panel
@hnasr2 жыл бұрын
From Google paper Popular Web browsers, including IE8 [2], Fire- fox 3 and Google’s Chrome, open up to six TCP connections per domain, partly to increase parallelism and avoid head-of- line blocking of independent HTTP requests/responses, but mostly to boost start-up performance when downloading a Web page. static.googleusercontent.com/media/research.google.com/en//pubs/archive/36640.pdf
@flobbie873 жыл бұрын
What, where does it say in the spec that i have to wait for the response to send another request? I hope no actual client does that.
@Ranjith_P2 жыл бұрын
Its a huge performance difference - thats what she said
@devashishrana16373 жыл бұрын
Suppose my configuration is client -> gateway -> server, how will http2 behave in this scenario between each layer?? or should I just keep only client and gateway in http2?
@chenrvn4 жыл бұрын
1. Thanks, Gr8 video 2. It will be helpful if u will show the stream Ids in the http request/response and the TLS connection mechanism 😎
@hnasr4 жыл бұрын
Thanks Chen! That is a great idea diving deep into the belly of the beast of HTTP/2.. will consider it in the future.
@chenrvn4 жыл бұрын
@@hnasr you are the men
@AnilSharma-gr6ck2 жыл бұрын
very good , thanks
@abdelrhmanahmed13783 жыл бұрын
does http2 also multiplex the segment inside each request or send them in sync and wait for each segment ack ?!
@abnan00015 жыл бұрын
I checked again brother Is there any update for the series
@sreevishal22234 жыл бұрын
michael scott..! , that's what she said.. haha :p :p Nice explanation..!
@Tony-dp1rl Жыл бұрын
Those CONs of HHTP/2 are certainly a stretch, given a server could return a HTML page with all sorts of unused assets in it anyway which effectively creates a PUSH in terms of network load ... and the chances of having a H1 load balancer and H2 backend are almost zero.
@45xtc4 жыл бұрын
Thank a lot Hussein.one question?for example clent says keep alive and server response not keep alive.what does it happen in tcp connection?client will try to re establish again with 3 way handshake?
@hnasr4 жыл бұрын
If the server doesn’t support keepalive (which I will be surprised if it doesn’t means it is so old its 1997 or prior) the connection will be terminated after the response will be created. In http/2 the connection will be always kept alived
@45xtc4 жыл бұрын
@@hnasr thank you very much for you great content that you offer us!keep going
@hhellohhello4 жыл бұрын
Sorry, but whats the difference between keep alive header and multiplexing?
@hnasr4 жыл бұрын
hhellohhello no problem! the Keepalived header instructs the server to not immediately close the TCP connection after it is made so we continue send more data through it. This was available since http 1.1 Multiplexing is the ability to send multiple requests in parallel in that TCP connection. Something we couldn’t in http 1.1 and only available in http2
@venkateswarans10123 жыл бұрын
HTTP 2 resolves head of line blocking at application layer but in transport layer (TCP) it's still exist and Quic is trying something to achieve even on transport layer level.
@shavishvilitornike2 жыл бұрын
How do I become member of this channel?
@Twerqt4 жыл бұрын
Hey, that is a brilliant explanation. I have one question. How did you say at 18:40 that there are 6 TCP connections sending images in parallel .. I couldn't make it out from the video
@hnasr4 жыл бұрын
Siddartha Reddy Thanks 🙏 6 connections are opened in case of HTTP/1 In browsers i explain this here Why Browsers have 6 active TCP Connections for each website? kzbin.info/www/bejne/jpzVY6Gja7qDhJo
@apoorvamishra59523 жыл бұрын
how can we check if it's a 6 TCP connections in case of HTTP/1.1 in developers tool?
@hnasr3 жыл бұрын
ConnectionID, I illustrate this here kzbin.info/www/bejne/gnPKl4atjZl6eqs
@apoorvamishra59523 жыл бұрын
@@hnasr cool thanks!
@PouriyaJamshidi5 жыл бұрын
cURL supports HTTP/3 (experimental) as well.
@hnasr5 жыл бұрын
Nice! Didn't know that, looks like I need to make a video about cURL, thanks !
@PouriyaJamshidi5 жыл бұрын
@@hnasr Thanks to you.
@sidharthvijayakumar3521 Жыл бұрын
This is not right load balancer layer 7 supports http 2. Recently i have created a flask app which only supports http 1.1 which using gunicorn which also does not support http 2 . Then used Cloudrun which was deployed as a backend to Classic application LB in GCP so my api in local shows as http 1.1 but the same Api in the load balancer i get it as http2 so i do not think what you said is relevant now.
@jerweiyeoh70963 жыл бұрын
Awww yis, another 1k like Either there is an ongoing meme on the community of leaving the like counts at 999 and I'm screwing it, or I'm on fire! XD PS: Appreciate the explanations, both high level and low level.
@hnasr3 жыл бұрын
🙏🙏🙏
@hazemabdelalim54323 жыл бұрын
The idea here , if the server and client keeps this connection open , isn't that some-kind of wasting resources ? if the client doesn't request anything , the server will still need to have maintain this connection even if the user doesn't use it , probably we can set a ttl to the open connection , so after that time with not being active , it will be closed
4 жыл бұрын
What is difference HTTP1.1 persistent connection and H2 multiplexing?
@hnasr4 жыл бұрын
Both HTTP 1.1 and H2 have persisted connection. (They are not closed as long as requests are being sent) The difference is in H1.1 you can only send one request at a time and you can’t send another request until you get a response.. this is made slightly better with pipelining where you can send multiple requests in the same connection but the server must respond in order the requests where sent. This causes problems with proxies and bad implementations. So browsers in HTTP 1.1 opens multiple connections to get around this limitations. In H2 you can send any number of requests in the same connections in parallel. The reason is each request is uniquely identified with a streamid. So if we get a response we know what request it belongs to All of this is hidden from us programmers but its good to understand.. Watch my HTTP/2 playlist here to learn more HTTP/2 kzbin.info/aero/PLQnljOFTspQWbBegaU790WhH7gNKcMAl-
@maheshkariya4 жыл бұрын
Thanks 🙏
@raphaelkuttruf4 жыл бұрын
great content :) how would i set up http2 in my backend network after a reverser proxy?
@arongulyas60964 жыл бұрын
HAproxy supports http/2
@Emmanuel-px9lk4 жыл бұрын
Why does HTTP 1.1 use '6' TCP connections? Is it a technical reason it is 6 or is this just a common standard?
@hnasr4 жыл бұрын
kidsWillSeeGhosts why 6 in particular I think it was anecdotal evidence that more than 6 doesn’t give more performance but more TCP overhead.. If you are asking Why H1 open many connections is to be able to send multiple requests in parallel (can’t do that in a single tcp connection) H2 allowed sending multiple requests in a single tcp connection using streams hope that helps 😊
4 жыл бұрын
If a lot of multiple objects are loaded in parallel, each object will just compete for this limited bandwidth, so each object will load proportionally slower. Also clients might be able to open hundreds of connections, but few web servers will want to do that, because they often are processing requests for many other users at the same time. A hundred simultaneous users, each opening 100 connections, will put the burden of 10,000 connections on the server. This can cause significant server slowdown.
@Emmanuel-px9lk4 жыл бұрын
@ Thanks
@abnan00015 жыл бұрын
Geodatabase related videos have been removed from your channel Could u please reupload then As the videos were helpful for us Thanks
@hnasr5 жыл бұрын
Muhammad Abnan hey Muhammed can you try again? Let me know..
@abnan00015 жыл бұрын
Hi It’s not there brother Last week I saw but since from afternoon I’m looking those But I cannot find it at all
@abnan00015 жыл бұрын
Nothing is there about geodatabase series and versioning related
@hnasr5 жыл бұрын
Muhammad Abnan Multi-User Geodatabase kzbin.info/aero/PLQnljOFTspQWseiNSmOMgsR5lgugKg_KP
@surendrasharma82383 жыл бұрын
not much learning. But still good for beginners.
@akashdeepbilkhu80762 жыл бұрын
Amazing
@treepiesinc14184 жыл бұрын
good. thanks.
@nabidulalam69563 жыл бұрын
powerful stuff :v
@ahsannasir62144 жыл бұрын
10:41 I see what you did there xD
@shah53642 жыл бұрын
thanks
@virgilbaldovin18529 ай бұрын
If someone asks me “what is an API?” i’ll send them this one
@akashdeepnandi4 жыл бұрын
21:57 that's what she said😂😂😂
@sawza03139 ай бұрын
🎉👏🏼👏🏼👏🏼👏🏼👏🏼👏🏼
@AMFLearning3 жыл бұрын
amflearning by doing
@matsematse90344 жыл бұрын
can you make the videos in arabic too?
@hnasr4 жыл бұрын
matse matse I was considering making another channel as a test or at least include subtitles but it is a lot of work.
@YineMiBen4 жыл бұрын
thanks youtube has 2x speed :)
@diasflp2 жыл бұрын
That's what she said. 😂
@masterali32705 жыл бұрын
انا رفيق علي احمد
@apoorvamishra59523 жыл бұрын
stuff is good, you just need not to make the voices , a simple and straight way of talking would be more clear, i presume.