► Join my Discord community for free education 👉 discord.com/invite/bDy8t4b3Rz ► Become a Patreon for exclusive tutorials👉 www.patreon.com/anthonygg_ Thanks for watching

Context is like a bag or container that holds information that is shared between different parts of the program, especially when it comes to handling a request. This information can include things like timeouts, cancellation signals, and other data that is specific to that request. For example, imagine you are building a web server that handles a lot of incoming requests. Each request has its own specific needs and requirements, such as a deadline for how long it should take to complete. The context allows you to keep track of these individual requirements for each request, and make sure that they are handled properly.

I've been putting off learning context because of its strange nature. You've cleared it up in 17 minutes, thank you.

You don't actually need the for loop for the select. Since you don't have a default case, the select with just block until a response is received or the context is canceled.

I like how you're providing almost real life examples with such a passion! Your videos helped me A LOT!

I have just started learning Go, there are lots of vids with basics but this sort of content gives you a good taste of what you actually should learn to become a good golang dev. Thanks a lot for your hard work!

Keep the content coming man, following along the JSON API series to write my own project has helped me learn Go so fast its unreal

Simplest and Effective Tutorial for Golang Context package! Thank you so much!!

Great video, thanks so much! As for your remark about what language can do this so cleanly, I think C#'s CancellationToken implementation is as clean, or perhaps even cleaner as it can be passed to any task, and the cancellation token expiring can be handled by catching the exception thrown, which realistically is the only code you'd need to implement to get the equivalent of this code in Go.

Thanks Anthony your videos from last few days are helping a lot man. 🍻

Surely the best explanation of contexts I've ever seen, thx

The function fetchData alone is a perfect description of why Go is such a beautiful language and how much effort it actually takes away from you. Image, you would have to code all of these implicit functionalities (including something complex like coroutines, thread communication and sync) by yourself or take them from some repo and try to incorporate it into your project, in C++ for instance. Here, you get all of that, wrapped up in a nice syntax that it easy to understand and follow. :)

you are simply the best teacher i could ever have

Your channel is pure Gold! Thanks for sharing your knowledge with the world!

amazing video. I would love to see more about tracing, loging and grafana

Great video. Thanks Anthony!

Please note that the go-routine will not be cancelled, but will run until it's ended naturally (or the program exits). This is default Go behavior and as far as I know there's no way to cancel it from outside the go-routine.

Literally the best explanation

Why for-select instead of only select?

Anyone reading this: This is *exactly* what we do in my company. So if you are looking for stuff to learn to get hired, this is one of those things!

Appreciate your content! Thanks so much!

Great Video. Loving your content.

Dude, that last application of a request ID in a context is the exact project I’m working on for work but in typescript. I wish we were making our APIs in GO but sadly not. I’ve been using a Axios wrapper inside a library I made and then in the request middleware I add the axios wrapper to an inversify config for dependencies injection. That way when ever a developer uses the axios wrapper in our code, all the classes have my axios wrapper with the request id as a public read only property. GO would be so much better

New to go. I didn't know about context and ended up making a struct to implement a shared state...

Keep the videos coming!👏👏

the best context tutorial I've ever seen!

Beautiful video, thanks!

Thank you for your help! U r making a great job!

very nice tutorial for who want starts golang. beautiful...

Very useful! Thanks! :)

next time you can consider using fmt.Errorf("some msg: %w", ctx.Err()) So the caller can rely on the embedded standard error to figure out it was a context related error on top of having a useful error message. Although, you could do all this stuff w/t the context package (func call with a cancel signaling), especially since generics has landed. this was not the in depth discussion i was looking for, but not your fault.

WOW. Cool 🔥. Really cool 🔥. Appreciate it 🤝

you are awesome, thanks for these videos

I've been using Rust on my back end for web api / static file serving and it's great. I'm confident that after it compiles its going to run like a champ.... however, looking at how amazingly simple go code is and how beautiful concurrency is implemented I can't help thinking that I would be better off banging out web shit with Go. Rust, incredible power but as a solo dev the complexity weighs me down a bit. I feel like, from watching some of your vids I could be shipping code at light speed compared to what I'm able to do with Rust.

Great video sir❤❤❤

Hi. First I wanna say I really love your channel. Seems you really have a deep knowledge of Go. I have one question. What is the reason you give a context.Background to fetchUserData and wrap it then inside the function with the context.WithTimeout? What were your thoughts behind this design decision ? why didn't you give the timeout context directly to the fetchUserData?

Thank you for the good content

cool video on context

great vid!

thankyou this was informational

loving it

Very educative! How do you move around so fast, do you use vim bindings?

thank u Great Man

context code is explained well, but the infinite for loop is not placed well. it should be in a seperate goroutine as well

Do you still need to use context pkg if you deploy this inside a service mesh like istio, which can handle timeouts in its envoy sidecars?

what the for loop is for?

Hey Anthony, great video, but wouldn’t the fetchThirdPartyStuff function keep running in the background after fetchUserData times out and returns? I have had this happen in a very similar situation, but I used time.after instead of contexts. Would this still happen with context timeouts if the whole program ran for longer?

I dont get why you wrapped select statement in for, since you return from each select branch?

thank you, great content. you talk like T Bag from prison break 😄

amazing

Apologies if I've missed this in this video or another video of yours but I'm struggling to work out how to test something similar to this. I have a AWS Lambda function written in go that has basic GET/PUT/POST/DELETE handlers that use context. The function just read/writes to DynamoDB. My function works but I'm struggling to work out how to unit test my handlers. I likely just need to rewatch this and do more digging but if you have anything or anyone can link to some examples that might help then I'd really appreciate it.

Came for contexts, stayed for the Swiss accent :)

very good

You're a fantastic teacher, Anthony! Thanks for sharing your knowledge aways most smoothly and animatedly possible - I've learned heaps watching your videos

why infinite for loop was required ? select statement alone was sufficient. Select waits for one of the case channel operation to complete.

you are awesome

wait go is really clean af wtf

(16:00) How does one actually implement request tracing in grafana? Thinking about it, Would love a clip about integrating projects grafana / prometheus, pprof / opentelemetry etcetera :)

omg you are ao cool🤩

Do you really need the select inside a for? In this case, isn't it going to work the same way if you remove the for?

nice vids

nice

I am struggling to understand the difference between context.WithDeadline and context.WithTimeout. they essentially do the same thing right ?

🤩

Hey, thanks for videos! Can you please share your VS Code theme?

The one thing I'm confused with is why does `context.WithTimeout()` & `context.WithValue()` need the `ctx` as parameter? What is it exactly? Why does that parameter matter? And, why does `ctx` need to be initiated from the main function (instead of on the `fetchUserData` right away? I mean before you started using `context.WithValue`.

Is it possiblo to trigger a "cancel" on demand? I mean, what if you want to "cancel" a request not because the timeout, but because another arbitrary reason?

I'm not sure why the select statement needed to be ran in a for loop

Hey Athony, could you please share how you use vim in your normal stuff? I really love your speed with vim. I've used vim for about 2 months but my speed really bad. I want high speed vimmer like you 😂

Great video! Cheers from Guatemala

Can somebody explain what will happen with the goroutine? Will not it hang infinitely waiting for the response? How it will be killed?

I’m a chess player, hey, that’s not true😂😂😂

I think the for around select is extranous. You could have the same results without it

what theme?

Can somebody explain why do we need an infinite loop with select? Why not just select?

Where can I get the code?

> which language can those that, that clean? > * silence * > NONE exactly loved that part

Great video but your keyboard / navigating stresses me out.

I like how the go makes it so cluttered to implement a piece of code which does exactly what a CancellationToken would do in c# in ~6 loc

it's just a map it's really easy

boring lecture

Excellent Video, thanks @anthonygg_ really appreciate your content. I am new to Microservices and how they can be connected in Golang. Can I ask if you have any video in which you join Microservice together in one app. Something like a part 2 for "How to build and structure a go microservice"