Course contentsShow
← System Design
Lesson 837 of 1,91922. Service MeshFree lesson

Service Mesh Architecture: Control vs Data Plane

Understand the separation between control plane (configuration) and data plane (traffic) in service mesh architecture.

Service Mesh Architecture: Control vs Data Plane

What you'll learn: How service meshes separate orchestration logic (control plane) from actual traffic handling (data plane).

The Two-Plane Architecture

A service mesh divides responsibilities into two distinct planes that work together but serve different purposes:

The data plane consists of the sidecar proxies deployed alongside each service instance. These proxies handle the actual network traffic—intercepting every request and response, applying routing rules, collecting metrics, and enforcing policies. Think of them as the workers on the factory floor, directly touching every package that flows through.

The control plane is the brain of the mesh. It manages configuration, service discovery, certificate distribution, and policy definitions. It tells the data plane what to do, but doesn't handle traffic itself. Using our factory analogy, it's the management system that configures conveyor belts and instructs workers, but never touches packages directly.

How They Interact

When you define a routing rule or timeout policy, you configure it through the control plane. The control plane then pushes this configuration to all relevant sidecar proxies in the data plane. The proxies apply these rules to live traffic without the control plane being in the request path.

This separation is crucial: if the control plane temporarily fails, traffic continues flowing through the data plane using its last-known configuration. Only configuration changes are blocked.

Why This Matters

This architecture enables scalability—the data plane scales with your services while the control plane scales independently based on configuration change frequency. It also provides flexibility: you can upgrade control plane logic without touching running traffic, and vice versa.

Key Takeaway: The control plane configures how traffic should flow; the data plane actually flows it—keeping configuration management separate from performance-critical request handling.