Worker Pool Pattern

A worker pool launches a fixed number of goroutines that all pull jobs from a shared channel. Instead of spawning one goroutine per task, you spawn N workers and feed them work.

• Bounds the number of concurrent operations
• Reuses goroutines instead of creating thousands
• Protects shared resources like databases or APIs

Unbounded goroutines can exhaust memory, file descriptors, or overwhelm a downstream service. A pool gives you a knob to control how much work runs at once.

If you have 10000 URLs to fetch, you do not want 10000 simultaneous HTTP requests. A pool of 20 workers keeps it sane.