This article explains the concept of Service Mesh, its sidecar architecture, and why it’s essential for cloud‑native microservices, then compares leading implementations such as Istio, Linkerd, and Envoy, highlighting their features and deployment models.
This article explains how to achieve zero‑trust security in Kubernetes by using a service mesh such as Linkerd, covering workload identity, mTLS, certificate management, policy definition with CRDs, and the practical limitations of mesh‑based protection.
This article explains how to prepare Linkerd for production use by covering high‑availability deployment, Helm chart installation, Prometheus metric handling, external Prometheus integration, multi‑cluster communication, and additional operational best‑practices such as resource tuning and security considerations.
This article compares nine widely used open‑source service‑mesh frameworks, explains their core features and typical use cases, and provides practical criteria to help DevOps teams select the most suitable mesh for their micro‑service deployments on Kubernetes or other platforms.
This article explains the concept of microservices, compares them with traditional monolithic web applications, outlines their advantages and challenges, and introduces first‑generation frameworks like Spring Cloud and Dubbo as well as next‑generation service‑mesh solutions such as Linkerd, Envoy, Istio, and Conduit, especially in Kubernetes environments.
After two years of using Istio in production, the author explains the operational complexities, reliability issues, and protocol limitations that led to abandoning Istio in favor of Linkerd, highlighting the pros and cons of both service meshes within Kubernetes environments.
This article examines Service Mesh security by outlining core requirements, detailing Istio’s built‑in zero‑trust mechanisms—including mutual TLS, AAA, and automatic certificate rotation—and comparing the security features of Linkerd and Alauda Service Mesh, offering practical insights for designing robust microservice protection.
The article examines why adopting service meshes like Istio and Linkerd is still difficult, outlining the roles of platform and service owners, common pitfalls such as sidecar injection failures, configuration complexities, and offers guidance to help teams evaluate and successfully implement mesh solutions.
This article explains the concept of Service Mesh, why it emerged from micro‑service challenges, its evolution, and compares the main open‑source implementations such as Linkerd, Envoy, Istio, and Conduit, helping readers grasp its role in modern cloud‑native architectures.
This roundup highlights recent Kubernetes ecosystem changes, including the addition of anti‑discrimination statements to documentation, the upcoming 1.19.0‑beta.1 code freeze, Linkerd 2.8 multi‑cluster support, several upstream enhancements, and curated open‑source project and reading recommendations for cloud‑native practitioners.
Linkerd 2.8 adds a multi‑cluster extension that securely connects Kubernetes clusters across any network topology, introduces an add‑on plugin system with Jaeger and Grafana support, and includes numerous performance and stability improvements for cloud‑native service mesh deployments.
A detailed benchmark comparing Spring Cloud Gateway, Zuul, and Linkerd shows that, contrary to popular belief, Spring Cloud Gateway delivers 1.6 times the throughput of Zuul and even outperforms Linkerd, after correcting earlier testing errors caused by a Reactor Netty bug.
