What pattern is commonly used in the Data Plane of a Service Mesh?

What pattern is commonly used in the Data Plane of a Service Mesh?

• A. Init container pattern
• B. DaemonSet pattern
• C. Gateway pattern
• D. Sidecar pattern

Answer: (D)

The pattern used in the Data Plane of a Service Mesh is the sidecar pattern. In this approach, a lightweight proxy is deployed alongside each service instance in the same unit (for example, in the same pod). The proxy intercepts all inbound and outbound traffic for that service, enabling features like mutual TLS, traffic routing, retries, timeouts, load balancing, monitoring, and policy enforcement without requiring changes to the application code. This per-service proxy setup makes it easy to apply mesh capabilities consistently across all services and to manage east–west traffic within the cluster. Major meshes like Istio and Linkerd implement this model. Init containers run setup tasks before the main app starts, and DaemonSet patterns place a pod on every node for node-level agents, neither of which provide the per-service traffic interception that the sidecar pattern delivers. The gateway pattern handles ingress/egress at the edge, not the per-service data-path interception inside each service.

The pattern used in the Data Plane of a Service Mesh is the sidecar pattern. In this approach, a lightweight proxy is deployed alongside each service instance in the same unit (for example, in the same pod). The proxy intercepts all inbound and outbound traffic for that service, enabling features like mutual TLS, traffic routing, retries, timeouts, load balancing, monitoring, and policy enforcement without requiring changes to the application code. This per-service proxy setup makes it easy to apply mesh capabilities consistently across all services and to manage east–west traffic within the cluster. Major meshes like Istio and Linkerd implement this model.

Init containers run setup tasks before the main app starts, and DaemonSet patterns place a pod on every node for node-level agents, neither of which provide the per-service traffic interception that the sidecar pattern delivers. The gateway pattern handles ingress/egress at the edge, not the per-service data-path interception inside each service.