We (me and imaginary friend) currently create per each HTTP request a goroutine which spawns another group of goroutines called jobs in fan-out pattern, where each job might create several goroutines as well. We haven't noticed the case when HTTP request might be canceled, nor it's died due to TTL. So consider and check if we really need this: https://blog.golang.org/context
We (me and imaginary friend) currently create per each HTTP request a goroutine which spawns another group of goroutines called jobs in fan-out pattern, where each job might create several goroutines as well. We haven't noticed the case when HTTP request might be canceled, nor it's died due to TTL. So consider and check if we really need this: https://blog.golang.org/context