Worker
A worker is a person or computational execution unit assigned to perform a task as part of a larger system or activity.
Build and Orchestrator in Go (From Scratch)
A worker is a machine or node in an orchestration system that executes assigned application tasks or jobs.
- How it is used
- Executes manager-assigned application tasks as containers while reporting local task and machine information for orchestration.
- How deep it goes
- Builds a worker from a stateful skeleton through queue processing, task transitions, Docker delegation, metrics, and failure behavior.
- Examples
- Demonstrates a Go worker starting and stopping a strm/helloworld-http container task and running multiple web-server instances across workers.
- What you can do after
- Build it from scratch as a Go worker that queues tasks, transitions their states, and starts or stops Docker containers.
Read how Build and Orchestrator in Go (From Scratch) explains worker →
ASP.NET Core in Action, 3e
A worker service is a headless .NET application whose primary function is to run hosted background tasks rather than serve user-facing web endpoints.
- How it is used
- Runs background jobs without web endpoints, including scheduled processing and event handling.
- How deep it goes
- Walks through template setup, hosted-service registration, shutdown-aware execution, production hosting, and scaling tradeoffs.
- Examples
- Uses a once-per-second logging loop and a service that saves exchange rates with an HTTP client and EF Core.
- What you can do after
- Build it from scratch with `dotnet new worker`, register a hosted task, and prepare it for operating-system service hosting.
Data Pipelines with Apache Airflow, Second Edition
An Edge Worker is a worker process that registers with an Airflow API server and executes tasks assigned to it remotely.
- How it is used
- Executes scheduled DAG tasks, including tasks assigned to a remote environment through EdgeExecutor.
- How deep it goes
- Explains task pickup and Edge Worker registration, assignment, completion, and configuration, but not worker-process internals.
- Examples
- Uses on-premises and Kubernetes-cluster jobs, an executor-specific task override, and a worker-status CLI command.
- What you can do after
- Operate/configure an Edge Worker for remote task execution and inspect its status with the Airflow CLI.
Read how Data Pipelines with Apache Airflow, Second Edition explains worker →
Kubernetes for Developers
A worker Pod is a workload instance that performs units of work assigned by a coordinator.
- How it is used
- Runs continuously to take queued tasks that a web application cannot complete inline.
- How deep it goes
- Works through a Redis-backed worker loop, Deployment, replica tradeoff, and CPU autoscaling; does not show a separate result store.
- Examples
- Uses two Python Pods that calculate pi from Redis tasks, plus a 36-worker comparison of internal concurrency and replicas.
- What you can do after
- Build it from scratch as a Redis-backed worker Deployment, then operate and scale its Pods with Kubernetes.
Elixir in Action, Third Edition
A worker process is a supervised process that performs part of a service's operational work rather than organizing other processes.
- How it is used
- Handles service operations or independent requests while supervisors manage worker life cycles.
- How deep it goes
- Defines workers, demonstrates spawned request handlers, and places them in supervision trees; it stops short of exhaustive process internals.
- Examples
- Uses Todo.DatabaseWorker, to-do cache and server processes, and spawned file-read and file-write handlers.
- What you can do after
- Operate/configure concurrent services by separating work into workers and placing restart boundaries under supervisors.
Distributed Machine Learning Patterns
A machine or execution unit that processes assigned data and participates in distributed model training.
- How it is used
- Accelerates distributed training and batch processing by assigning independent data partitions or work items to parallel execution units.
- How deep it goes
- Explains partition consumption, gradient calculation, asynchronous operation, and parameter-server contention without specifying implementation APIs.
- Examples
- Uses partitioned training, grayscale image work queues, LeNet training, and Fashion-MNIST worker-only training architectures.
- What you can do after
- Evaluate worker parallelism against gradient conflicts, stale parameters, communication blocking, and the worker-to-parameter-server ratio.
Read how Distributed Machine Learning Patterns explains worker →
AI Agents in Action, Second Edition
A worker agent is an agent specialized in performing delegated tasks or a defined set of tools for an orchestrator.
- How it is used
- Delegates bounded subtasks to specialist agents while an orchestrator coordinates the overall goal.
- How deep it goes
- Explains worker roles, control boundaries, and an adaptive delegation loop, with typed decisions and an implementation exercise.
- Examples
- Uses research and analysis workers, a solar-versus-wind comparison exercise, and a deep-research planner with specialized workers.
- What you can do after
- Build it from scratch: define specialized workers and an orchestrator loop that delegates, evaluates results, and can revise its plan.
Read how AI Agents in Action, Second Edition explains worker →
Amazon Web Services in Action, Third Edition: An in-depth guide to AWS
A worker is a background process that consumes tasks or messages and performs processing independently of a request-serving process.
- How it is used
- Decouples request handling from slower background work through queues and independent processing.
- How deep it goes
- Explains polling, processing, acknowledgement, retries, scaling, and fault tolerance with Node.js implementations.
- Examples
- Uses website screenshots and sepia-filtered image processing as queue-driven worker examples.
- What you can do after
- Build it from scratch as a Node.js process that consumes SQS messages, processes files, updates state, and acknowledges completion.
Read how Amazon Web Services in Action, Third Edition: An in-depth guide to AWS explains worker →
Go in Action, Second Edition
A worker service is a background process that performs scheduled or queued processing independently of request-serving services.
- How it is used
- Runs feed ingestion in the background so request-serving APIs remain responsive and decoupled from slow external providers.
- How deep it goes
- Defines single workers, buffered shared queues, configurable pools, submission, shutdown, and process-level operation.
- Examples
- Uses RSS feed URLs, NYT and BBC ingestion, a three-worker pool, periodic fetching, and terminal-based worker/API integration.
- What you can do after
- Operate a background Go worker, scale it with a configurable pool, submit queued work, and integrate it with an API.
Related concepts
- queueuses · A queue is an ordered collection that holds items for retrieval or processing, typically removing them in the order they were added.
- agent orchestrationused by · Orchestration is the coordination and sequencing of agents, services, tasks, or components to carry out a larger workflow or objective.
- contractuses · An API contract is a specification of the operations, data, and behavioral expectations that govern interactions between software components.
- Mapuses · A map is an associative data structure that stores key-value pairs and supports retrieving values by key.
- Docker Swarm manager nodeuses · A Docker Swarm manager node coordinates the cluster, schedules services and tasks, maintains swarm state, and directs worker nodes.
- gradientproduces · A gradient is the vector of partial derivatives of a scalar function with respect to its variables, indicating its local rate and direction of change.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.