The article explains how microservice architectures introduce complexity, how Netflix OSS tools address these challenges, and why adopting the Sidecar design pattern with Istio’s service mesh can improve scalability, resilience, and observability in cloud‑native systems.
This article explains the concept of circuit breaking and rate limiting in micro‑service architectures, compares Hystrix and Istio implementations, details Istio's ConnectionPool and outlierDetection settings, maps their parameters to Envoy, and provides step‑by‑step command‑line examples that demonstrate how these controls behave in practice.
Implementing a service mesh in production faces real‑world hurdles such as significant CPU consumption, 20‑50% performance loss, tangled sidecar responsibilities, missing registration support, and control‑plane bottlenecks, which can be mitigated by a central‑mesh fallback, IPC and lock‑free optimizations, staged sidecar splitting, and unified Pilot‑based service discovery.
This article provides a detailed analysis of Envoy’s filter architecture within Istio 1.1, explaining the async event model, each filter type, their registration interfaces, and the key processing steps from listener selection to load‑balancing and Mixer integration.
This article introduces Istio as an open‑source service mesh, explains its data‑plane and control‑plane architecture, outlines its traffic management, security, and telemetry features, discusses performance considerations, and shows how Lingque Cloud ASM leverages Istio to solve typical microservice problems such as debugging, testing, release processes, and flexible network policies.
This article introduces the fundamentals of Istio as a service mesh, explains its data‑plane and control‑plane architecture, and details the roles of the Pilot component—including pilot‑agent and pilot‑discovery—in providing service discovery, traffic management, and integration with Kubernetes for microservice deployments.
This article explains how Istio simplifies microservice management by providing a full service‑mesh solution—including service discovery, load balancing, fault recovery, telemetry, and traffic control—while detailing its architecture, the roles of the data and control planes, and the functions of the Pilot components.
The weekly roundup covers the Docker Hub breach affecting 190,000 accounts, Java 8’s new container support, Snyk’s 2019 container‑security report, major Kubernetes upstream changes including Federation v2 and Ephemeral Containers, Knative’s build deprecation, Istio 1.1.4 release, Envoy enhancements, a non‑root containerd effort, and a recommendation of the kubeCDN project.
This article examines the rising hype around Service Mesh, explains the three core service‑discovery patterns, compares their trade‑offs, details how Service Mesh (the sidecar model) works with Istio, and offers practical advice on when (or when not) to adopt it in production environments.
This article traces the historical shift from program‑centric sockets to service‑oriented architectures, explaining how performance, stability, and access control drove the rise of load balancing, DNS, service governance, micro‑services, and ultimately cloud‑native service‑mesh solutions like Istio.
This article details Ant Financial's progressive Service Mesh migration plan, explaining the challenges of moving massive legacy applications to Kubernetes and Istio, the evaluated evolution routes, key migration practices like network continuity and DNS-based addressing, and the implementation of custom CoreDNS plugins for dynamic DNS updates.
The BEP Gateway architecture for YouZan’s e‑commerce cloud bridges the core domain’s Dubbo‑based service governance with the customized domain’s Kubernetes/Istio mesh by using sidecar proxies, converting Dubbo RPC to HTTP/2, providing network isolation, a generic provider, SDK authorization, and plans for multi‑language support and enhanced gateway features.
This article introduces Istio as a cloud‑native service mesh, explains its core components, features such as traffic management, security, and observability, and provides step‑by‑step commands to quickly deploy Istio on an Alibaba Cloud Kubernetes cluster.
Naftis is an open‑source web dashboard for Istio that lets users define custom task templates, manage services, view topology and metrics, and provides step‑by‑step Kubernetes deployment instructions, Docker images, and a complete developer guide for building and running the platform.
This article presents a DNS‑based universal addressing solution that enables traditional SOA applications using interfaces such as Dubbo, HSF, and SOFA to run on a Service Mesh without code changes, by mapping interface names to Kubernetes ClusterIP through CoreDNS and leveraging Istio’s routing mechanisms.
This article explains why UCloud introduced a Service Mesh, how Istio was chosen and adapted for the UAEK Kubernetes platform—including IPv6 challenges, performance testing, and future improvements—providing practical insights for building reliable micro‑service infrastructures.
Istio 1.0, released on August 1, brings the first production‑ready service‑mesh platform with major enhancements in networking, policy & telemetry, out‑of‑process adapters, and security features such as mTLS and JWT, while introducing the IstioGateway to replace the legacy Ingress model.
Istio 1.0, now production‑ready, launches after a year of rapid growth, offering beta‑grade features such as multi‑cluster support, fine‑grained network APIs, incremental mutual TLS rollout, and enhanced Envoy performance, while an expanding ecosystem of observability, policy, and serverless projects backs its adoption.
In a detailed Q&A session at ArchSummit 2018, Ant Financial and Alibaba UC experts discuss the fundamentals, challenges, implementation strategies, and future directions of Service Mesh and Kubernetes, covering performance, multi‑language support, open‑source efforts, and practical advice for developers and operators.
This article explains why microservice architectures need reliable communication, load balancing, fault tolerance, monitoring, tracing and circuit breaking, and shows how Istio—a cloud‑native service mesh built on Envoy—provides these capabilities, enabling blue‑green and canary deployments, traffic routing, retries, and observability within Kubernetes.
UCloud’s CTO emphasizes stable services while embracing change, leading to a lightweight Service Mesh solution that replaces costly API gateways with Istio‑derived components, enabling efficient gray releases, reduced maintenance, and seamless integration with existing services through Docker‑compose sidecars and ETCD‑based discovery.
This article reviews the challenges of early microservice frameworks—high technical barriers, limited multi‑language support, and intrusive code—and explains how service mesh architectures with sidecar proxies, exemplified by Linkerd, Envoy, and Istio, provide a dedicated, language‑agnostic infrastructure layer that simplifies service governance and operations.
This article introduces the concept of Service Mesh, highlights Istio as a leading solution, explains the Sidecar pattern—its isolation benefits, typical implementations such as NGINX reverse proxies, and discusses when to adopt this architecture in cloud-native environments.
With large organizations moving to self‑organized microservice teams, this article explains how service mesh and microgateway technologies provide decentralized, consistent service‑to‑service communication, detailing gateway functions, data‑plane and control‑plane roles, and the evolution of low‑invasive components, reverse proxies, sidecar patterns, and native infrastructure such as Istio.
Istio, an open-source service mesh created by IBM, Google, and Lyft, offers a uniform platform for integrating microservices, managing traffic, enforcing policies, and collecting telemetry, with a control plane that abstracts underlying cluster platforms like Kubernetes, illustrated through developer presentations and slide decks.
This article compiles a curated collection of high‑quality resources—including introductory explanations, in‑depth tutorials, Chinese translations, and tool overviews for Istio, Linkerd, and Envoy—to guide readers from basic concepts to advanced practices in service mesh and cloud‑native microservice architectures.
This article introduces Envoy as the core sidecar proxy in Service Mesh, explains its terminology, thread model, filters, routing, health checking, circuit breaking, hot restart, and presents multiple deployment patterns for cloud‑native microservice environments.