go-context

context.Context carries security credentials, tracing information, deadlines, and cancellation signals across API and process boundaries. Go programs pass contexts explicitly along the entire function call chain. Based on Go Wiki CodeReviewComments - Contexts . Functions that use a Context should accept it as their first parameter : This is a strong convention in Go that makes context flow visible and consistent across codebases. Do not add a Context member to a struct type. Instead, pass ctx as a parameter to each method that needs it: Exception : Methods whose signature must match an interface in the standard library or a third-party library may need to work around this. Do not create custom Context types or use interfaces other than context.Context in function signatures: If you have application data to pass around, consider these options in order of preference: Context values are appropriate for: Context values are not appropriate for: Contexts are immutable. It's safe to pass the same ctx to multiple calls that share the same deadline, cancellation signal, credentials, and parent trace: Use context.Background() only for functions that are never request-specific : Default to passing a Context even if you think you don't need to.