Scheduling
Scheduling is the assignment and ordering of tasks or activities over time and available resources, subject to constraints.
Data Pipelines with Apache Airflow, Second Edition
A schedule is a rule that specifies when a workflow should run.
- How it is used
- Automates DAG runs for recurring data processing instead of requiring manual triggers.
- How deep it goes
- Works through schedule parameters, catchup, and trigger-versus-interval timing; defers asset-based scheduling.
- Examples
- Uses daily website-event statistics and a midnight-UTC cron timetable with dated output files.
- What you can do after
- Operate/configure it by setting DAG dates, a timetable, and catchup to control current and historical runs.
Read how Data Pipelines with Apache Airflow, Second Edition explains scheduling →
JavaScript in Depth
The coordination of when deferred actions are eligible to execute in a runtime rather than immediately running them upon definition.
- How it is used
- Coordinates deferred JavaScript callbacks and helps explain why identical scheduling calls can produce different output across runtimes.
- How deep it goes
- Traces call-stack boundaries and queue draining through ordering puzzles, while distinguishing host implementations from language-specified behavior.
- Examples
- Uses a click handler, synchronous versus timed array callbacks, and a Node.js program run as .js and .mjs.
- What you can do after
- Diagnose/debug callback-order surprises by checking execution context, queue-draining behavior, and host-specific API semantics.
Acing the Certified Kubernetes Administrator Exam, Second Edition
The process of deploying applications to Kubernetes by assigning their pods to suitable execution resources.
- How it is used
- Deploys and places Kubernetes workloads while supporting node selection, resource allocation, configuration, and exam-oriented administration tasks.
- How deep it goes
- Defines scheduler assignment and resource checks, then works through labels and selectors; it stops short of deeper scheduler internals.
- Examples
- Demonstrates labeling kind-worker as disktype=ssd, selecting it in pod YAML, and verifying the running pod with kubectl output.
- What you can do after
- Operate/configure pod placement by labeling nodes, editing YAML selectors, applying workloads, and verifying their assigned nodes.
Read how Acing the Certified Kubernetes Administrator Exam, Second Edition explains scheduling →
Kubernetes in Action, Second Edition
Scheduling is the process of selecting suitable compute nodes on which workloads should run.
- How it is used
- Places application pods on worker nodes so Kubernetes can run and maintain containerized workloads.
- How deep it goes
- Explains pod assignment, Kubelet reaction, image startup, and replacement behavior without detailing node-selection rules.
- Examples
- Uses a kubectl deployment, Pending pod output, scheduling events, image pulling, container creation, and startup.
- What you can do after
- Operate scheduling indirectly by creating a deployment and inspecting pod status and scheduling events with kubectl.
Read how Kubernetes in Action, Second Edition explains scheduling →
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
A timeline is a chronological visual arrangement of domain events that represents the sequence of activities or occurrences in a business domain.
- How it is used
- Uses a chronological event arrangement to help groups map business knowledge, tell an end-to-end story, and identify conversations.
- How deep it goes
- Explains construction, sorting, walk-through, notation, and chunking, while deliberately avoiding rigid precision about domain boundaries.
- Examples
- Uses business events, seeded whitespace, hot spots, terminology notes, and grouped event sequences as concrete artifacts.
- What you can do after
- Apply it via EventStorming to map a business process, surface uncertainty, and compare possible domain or subdomain groupings.
D3.js in Action, Third Edition
A timeline is a visual representation that arranges events or measurements along an ordered temporal dimension.
- How it is used
- Uses timelines to explore how events, measurements, and related categories change across periods.
- How deep it goes
- Explains data classification, visual encodings, D3 axes, and brushing, but stops short of a complete timeline implementation.
- Examples
- Demonstrates Van Gogh’s paintings, drawings, letters, cities, and Nobel laureate years through timelines and selectable ranges.
- What you can do after
- Build it from scratch by mapping attributes to timeline encodings and adding D3 brushing to filter a selected time range.
Read how D3.js in Action, Third Edition explains scheduling →
Also covered in
- Grokking Simplicity
- Collaborative Software Design: How to facilitate domain modeling decisions
- Bug BashIn early access (MEAP)
- Claude at WorkIn early access (MEAP)
- Software Engineering for Data ScientistsIn early access (MEAP)
- Practical Automation with PowerShell: Effective scripting from the console to the cloud
- Acing the CCNA Exam: Volume 2 Advanced Networking and Security
- Interview Speak
- Lead Developer Career Guide
- Build and Orchestrator in Go (From Scratch)
- ASP.NET Core in Action, 3e
- Designing Deep Learning Systems: A guide for software engineers
What to know first
- pipelineA pipeline is an ordered sequence of connected processing stages through which data or work flows, with each stage passing or transforming its output for subsequent stages.
- asynchronous programmingAsynchronous programming structures operations so that the initiating execution can continue or yield control without synchronously waiting for each operation to complete.
- generationGeneration is the production of an output by a computational model from supplied input or context, often using patterns learned from data.
- threadA thread is a distinct sequence of execution with its own control flow and state, managed or scheduled by a processor, runtime, or operating system.
Related concepts
- fair-share schedulingincludes · Fair-share scheduling is an operating-system scheduling algorithm that distributes CPU usage among users or groups rather than equally among individual processes.
- gang schedulingincludes · Gang scheduling starts or schedules a group of cooperating workers together so they are simultaneously available for coordinated computation or communication.
- production schedulingincludes · Production scheduling is the assignment and sequencing of production jobs across resources and time subject to operational constraints.
- ant colony optimizationaddressed by · Ant colony optimization is a population-based probabilistic optimization technique in which artificial agents use simulated pheromone trails to guide the search for good solutions.
Questions about scheduling
What is scheduling?
Scheduling is the assignment and ordering of tasks or activities over time and available resources, subject to constraints.
Which Manning books explain scheduling?
Data Pipelines with Apache Airflow, Second Edition, JavaScript in Depth, Acing the Certified Kubernetes Administrator Exam, Second Edition, Kubernetes in Action, Second Edition, Architecture Modernization: Socio-technical alignment of software, strategy, and structure and D3.js in Action, Third Edition.
What should I know before learning scheduling?
Manning books that teach scheduling usually introduce pipeline, asynchronous programming, generation and thread first.
What kinds of scheduling are there?
Kinds of scheduling include fair-share scheduling, first-come first-served scheduling, gang scheduling, production scheduling and weighted scheduling.
What is scheduling also called?
Scheduling is also called schedule.
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.





