If you are looking to implement these for production-level applications then it's worthwhile having a look at the following articles: The acme of foolishness - by Dave Cheney dave.cheney.net/2016/12/22/never-start-a-goroutine-without-knowing-how-it-will-stop Thread Pooling in Go Programming - by Bill Kennedy www.ardanlabs.com/blog/2013/05/thread-pooling-in-go-programming.html These were recommended by www.reddit.com/user/Cazineer/ on Reddit 🙏
@NunoLopes993 жыл бұрын
Very simple and clear explanation! 👏👏👏
@Tutorialedge3 жыл бұрын
Welcome Gophers 👋 This video on constructing Worker Pools in Go has been taken directly from my new course - The Beginner's Guide to Go - tutorialedge.net/courses/go-beginners-guide/ If you want support learning Go, then feel free to join the TutorialEdge clan and join us on the Discord server where you can gain access to real-time support!
@redcokes Жыл бұрын
Thank you for tutorial!
@RN-er7mz3 жыл бұрын
Thanks for the video
@wisdommatthew67753 жыл бұрын
Awesome tutorial 🥰🥰🥰
@vamsikrishnasiddu35252 жыл бұрын
Nice Explanation of worker pool. you can range over the results channel to receive the output instead of using for loop
@devinsomnia3663 жыл бұрын
Welcome back \o/
@aqilisayev55293 жыл бұрын
Thanks for great explanation!
@Tutorialedge3 жыл бұрын
Absolutely! I'm glad you liked it!
@vic_shine3 жыл бұрын
Thanks for the video! But, which thing in a real life project can solve this solution? Please more explain this for full picture 🖼️
@halfi3 жыл бұрын
You have deadlock here. You write to bufferized chan jobs, which write to the result chan. When both of buffers will be filled, it will cause of the deadlock. You could try just add more than 6 urls and get deadlock. You shouldn't read to the jobs chan and read from the results chan in one thread.
@MuhammadIsmail-bi8ld2 жыл бұрын
After experiencing it my self, the quick workaround it actually wrap lines 49-52 with an anonymous go func() So it becomes: ``` go func() { for _, url := range urls { jobs
@fffsjkfbrutireer11 ай бұрын
Forgot close body after http call, it makes memory leaks
@kccccccccccccccc0904 Жыл бұрын
Why did you loop over the results channel like that? Couldn’t you have just ranged over the channel itself?