Cloud Service Mesh is Google’s managed service for secure, observable communication between services in service mesh architectures. The service evolved from Traffic Director and Anthos Service Mesh and automatically configures Envoy proxies or proxyless gRPC applications for load balancing and traffic splitting.
What is Cloud Service Mesh?
Cloud Service Mesh (formerly Traffic Director, and previously also marketed in part as Anthos Service Mesh) is the managed architecture for traffic management, observability, and security between microservices on Google Cloud. The service handles service discovery, health checking, load balancing, and traffic routing policies across all connected services — either via Envoy-based proxies and the xDS APIs or via proxyless gRPC applications.
Unlike self-managed service mesh solutions, Google Cloud manages the control plane. Cloud Service Mesh supports both a Google-managed control plane mode on GKE and Compute Engine and an in-cluster control plane mode for environments outside Google Cloud. The solution integrates natively with Google Cloud load balancers for global load balancing and multi-region deployments.
The service supports advanced traffic management patterns such as traffic splitting for canary deployments and A/B testing, circuit breaking for resilience, outlier detection for automatically removing faulty backends, and locality-based routing for latency optimization. Automatic mTLS between services provides security. Observability data flows automatically into Cloud Monitoring, Cloud Logging, and Cloud Trace.
Cloud Service Mesh works with GKE services, Compute Engine VMs, and hybrid or multi-cloud deployments. Depending on the use case, either Google Cloud-specific APIs or open Istio APIs are used.
Billing is usage-based. EU regions are available.
Core Features
- Managed control plane for traffic management, observability, and security
- Envoy-based proxies or proxyless gRPC applications as the data plane
- Traffic splitting, circuit breaking, outlier detection, and health checks
- Automatic mTLS between services
- Integration with Cloud Monitoring, Cloud Logging, and Cloud Trace
- Support for Google Cloud APIs and open Istio APIs
Typical Use Cases
Canary Deployments for Microservices
An e-commerce company uses Cloud Service Mesh for canary deployments of new service versions. A small share of traffic is routed to the new version while the majority remains on the stable version. The service monitors error rates, and issues trigger a manual or automated rollback. Progressive rollouts reduce deployment risk.
Multi-Region Service Mesh
A SaaS platform operates services across multiple GCP regions with Cloud Service Mesh. Locality-based routing directs requests to the nearest region, and cross-region failover helps during regional outages. Global load balancing optimizes latency for users worldwide.
gRPC Load Balancing
A FinTech startup uses Cloud Service Mesh for gRPC services in GKE. Proxyless client-side load balancing distributes requests directly to pod IPs without requiring additional sidecar proxies. Health checks and connection management optimize performance.
A/B Testing for Feature Rollouts
A mobile app platform tests new features using traffic splitting in Cloud Service Mesh. One share of users receives variant A, another variant B. Header-based routing enables targeting of specific user groups.
Hybrid Cloud Service Mesh
A company connects on-premises services with GKE via Cloud Service Mesh. Proxies in both environments use the same control plane for service discovery. Traffic policies ensure consistent load balancing logic across hybrid deployments.
Integration with innFactory
As a certified Google Cloud partner, innFactory supports you with Cloud Service Mesh: service mesh architecture, migration from older Traffic Director or Anthos Service Mesh setups, traffic policy design, GKE integration, and multi-region setup.
Contact us for a consultation on Cloud Service Mesh and Google Cloud.
Available Tiers & Options
Standard
- Managed control plane (GKE and Compute Engine)
- Traffic management, observability, and security in one service
- Envoy and proxyless gRPC support
- Setup and operation require service mesh expertise
Typical Use Cases
Frequently Asked Questions
What is Google Cloud Service Mesh?
Cloud Service Mesh is a managed architecture for secure, observable communication between microservices on GKE, Compute Engine, and hybrid environments. It handles traffic management, mTLS encryption, and observability so teams don't need to run their own service mesh control plane.
What was Traffic Director and how does it relate to Cloud Service Mesh?
Traffic Director (also previously marketed as Anthos Service Mesh) was the product's former name. Its traffic management functionality lives on in Cloud Service Mesh, with APIs and console paths largely unchanged.
Is Cloud Service Mesh available in EU regions?
Yes, the service is available globally, including EU regions, so data residency requirements for European workloads can be accommodated.
How does Cloud Service Mesh differ from self-managed Istio?
Cloud Service Mesh provides a Google-managed control plane, while Istio requires you to operate and update it yourself. Cloud Service Mesh integrates natively with Google Cloud load balancers and supports both Envoy proxies and proxyless gRPC.
What traffic management features does the service offer?
These include traffic splitting for canary deployments, circuit breaking, outlier detection for automatically removing faulty backends, health checks, and locality-based load balancing.
How is Cloud Service Mesh billed?
Billing is usage-based, including by number of managed clients or proxies. Exact prices and current rates are available on the official pricing page.
Note: All product information on this page has been compiled with care, but is provided without guarantee and may be outdated or incomplete. Cloud services evolve rapidly — features, pricing, SLAs, and availability change frequently. Authoritative and up-to-date information can only be found on the official product page of Google Cloud (official documentation). This page does not represent an offer by Google Cloud.
