liveBook · Manning

Executor

An executor is a software component or abstraction that accepts tasks and arranges for them to run in an execution environment.

How 3 Manning books explain it

Data Pipelines with Apache Airflow, Second Edition

An Airflow executor is an execution framework component that determines how workflow tasks are dispatched and run by workers.

How it is used
Determines how queued Airflow tasks are dispatched to workers in a production deployment.
How deep it goes
Explains the scheduler handoff, compares executor trade-offs, and gives configuration and installation checks without detailing every installation approach.
Examples
Uses an executor configuration setting, a task-level BashOperator selection, and a mixed-executor deployment with different task images.
What you can do after
Operate/configure it by choosing an executor for the workload, setting its configuration, and checking that a DAG task reaches running.

Read how Data Pipelines with Apache Airflow, Second Edition explains executor →

Rust Servers, Services, and Apps

The Tokio executor is the Tokio runtime component that drives futures toward completion by polling them when they can make progress.

How it is used
Drives spawned and awaited Tokio futures by polling them until they produce results.
How deep it goes
Works through polling, pending results, waking, and a custom timer; treats pinning as a requirement rather than explaining it fully.
Examples
Uses spawned file-reading tasks, a future that stays pending, and an expiration timer that wakes its task.
What you can do after
Evaluate/understand it: trace why a Tokio task remains pending, gets polled again, or completes.

Read how Rust Servers, Services, and Apps explains executor →

Fast Python: High performance techniques for large datasets

How it is used
Coordinates coroutine scheduling or thread-backed map/reduce work, depending on the execution model.
How deep it goes
Demonstrates yielding, blocking map, futures, and progress callbacks; notes that worker tuning remains opaque in `concurrent.futures`.
Examples
Uses network listening with disk writes and a Python word-count MapReduce workload.
What you can do after
Apply `asyncio` scheduling or `concurrent.futures` thread pools to coordinate I/O or map/reduce tasks.

Read how Fast Python: High performance techniques for large datasets explains executor →

Also covered in

What to know first

Related concepts

Questions about executor

What is executor?

An executor is a software component or abstraction that accepts tasks and arranges for them to run in an execution environment.

Which Manning books explain executor?

Data Pipelines with Apache Airflow, Second Edition, Rust Servers, Services, and Apps and Fast Python: High performance techniques for large datasets.

What should I know before learning executor?

Manning books that teach executor usually introduce thread, future, multiprocessing and multithreading first.

What kinds of executor are there?

Kinds of executor include ExecutorService.

What is executor part of?

Executor is part of async runtime. An async runtime is software that schedules asynchronous tasks and drives their suspended computations toward completion.

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.