liveBook · Manning

Service mesh

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

How 7 Manning books explain it

Effective Platform Engineering

A service mesh is an infrastructure layer that manages communication, routing, security, and observability between application services.

How it is used
Standardizes microservice communication policies and supports a self-service ingress pattern in an engineering platform.
How deep it goes
Explains proxy behavior and placement trade-offs, then demonstrates Istio deployment and ingress configuration; it does not detail proxy internals.
Examples
Uses token validation, connection retries, encrypted proxy traffic, and an HTTPS request routed through an Istio VirtualService.
What you can do after
Apply it via Istio to configure application ingress and verify an HTTPS route with a functional test.

Read how Effective Platform Engineering explains service mesh →

Authorization in Action

A service mesh is an infrastructure layer that manages communication among microservices, including routing, load balancing, discovery, security, and observability.

How it is used
Places authorization enforcement at internal service hops that may bypass an API gateway.
How deep it goes
Explains sidecar traffic interception and traces identity, request context, policy evaluation, and forwarding through a worked authorization flow.
Examples
Uses a document-indexing request to demonstrate allowing ordinary documents while denying documents labeled Legal.
What you can do after
Evaluate service-mesh sidecars alongside gateway and per-service proxy enforcement for distributed APIs.

Read how Authorization in Action explains service mesh →

Software Security for Developers

A service mesh is an infrastructure layer that manages communication between distributed services, commonly providing traffic control, observability, and security.

How it is used
Secures internal microservice communication by centralizing mTLS, service identity checks, and baseline authorization outside application code.
How deep it goes
Explains mTLS, sidecars, traffic direction, policy placement, and tradeoffs, but does not detail mesh configuration or protocol internals.
Examples
Uses inventory calls, sidecars, internal east-west traffic, external north-south traffic, API gateways, and Istio as concrete examples.
What you can do after
Evaluate authorization placement and apply a mixed model that combines mesh enforcement with application-level business rules.

Read how Software Security for Developers explains service mesh →

Grokking Software Architecture

A service mesh is an infrastructure layer that manages service-to-service communication through dedicated networking components and centralized traffic policies.

How it is used
Uses a service mesh to support Zero Trust communication across polyglot or legacy services.
How deep it goes
Explains mutual authentication and token authorization through a service request, without detailing mesh configuration.
Examples
Uses a request between order and customer services to illustrate mutual authentication and token validation.
What you can do after
Evaluate/understand how sidecar proxies support internal service authentication and why authorization remains a separate check.

Read how Grokking Software Architecture explains service mesh →

Google Anthos in Action

A service mesh is an infrastructure layer that manages communication, traffic, security, and observability for distributed services.

How it is used
Manages communication, security, observability, resilience, and traffic flow across distributed services.
How deep it goes
Explains control-plane responsibilities, sidecar and proxyless architectures, telemetry, security, and deployment patterns without detailing implementation configuration.
Examples
Uses sidecars, proxyless services, telemetry dashboards, weighted canaries, A/B tests, retries, circuit breaking, and migration bridging.
What you can do after
Operate service communication through Anthos Service Mesh, inspect dependencies and metrics, secure traffic, and control progressive releases.

Read how Google Anthos in Action explains service mesh →

Kubernetes in Action, Second Edition

A service mesh is an infrastructure layer that manages communication, observability, traffic, and security between services without requiring application code changes.

How it is used
Manages communication, observability, traffic, and security between services without requiring application code changes.
How deep it goes
Defines east/west service communication and configuration models, but defers a full service-mesh explanation.
Examples
Uses an HTTPRoute with a destination Service parentRef to represent direct interservice traffic.
What you can do after
Apply it via Gateway API and GAMMA concepts to configure communication between services.

Read how Kubernetes in Action, Second Edition explains service mesh →

Kafka for Architects

A service mesh is an infrastructure layer that manages service-to-service communication and cross-cutting network concerns independently of service business logic.

How it is used
Separates microservice business functionality from standardized service-to-service communication and cross-cutting infrastructure concerns.
How deep it goes
Explains the sidecar split, proxy routing, configurable concerns, and contrast with centralized middleware without detailing implementation.
Examples
Uses separate business-logic and sidecar containers, with traffic routed through proxies handling encryption, retries, auditing, and load balancing.
What you can do after
Operate/configure reusable sidecars to offload integration responsibilities from microservice business code.

Read how Kafka for Architects explains service mesh →

Also covered in

What to know first

Related concepts

Questions about service mesh

What is service mesh?

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

Which Manning books explain service mesh?

Effective Platform Engineering, Authorization in Action, Software Security for Developers, Grokking Software Architecture, Google Anthos in Action, Kubernetes in Action, Second Edition and Kafka for Architects.

What should I know before learning service mesh?

Manning books that teach service mesh usually introduce microservice architecture, API gateway, observability and authentication first.

What is the difference between service mesh and API gateway?

A service mesh is an infrastructure layer that manages communication between distributed services and commonly provides traffic control, security, and observability. An API gateway is a server-side intermediary that provides an entry point for client requests to backend APIs or services and routes or mediates those requests.

What kinds of service mesh are there?

Kinds of service mesh include Istio and AWS App Mesh.

What are the parts of service mesh?

Service mesh includes control plane and data plane.

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.