WebTransport is a Game Changer Protocol

Поділитися
Вставка
  • Опубліковано 24 гру 2024

КОМЕНТАРІ • 74

  • @hnasr
    @hnasr  Рік тому +15

    backend course backend.husseinnasser.com

  • @HardikGhoshal
    @HardikGhoshal Рік тому +64

    Hi Hussein I just wanted to say that I got an admission offer from Technical University of Dresden for masters in Distributed Systems Engineering. And it wouldn't have been possible without your videos. I've been following you since the last couple of years and your content has been extremely helpful and thought provoking. I wouldn't have been here without you. Thanks and never stop making free content like this. ❤️

    • @oluwaseunsorinola7039
      @oluwaseunsorinola7039 Рік тому +2

      Congratulations.

    • @turbinator70707
      @turbinator70707 Рік тому +2

      If he got you a job with all this free content share the love and send him a tip!

    • @maximus1172
      @maximus1172 15 днів тому

      my bachelors grades are not good, what would you suggest

  • @thatryanp
    @thatryanp 9 місяців тому +3

    Hussein's pacing, expressions and intonation add so much context to these complex topics. 13:14 - summarizing layer 4 proxying with a single gesture and noise - I understood instantly.

  • @Gahlfe123
    @Gahlfe123 Рік тому +9

    11:35 and this why i love Postgres, has so many capabilities that i love tinkering with and i dont feel limited but know that if i need this feature from sql its probably available.

  • @redhood7105
    @redhood7105 Рік тому +16

    Unfortunately, people tend to give up control too easily. I understand that when dealing with simple tasks, it can be tempting to delegate to black-box solutions without much consideration. However, this mindset can foster a dangerous culture. While working with raw streams or low level APIs may require more code and can increase the risk of mistakes, it also presents valuable learning opportunities. Engaging with low-level APIs, streams, and similar concepts can ultimately make you a better developer, enhancing your skills and understanding.

    • @drac.96
      @drac.96 Рік тому +1

      Agreed

    • @autohmae
      @autohmae Рік тому +1

      best is to have both APIs, high level and low-level. So when someone needs to build something simple quickly, high-level will do...
      The alternative is: having a low-level API and a good open source/free software libraries/framework that implements a high-level API.

    • @parlor3115
      @parlor3115 Рік тому +1

      It's a compromise really. And us devs need to find the solution that gets the job done asap while taking into account future expansion.

    • @jacob_90s
      @jacob_90s Рік тому +1

      I kind of agree. I do think that people should be more willing to familiarize themselves with lower level concepts, rather than just treating them like black boxes as you put it. Even if you have no desire to work with code at that level, being more familiar with the mechanics of it can help you utilize it better, and avoid bad use cases.
      However in a production environment, trying to rebuild everything from scratch without first having experience on the higher level is a recipe for disaster, and a great example of premature optimization (regardless of whether you're trying to optimize for execution time, memory usage, stability, scalability, etc).
      I would also say this would be much easier to get people to do if developers would stop writing documentation which is ostensibly for 3rd parties, but in fact only makes sense to people who are already intimately familiar with it. This whole hazing routine of "I-had-to-suffer-reading-shit-documentation-so-you-do-to" really needs to stop.

  • @RootsterAnon
    @RootsterAnon Рік тому +6

    Awesome, my friend and I had to use WebRTC in order to have car game with decent UDP support for fast data transfer like playerPostion, while all other game logic was with WebSockets reliable (match start, match end, etc). WebRTC was pain in the ass so I am glad to hear there are some new protocols that as you said gives us control how we want our data be sent/received and how we deal with that on app level.

  • @VaibhavPatil-rx7pc
    @VaibhavPatil-rx7pc Рік тому

    Your explanation makes anyone visualization internal of network magics

  • @jlai383
    @jlai383 Рік тому +3

    Thanks!

  • @Akshatgiri
    @Akshatgiri Рік тому +42

    Yo this video was awesome. Web has evolved so much that it’s hard to understand how we landed on the ‘latest solution’. Knowing the history helps answer the ‘why’ for the technology. Thank you

    • @yash1152
      @yash1152 Рік тому +2

      not just web, same holds for
      computing, maths, physics, chemistry, politics and at times cotemporary culture as well

    • @vikingthedude
      @vikingthedude Рік тому +1

      This applies to my household rules as well

  • @Openspeedtest
    @Openspeedtest Рік тому +4

    I can't believe this is actually happening, it feels like a dream!

  • @P8qzxnxfP85xZ2H3wDRV
    @P8qzxnxfP85xZ2H3wDRV Рік тому +5

    Any chance we can get a comparison video between NATS and RabbitMQ? I would also love videos about Aeron and FastDDS, in comparison to ZeroMQ.

  • @LukasSchindler
    @LukasSchindler Рік тому +1

    Could you at some point make a video going into detail, how e.g. twitch is able to bypass ad blockers and the concepts involved in such processes?

  • @andrewandrosow4797
    @andrewandrosow4797 11 місяців тому

    Hello! It would be good to have a raw TCP connection in web browser.But they (web consorcium) don't want to allow it for developers

  • @kartikjain3064
    @kartikjain3064 Рік тому +1

    Hi @Hussein can you explained the Gmail backend design?

  • @dario.lencina
    @dario.lencina Рік тому

    Amen brother!!! lets do this! long life to WebTransport!

  • @DF-ss5ep
    @DF-ss5ep Рік тому +2

    I'm guessing WASM has something to do with this. With the required low level primitives, WASM would get portability between a real OS and just a web browser

  • @dhruvvadodariya4685
    @dhruvvadodariya4685 Рік тому

    Hello Hussein, great video but i have one question at 13:10 you mentiontioned something like layer-7 and layer-4, what does that mean,
    I many sound silly asking this question but I only have 3 years of experience with web development.

  • @chris-pee
    @chris-pee Рік тому +1

    Small nitpick, you seem to have mixed up unreliable with unordered, when describing datagrams (which are obviously both). In practice the difference is pretty small, but if someone uses datagrams for online multiplayer games, then it will matter.

  • @yalihart
    @yalihart Рік тому

    Hi, can you please make a video explaining how to create a WebTransport server with Datagrams and Streams?

  • @chudchadanstud
    @chudchadanstud Рік тому

    Webshizzers have done it again! They've convoluted the space and made it more complex.

  • @tyu3456
    @tyu3456 Рік тому +4

    I'm just waiting for the job descriptions - 5+ years experience required in WebTransport development 😂😂

  • @malleswaribhumireddy8630
    @malleswaribhumireddy8630 Рік тому

    Thank you about this video but I have too web transport in python how to use this

  • @saeedalobidi4195
    @saeedalobidi4195 Рік тому +3

    Hussein Nasser
    I was wondering why, now that we have IPv6, which can cover all devices in the world, each device has its own IP address so we don't have to design new bidirectional protocols such as sockets

    • @davidstephen7070
      @davidstephen7070 Рік тому +1

      ip and protocol is different things. ip is for identify device. protocol is what and how characteristic to send something.

    • @saeedalobidi4195
      @saeedalobidi4195 Рік тому

      Yes, I get that, but I mean that if each device has its own IP, we don't need bidirectional protocols since each device acts as a server, and the server may obtain the IP addresses of all linked devices and transmit them straight to a specific device. because the main purpose of the bidirectional protocol is to allow the server to send data back to the client and keep the connection alive

    • @davidstephen7070
      @davidstephen7070 Рік тому +1

      ​@@saeedalobidi4195 oh i see, i think because bussiness and permit management. thats why each client still dont get own public ip. it more easy and scallable to use NAT, one public ip used by several client by assign private ip.

  • @mohammadravand4351
    @mohammadravand4351 Рік тому

    hi, thanks for this best channel.
    but why you dont using diagrams to demonstrate , diagram really help to underestand.

  • @yash1152
    @yash1152 Рік тому

    10:56 so, how does it diffor from QUIC ?

    • @thatryanp
      @thatryanp 9 місяців тому

      WebTransport is available on both HTTP/2 and HTTP/3. QUIC is an HTTP/3 thing, basically building around head-of-line issues with TCP by using UDP instead.

    • @yash1152
      @yash1152 9 місяців тому

      @@thatryanp ohwkayh.

  • @kevinb1594
    @kevinb1594 Рік тому +1

    So what makes this better that webrtc?

    • @JetpackBattle-lc7ob
      @JetpackBattle-lc7ob Рік тому

      For starters you dont need multiple protocols and 2 seperate servers minimum to correctly establish connections

  • @ДмитрийКарпич
    @ДмитрийКарпич Рік тому

    We have epic WebRTC failure, where great idea about P2P connection was killed by NAT. Will WebTransport can be useful in real world with all this proxy, CDN e.t.c and wild zoo of browsers at client side? I see somone still support they project for IE.

  • @user-rx7fv8rg4t
    @user-rx7fv8rg4t Рік тому

    what does meant by stream ?

  • @leojohn6702
    @leojohn6702 Рік тому

    Btw. Is http3 available for nodejs?

  • @ttrss
    @ttrss Рік тому

    so webtransport over http/3 is like UDP -> QUIC -> UDP again?

    • @thatryanp
      @thatryanp 9 місяців тому +1

      WebTransport appears to offer any connection format you would want (uni, bi, unreliable). So: UDP -> QUIC -> (HTTP | WebSockets | UDP-like)

  • @Alexithymiander
    @Alexithymiander Рік тому

    Incredibly insightful explanations.

  • @mhcbon4606
    @mhcbon4606 Рік тому

    hm. Looks good, i am intrigued by this prop of the transport "draning", I have not seen that mechanism often. I still wonder where it stops, about the networking APIs. There has been several, it is not like they did not have success, but we would not be here if something was not off.

  • @akshay-kumar-007
    @akshay-kumar-007 Рік тому

    I know I should get the answer of this by profiling, but wanted to know from all other fellow engineers here,
    Will WebTransport protocol (over HTTP/2) be ideal for a high throughput usecase (like sending the LTP of a stock or cryptocurrency)?

  • @pemessh
    @pemessh Рік тому

    As always, thank you for the amazing video.
    Just a quick naive question. :)
    How does this translate to the load on the servers?

  • @REDIDSoft
    @REDIDSoft Рік тому

    Amazing video hussein😊

  • @tmbarral664
    @tmbarral664 Рік тому

    Miyamoto ?

  • @pajeetsingh
    @pajeetsingh Рік тому

    Yes we need full new standard.

  • @emenikedaniel
    @emenikedaniel Рік тому

    I love your detailed explanation and ur vast understanding on the subject is top notch👏👏

  • @krishnaSagar69
    @krishnaSagar69 10 місяців тому

    Ezsnippet recommended your video bhai.

  • @umer.on.youtube
    @umer.on.youtube Рік тому +4

    Who said it's the best time to be a developer?? GIVE US A BREAK. Tech is going wayyyyy too fast and hot these days

    • @autohmae
      @autohmae Рік тому

      An other way to look at it, enjoy this quiet period before it moves even faster ! 🙂

  • @uchennaofoma4624
    @uchennaofoma4624 Рік тому

    Amazing video 👏. I've been sub for a long time, that's how I noticed 5hr improvement 😀

  • @jejeraojadhav5090
    @jejeraojadhav5090 Рік тому

    It resembles RSocket created at Netflix

  • @jsonkody
    @jsonkody Рік тому

    Musashi :)
    I've read it twice already.

  • @mariumbegum7325
    @mariumbegum7325 Рік тому

    Fantastic video!

  • @davepubliday6410
    @davepubliday6410 Рік тому

    Why not just use sockets. Old fashioned TCP sockets. Why all this stuff on top of it?

    • @JetpackBattle-lc7ob
      @JetpackBattle-lc7ob Рік тому

      tcp IS stuff on top.. this gives us access to the lower level udp

    • @davepubliday6410
      @davepubliday6410 Рік тому

      @@JetpackBattle-lc7ob I believe the BSD Sockets library let’s you use TCP and UDP. Perhaps I shouldn’t have been so specific citing TCP. I never completely understood why Websockets is a thing when actual sockets are available as an option, and have been a thing since the inception of the Internet.

  • @АртемСиробаба
    @АртемСиробаба Рік тому

    Sounds like R-Socket

  • @robl39
    @robl39 Рік тому +1

    Hey Hussein, I love your content but sometimes it would be nice if these were summarized into 5 minutes or less. My short attention span gets the best of me after that point. Just my unsolicited opinion and hopefully you take it with positive intent. Thanks for the content!

  • @AnasAlQudah
    @AnasAlQudah Рік тому

    الله يجزيك الخير

  • @AlayDhagia
    @AlayDhagia Рік тому

    You look like an older version of CarryMinati 😅

  • @Mohamed_jeddah
    @Mohamed_jeddah Рік тому

  • @stewiegriffin6503
    @stewiegriffin6503 Рік тому

    booooooooooooooooooooooooring

  • @mohammedabdulbary1577
    @mohammedabdulbary1577 Рік тому +1

    another amazing video ❤️❤️