Patterns and best practices for getting most out of Istio, Linkerd, Consul, App Mesh or any service mesh, including those using Envoy and use of WebAssembly.

About the Service Mesh Patterns book

A service mesh is a layer in your infrastructure that facilitates communication between services… and so much more. Its value is enormous, and the value you derive from one is very much related to what role you play in the design, implementation, and operations of your cloud native applications and infrastructure.

This book is being written for

Identifying who this book is for has been one of the hardest challenges in writing it. The power of a service mesh is vast, and therefore, empowers individuals of many different roles. In short, this book is for anyone delivering workloads enabled by a service mesh and who wants to ensure their use of a service mesh provides the most possible value to the workloads and teams that rely on it.

Service Mesh Patternalpha icon
Categoryalpha icon
Area I: It's a Mesh Out There
A world of multiple service meshesFoundational
Pattern: How a service mesh empowers an Operator: Retry BudgetsFoundational
Pattern: How a service mesh empowers a service ownerFoundational
Pattern: How a service mesh empowers a DeveloperFoundational
Pattern: Employing planes of a service meshFoundational
Area II: Patterns of Initialization and Deployment
Pattern: How to get started with any service mesh; Local DeploymentDeployment
Pattern: Sidecar ProxiesDeployment
Pattern: Node AgentsDeployment
Pattern: Proxyless Service MeshDeployment
Pattern: Passive and Active Health CheckingDeployment
Pattern: Workload Onboarding and Service Mesh Adoption workloads
Pattern: Expanding the Mesh to Brownfield Environmentsworkloads
Pattern: Segmenting the Monolith (Strangler)workloads
Area III: Patterns of Configuration
Pattern: Data plane extensibilityObservability
Pattern: Transparently Proxying TLSTraffic Manangement
Pattern: Foundational Traffic RoutingTraffic Manangement
Pattern: Local and Global Rate LimitingTraffic Manangement
Pattern: TimeoutsTraffic Manangement
Pattern: RetriesTraffic Manangement
Pattern: Circuit BreakingTraffic Manangement
Pattern: Bulkheading with ResiliencyResiliency
Pattern: Canary DeploymentsTraffic Manangement
Pattern: IngressTraffic Manangement
Pattern: Advanced Traffic RoutingTraffic Manangement
Pattern: Protocol Aware MeshingTraffic Manangement
Pattern: Load balancing AlgsTraffic Manangement
Pattern: Incorporating Business Logic in your data plane (WASM)Traffic Manangement
Pattern: Chaos Engineering with a Service MeshResilience
Pattern: Service Meshing at the EdgeTraffic Manangement
Pattern: Service Mesh Adapter Pattern (Protocol conversion using WASM)Traffic Manangement
Area IV: Patterns of Operation
Pattern: Visualizing servicesObservability
Pattern: Using Envoy metricsObservability
Pattern: Using Request LogsObservability
Pattern: Using TracesObservability
Pattern: Managing configuration changeTroubleshooting
Pattern: Advanced Data Plane Extensbility and IntelligenceTroubleshooting
Pattern: Cloud burstingScaling
Pattern: Multi-cluster failoverScaling
Pattern: FederationScaling
Pattern: Egress GatewaysSecurity
Pattern: Zero Trust: Securing in-cluster communication (mTLS) - EncryptionSecurity
Pattern: Applying Connection-level AuthorizationSecurity
Pattern: Applying Request-level AuthorizationSecurity
Area V: Performance, Testing, and Debugging, Tuning, Troubleshooting
Pattern: Debugging the Control PlaneTroubleshooting
Pattern: Debugging the Data PlaneTroubleshooting
Pattern: Methodologies of Performance Tuning and TestingTuning / Performance
Pattern: Managing the Performance of the Service MeshTuning / Performance
Pattern: Managing the Performance of the WorkloadsTuning / Performance
Pattern: Using the Service Mesh for Functional TestingValidating
Pattern: How to use the Service Mesh as a DebuggerDebugging
Pattern: TAPing into your requestsDebugging
Area VI: Patterns in Practice: Employing Standards
Pattern: The need for abstracting the service meshService Mesh Interface (SMI)
Pattern: Baselining your workload performanceService Mesh Performance (SMP)
Pattern: Gauging the value of your service mesh deploymentService Mesh Performance (SMP)
Pattern: Federating Service CatalogsMulti-Vendor Service Mesh Interoperation (Hamlet)
Pattern: Common interface for integrating with service mesh functionalityService Mesh Interface (SMI)

Docker and Meshery

Docker Extension for Meshery is now available!

Managing cloud native infrastructure has never been easier.

Sign up to to get access the extension.

Layer5, the cloud native management company

An empowerer of engineers, Layer5 helps you extract more value from your infrastructure. Creator and maintainer of service mesh standards. Maker of Meshery, the cloud native management plane.