golang-context

To stop goroutines on client disconnect, pass r.Context() from the HTTP handler through your service and repository layers. This propagates cancellation signals automatically, ensuring downstream database calls stop executing when the client connection drops.

Use context.WithTimeout when you need to cancel operations after a specific duration, and context.WithDeadline when targeting an absolute time. Both ensure that resource-intensive Go routines terminate reliably, preventing leaks when calls exceed expected timeframes.

The best way to pass request-scoped metadata is by using unexported keys for context values. This prevents key collisions across packages and ensures that metadata is carried safely without violating the idiomatic rule of avoiding storing context in structs.

Goroutine leaks during context cancellation usually occur when contexts are not propagated correctly or stored in structs. Apply context variants like WithCancel and WithoutCancel properly across HTTP handlers and services to ensure cancellation signals reach all routines.

Yes, you can use context.WithoutCancel in Go to detach an operation from its parent context. This allows background tasks to continue running independently even after the originating HTTP request or parent process has been canceled or timed out.

Yes, Golang context works with database calls by enforcing timeouts and cancellation. Use the proper context variants like QueryContext and ExecContext instead of standard methods to ensure queries terminate immediately when a context deadline exceeds or cancels.