golang context package explained: the package that changed concurrency forever

Поделиться
HTML-код
  • Опубликовано: 9 мар 2024
  • In this video we go over a visualization of how the context package works in golang.
    Golang Microservices Full Course!:
    kantan-coding.teachable.com/p...
    ► Join my Discord community 👉 / discord

Комментарии • 38

  • @kantancoding
    @kantancoding  Месяц назад

    🌟 Hey devs! 🌟 Ready to level up your coding game? Check out this awesome course on Microservices using Go! 🚀 From beginner to pro, learn to build scalable apps with ease. Don't miss out! Enroll now 👉 kantan-coding.teachable.com/p/early-bird-special-pricing
    #GoLang #Microservices #CodeWithConfidence 🔥🎉

  • @user-tw8wb1id3l
    @user-tw8wb1id3l 2 месяца назад

    Thanks mate. I've enjoyed your video series on concurrency in GO. Nice and clear explanation. Very helpful. Keep on the good work.

    • @kantancoding
      @kantancoding  2 месяца назад

      Hey! Thanks for the encouragement. I’m glad you enjoyed it 😊

  • @folklinoff
    @folklinoff 2 месяца назад

    Amazingly structured comprehensive video! Thank you very much

    • @kantancoding
      @kantancoding  2 месяца назад

      Thank you! Happy to help 😊

  • @defnd3r
    @defnd3r 2 месяца назад +1

    Glad you're back to making Go videos man... They're super useful

  • @sinahassani9880
    @sinahassani9880 25 дней назад

    This explanation is worth paying time for

    • @kantancoding
      @kantancoding  10 дней назад

      Thank you! I’m glad it helped 🙂

  • @brandon_wallace
    @brandon_wallace 2 месяца назад

    Excellent!

  • @ShadwTrooper
    @ShadwTrooper Месяц назад

    Super helpful. Thanks!

  • @marioluigi2995
    @marioluigi2995 2 месяца назад +1

    hey man, welcome back, I'll watch your vid.

    • @kantancoding
      @kantancoding  2 месяца назад

      Thank you for watching! More to come 😊

  • @LeviElekes
    @LeviElekes 2 месяца назад

    🙏

  • @aamirshekh934
    @aamirshekh934 Месяц назад

    can you do a video on ticker package and go sarama package. Both of them doesn't have any good resources on youtube.

    • @kantancoding
      @kantancoding  Месяц назад

      not sure at the moment but I will keep it in mind! ☺️

  • @user-pc7bv8vk4p
    @user-pc7bv8vk4p 2 месяца назад +1

    Sir upload go tutorial for beginners

    • @kantancoding
      @kantancoding  2 месяца назад

      Hmm I have quite a few geared towards beginners. Is there anything specific you want to see?

    • @user-pc7bv8vk4p
      @user-pc7bv8vk4p 2 месяца назад

      @@kantancoding yes, I am beginner in programming. Golang is my first programming language

    • @kantancoding
      @kantancoding  2 месяца назад +1

      Introduction to Programming Using Go
      ruclips.net/video/08Blkpo1F8I/видео.html

  • @Porumb007
    @Porumb007 16 дней назад

    Good explanation. Do you really need to duplicate the code for ctx cancel handling? Can't you have it in a separate function? Your function naming in the example is kind of bad.

  • @stupidfilip23
    @stupidfilip23 2 месяца назад

    hiii, we missed you

  • @dawnrazor
    @dawnrazor 14 дней назад

    Great video, but what happens when you DO want to cancel a parent context from a child. I have this exact scenario and in this case I pass in the parents cancel to the child gr. this works fine but this seems to be going against the grain. How do you cancel the parent without passing cancel func? What is wrong with this?

    • @kantancoding
      @kantancoding  14 дней назад +1

      I can’t think of any valid scenario where you’d cancel the parent from a child goroutine. I’d say the fact that you want/need to do this points out a fundamental design flaw in your application.
      I can help more if you tell me WHY you feel it is necessary to cancel the parent from the child.

    • @dawnrazor
      @dawnrazor 13 дней назад

      @@kantancoding great thanks. I knew it was wrong but I couldn’t figure out how to fix it properly. I have designed a worker pool. The worker pool exposes an optional output channel that the client can read from for results. But if the client doesn’t define a consumer for the channel, then the pool will lockup. So I decided to introduce a feature that would timeout and allow the pool exit gracefully. I do this by allowing the worker to cancel the parent context so the whole pool including other workers to exit gracefully. Only the worker knows when the timeout occurs not the parent. How can I fix this? (gh/snivilised/lorax/boost/issues/68)

    • @kantancoding
      @kantancoding  13 дней назад

      @@dawnrazorif you’re just using a timeout mechanism, just set the timeout in the context that you pass from the parent to the children using WithTimeout() (I explained how to use it in the video). Hope that helps!

    • @dawnrazor
      @dawnrazor 12 дней назад

      @@kantancoding hi again, actually I don’t think your approach will work and the reason is this. The worker is running a task and there is no way to know how long the task will take. So what value do you set for the timeout in the parent context. There is no sensible value that you could come up with. And besides, the timer should only start at the point when the worker has attempted to sent to the output channel. Am I wrong about this?

    • @dawnrazor
      @dawnrazor 7 дней назад +1

      @@kantancoding just wanna say thanks for making me realise that trying to cancel a parent from a child was totally wrong. I’m junking my entire worker pool and starting again with a better design

  • @NigelTatschner
    @NigelTatschner Месяц назад

    You alllll get a context 😂

  • @rishirajrao5337
    @rishirajrao5337 8 дней назад

    Honest feedback, it was bit verbose and was lacking clarity unlike other tutorials. Thanks anyway for the effort.