golang-concurrency

Prevent goroutine leaks by ensuring every goroutine has a clear stop path via context cancellation, done channels, or explicit shutdown logic. Structured concurrency requires checking ctx.Done() in select statements to guarantee deterministic shutdown and avoid orphaned routines.

Use singleflight in Go when you need to deduplicate thundering herd requests, preventing multiple concurrent identical calls from overwhelming a downstream resource. It suppresses duplicate in-flight calls and shares the result among all waiting callers.

Correct channel ownership in Go pipelines dictates that senders own channels and enforce direction using chan<- and <-chan. Receivers must never close data channels; instead, the sender is responsible for closing output channels safely once all sends complete.

Choose sync.Mutex or sync.RWMutex for protecting shared state, sync/atomic for simple counter or flag updates, and errgroup for managing concurrent goroutines that need bounded limits via SetLimit and synchronized error propagation.

Yes, you can use goleak in Go tests to detect goroutine leaks by verifying that all goroutines spawned during test execution exit cleanly. Adding goleak checks ensures your pipelines and fan-out/fan-in patterns maintain deterministic shutdown.

Build bounded concurrent fetchers in Go using errgroup with SetLimit to cap active worker goroutines. Ensure each fetcher respects context cancellation to achieve structured concurrency and prevent pipeline bottlenecks or resource exhaustion.