Google Cloud Service Mesh vs Linkerd
Google Cloud Service Mesh
cloud.google.comLinkerd
linkerd.ioSide by side
| Figure | Google Cloud Service Mesh | Linkerd |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| Linux | — | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 1 |
| Spec score · Service Mesh Platforms | 6.8 (#13) | 7.6 (#10) |
Plans
Google Cloud Service Mesh
- Cloud Service Mesh standalone usageFree
In their own words
Google Cloud Service Mesh
Google Cloud Service Mesh is a web-accessed service mesh with a hybrid deployment model. Its listed capabilities include mutual TLS, traffic policies, and multi-cluster support, with proxy architecture listed as both. Supported platforms include GKE on Google Cloud and Google Distributed Cloud software-only for VMware. The standalone usage plan is listed at free and charges each client $0.0006945 per hour. That plan includes a managed control plane, telemetry dashboards, and a managed certificate authority with no per-certificate charge. The broader pricing information identifies the service as paid, says there is no free plan, and gives a pricing note of From $0.50/mo. These are separate listing details from the standalone usage plan. Teams assessing the service can focus on its stated traffic-policy controls, mutual TLS, multi-cluster coverage, hybrid deployment, and managed components. Web is the listed platform for access.
Linkerd
Linkerd is a service mesh for Kubernetes that adds runtime debugging, observability, reliability and security without requiring changes to application code. It installs into a Kubernetes cluster and injects sidecar proxies into workload pods. The mesh handles HTTP, HTTP/2, gRPC and arbitrary TCP traffic, including TLS connections and WebSockets. It automatically enables mutual TLS between meshed applications and supports authorization policies between services. Metrics include request volume, success rates and latency distributions for HTTP, HTTP/2 and gRPC, plus TCP-level metrics. Traffic controls include load balancing, retries, timeouts, dynamic routing, traffic splitting and rate limiting. Linkerd can use Prometheus and Grafana and supports distributed tracing. Its Linkerd Viz Prometheus instance retains metrics for a short fixed interval, currently six hours, so it is intended to supplement an existing metrics store. Installation requires a modern Kubernetes cluster and a working kubectl command. The open-source project is licensed under Apache 2.0; Buoyant offers commercial support, training and architecture reviews. The listed plan is free.