context.WithTimeout(parent, d) returns a derived context that auto-cancels after d, plus a cancel function you should defer even if the timeout fires first (it releases internal resources). The callee blocks in a select waiting for either work to complete or ctx.Done() to close, returning ctx.Err() (context.DeadlineExceeded or context.Canceled) on timeout. This pattern is what every Go HTTP client, database driver, and gRPC stub already implements internally; threading the context through your own functions lets callers tighten or extend the deadline without changing your code.

Long-running worker goroutines should always check ctx.Done() so callers can shut them down without leaking. context.WithCancel(parent) gives you a context plus a cancel() function you call when shutdown is desired; closing the context's done channel signals every selecting goroutine. Pair this with the worker-pool pattern: pass the same context into every worker, and a single cancel() call drains all of them. Always return promptly from ctx.Done(); if you need to flush state, do so before returning, but do not start new long operations after cancellation.

context.WithValue(parent, key, value) attaches a key/value pair to the context, propagated to every derived context. Use this for request-scoped metadata that genuinely should travel with the request (request id, correlation id, trace span); do NOT use it for optional function arguments. Always declare a private key type (type ctxKey string) so external packages cannot accidentally collide with your key. The lookup form is ctx.Value(key).(string) with a comma-ok type assertion since the underlying value is interface{}. Keep the value tree shallow: every layer of WithValue allocates a new wrapper and slows lookups.