recall

← recall

unbounded concurrency term

no limit on parallel work, can exhaust resources

When you spin up goroutines/threads/workers without a cap, a burst of work can saturate CPU, exhaust memory, or hammer downstream connection pools. Always bound concurrency with a semaphore, worker pool, or queue.

aliases: no concurrency limit, uncapped parallelism

topics: concurrency, failure-modes

references: