liveBook · Manning

Data plane

A data plane is the part of a networked or distributed system that executes workloads and carries or processes application data and traffic.

How 5 Manning books explain it

Acing the CCNA Exam: Volume 2 Advanced Networking and Security

The data plane is the part of a network system that forwards packets or frames according to programmed forwarding decisions.

How it is used
Classifies functions that directly receive, process, and forward network packets or frames.
How deep it goes
Explains forwarding behavior and representative switch functions, but does not detail hardware implementation or command configuration.
Examples
Uses MAC-based frame forwarding, security filtering, 802.1Q tagging, routing-table instructions, and SDN controller directives.
What you can do after
Evaluate which network-device functions directly forward messages and distinguish them from control or management responsibilities.

Read how Acing the CCNA Exam: Volume 2 Advanced Networking and Security explains data plane →

Azure Security

The Azure data plane is the layer through which applications and users access or manipulate the capabilities and data managed by Azure resources.

How it is used
Separates Azure resource management from data and capability access when assigning permissions and reviewing logs.
How deep it goes
Defines the plane distinction through RBAC properties, logging locations, and storage and VM examples without enumerating individual data permissions.
Examples
Contrasts viewing a storage account with reading its data, creating a VM with connecting through RDP, and creating accounts with reading blobs.
What you can do after
Apply it via Azure RBAC properties and resource logs to separate data access from management permissions and audit trails.

Read how Azure Security explains data plane →

Designing AI Systems

A data plane is the part of a distributed system that processes application requests and carries out runtime operations.

How it is used
Handles application requests and runtime operations inside workflow containers, while deployment and scaling remain outside the request path.
How deep it goes
Explains container placement, request modes, tracing, concurrency, retries, and service calls, but defers deployment management to the control plane.
Examples
Demonstrates synchronous, streaming, and asynchronous responses plus a fan-out/fan-in research workflow using parallel child workflows.
What you can do after
Operate request handling with runtime servers, response modes, retries, tracing, concurrency isolation, and horizontally scalable workflow containers.

Read how Designing AI Systems explains data plane →

Kubernetes in Action, Second Edition

The workload plane is the collection of worker resources on which applications run in a cluster.

How it is used
Explains where Kubernetes workloads run after the cluster is divided into control plane and worker nodes.
How deep it goes
Defines the plane, its node membership, and deployment behavior while deferring component internals to later treatment.
Examples
Uses cluster diagrams and the scenario of deploying an application without selecting its worker node.
What you can do after
Operate Kubernetes deployments as a shared worker-node resource without coupling applications to individual machines.

Read how Kubernetes in Action, Second Edition explains data plane →

Cloud Observability in Action

The data plane is the set of worker resources that execute application workloads and carry operational traffic in a distributed system.

How it is used
Organizes Kubernetes worker components that execute, monitor, report, and terminate application workloads.
How deep it goes
Explains workload responsibilities and observability implications, but stops short of detailing individual worker components.
Examples
Uses frontend container logs, kubectl logs, API-server metrics, and a Kubernetes signal-source architecture figure.
What you can do after
Operate/configure it by identifying workload signals and planning their collection, routing, storage, and querying.

Read how Cloud Observability in Action explains data plane →

Also covered in

What to know first

Related concepts

Questions about data plane

What is data plane?

A data plane is the part of a networked or distributed system that executes workloads and carries or processes application data and traffic.

Which Manning books explain data plane?

Acing the CCNA Exam: Volume 2 Advanced Networking and Security, Azure Security, Designing AI Systems, Kubernetes in Action, Second Edition and Cloud Observability in Action.

What should I know before learning data plane?

Manning books that teach data plane usually introduce replica and worker first.

What is the difference between data plane and control plane?

A data plane is the part of a networked or distributed system that executes workloads and carries or processes application data and traffic. A control plane is the management and coordination part of a system that governs the configuration, policies, state, and operations of its components and resources.

What is data plane part of?

Data plane is part of service mesh. A service mesh is an infrastructure layer that manages communication between distributed services and commonly provides traffic control, security, and observability.

What are the parts of data plane?

Data plane includes Kubernetes worker node.

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.