Thread pool

As explained in Go in Action, Second Edition

A thread pool is a managed collection of reusable worker threads that execute submitted tasks.

A thread pool, called a worker pool in Go, processes many independent tasks concurrently while limiting parallelism. Fixed worker goroutines pull jobs from a shared channel, distributing bursts of work without exhausting resources. section 9.5

Model the pool as a queue and a set of workers. Each worker loops over the shared channel, performs the task, and waits for the next job; the pool exposes submission and shutdown operations. section 9.5.1

Feed-ingestion worker pool

A feed-ingestion service can create a buffered queue, start three workers, and submit feed URLs through Submit. Each worker fetches URLs with a 30-second context timeout. Closing the queue through Stop lets workers exit cleanly, while embedding the pool in App keeps submission separate from execution. section 9.5.1

Figure 9.2 Worker pools ingest incoming messages across multiple processes.

Visualizes workers consuming incoming messages across processes, clarifying how queued work is distributed. section 9.5.1

How Go in Action, Second Edition covers it

How deep it goes

Implements workers, a buffered shared channel, configurable pool size, submission, application integration, and shutdown.

Examples

Uses feed URLs, a buffered queue, three workers, timed feed fetching, an App-owned pool, and explicit Stop shutdown.

What it assumes

Assumes familiarity with Go concurrency, especially goroutines and channels, while applying them to queued work and controlled parallelism.

What you can do after

Build it from scratch using Go goroutines, channels, configurable workers, context timeouts, and explicit channel closure.

How it connects

Connects goroutines and channels with context.Context, pipelines, fan-in/fan-out, cancellation, error handling, and race detection.

liveBookmanning.com

Read Go in Action, Second Edition on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Python Concurrency with asyncioA thread pool executor is an execution service that runs submitted callables using a reusable pool of worker threads.
• 

  liveBookmanning.com
  C++ Concurrency in Action, Second EditionA thread pool is a managed collection of reusable threads that execute submitted tasks.
• 

  liveBookmanning.com
  Functional Programming in Scala, Second EditionA thread pool is a managed set of reusable worker threads that execute submitted tasks, optionally with a fixed maximum size.
• 

  liveBookmanning.com
  Functional Design and Architecture: Examples in HaskellA thread pool is a managed collection of reusable worker threads whose size limits concurrent thread execution.
• 

  liveBookmanning.com
  Grokking ConcurrencyA thread pool is a concurrency pattern that maintains a collection of reusable worker threads and assigns submitted tasks to available threads.
• 

  liveBookmanning.com
  Starting Data Analytics with Generative AI and PythonThreadPoolExecutor is a Python concurrency component that manages a pool of worker threads for executing callable tasks.
• 

  liveBookmanning.com
  100 Go Mistakes and How to Avoid ThemA worker pool is a concurrency pattern that runs a fixed number of worker goroutines to process shared work or communicate through a common channel.
• 

  liveBookmanning.com
  .NET in Action, Second EditionA thread pool is a managed collection of reusable worker threads that execute queued work items.
• 

  liveBookmanning.com
  Clojure: The Essential ReferenceA thread pool is a set of reusable worker threads managed to execute multiple tasks without creating a new thread for each task.

Compare how 10 books explain thread pool →

Related concepts

• std::functionuses · std::function is a C++ standard-library class template that stores and invokes callable objects compatible with a specified function signature.
• std::thread::hardware_concurrencyuses · A C++ standard library function that returns a hint about the number of hardware threads available for concurrent execution.

This explainer was generated by Manning's knowledge graph from the text of Go in Action, Second Edition. The section links point to the parts of the book it draws on.