CNCF and SlashData report shows China has 1.75 million cloud native developers, with 400,000 focused on AI, as cloud native technologies like Kubernetes, service mesh, and immutable infrastructure enable AI workloads to move from training to production inference at scale.
This article analyzes when to adopt Service Mesh over SDK-based governance, using three real incidents to illustrate trade-offs, comparing three governance generations, detailing cost analysis, migration paths, and troubleshooting methods, concluding that Mesh amplifies existing governance capability rather than creating it.
The article analyzes whether service mesh sidecar dual-write is suitable for a commercial bank's Xinchuang (indigenous innovation) system transformation, detailing service mesh concepts, pros/cons, applicable scenarios, and a decision framework with concrete criteria.
A comprehensive guide to diagnosing Kubernetes service connectivity issues by systematically verifying each network layer — DNS, Ingress, Service, Endpoints, kube-proxy, Pod readiness, and NetworkPolicy — with executable commands and a real-world case study.
The article argues that microservice performance testing must evolve from isolated load‑generation to topology‑aware, chaos‑integrated, AI‑driven practices, highlighting upcoming trends such as service‑mesh‑based traffic modeling, built‑in chaos‑as‑a‑test, and large‑language‑model‑assisted root‑cause analysis to prevent cascading failures.
The article explains why propagating TraceID and parent SpanID across services, processes, and asynchronous boundaries is essential for complete distributed tracing, outlines the pain points of manual header handling, and walks through the evolution toward standardized W3C Trace Context, automatic instrumentation, and OpenTelemetry‑based solutions while highlighting async and service‑mesh pitfalls.
This Day 60 case study walks through a regional medical appointment platform that has been broken into micro‑services on a container cluster, asking you to select and justify service discovery, TCC/Saga, reliable messaging, Kubernetes, Service Mesh and observability measures, and to explain their benefits and trade‑offs.
This article provides a comprehensive overview of microservices architecture, covering bounded contexts, service granularity, API layers, sidecar/service mesh patterns, communication styles, data topology, distributed transactions with Saga, common anti-patterns, characteristic ratings, and team topology alignment.
The article examines how traditional percentage‑based canary releases evolve into fine‑grained, attribute‑driven deployments with session stickiness, automated SLO gating, traffic mirroring, and service‑mesh integration, highlighting five pain points, practical solutions, and the hidden prerequisites for large‑scale systems.
This article walks through a real‑world microservice latency incident, then explains how SkyWalking’s Java agent provides zero‑intrusion tracing, automatically builds service topology, offers built‑in alerting and profiling, and compares storage options and deployment patterns for production observability.
The article revisits microservice design by explaining how Domain‑Driven Design determines business boundaries, why each service must own its data, how Service Mesh and unified governance handle communication, and how logs, metrics and traces provide observability for distributed systems.
This article walks through why Go is ideal for cloud‑native development and demonstrates step‑by‑step how to build a scalable service mesh, covering static compilation, HTTP services, Go modules, Gin/Gorilla APIs, configuration, logging, health checks, service registration, load balancing, sidecar proxies, traffic interception, circuit breaking, rate limiting, retries, and distributed tracing with OpenTelemetry.
Over five years, Airbnb's Viaduct service mesh grew traffic eightfold, doubled the number of owning teams to over 130, tripled its codebase to 1.5 million lines, halved incident minutes, and kept operational costs linear with QPS, leading to a major redesign and open‑source release.
Even though a gateway performs unified authentication and injects user information into request headers, microservices must still execute a second layer of authorization to verify data ownership, enforce business rules, and protect against internal threats, following a zero‑trust security model.
The article analyzes why the gateway layer often becomes a bottleneck, compares four gateway architecture patterns, evaluates protocol choices between HTTP and gRPC, presents performance benchmarks of open‑source gateways, reviews industry case studies, and finally recommends an APISIX‑based gRPC‑only architecture with domain‑level aggregation.
This article breaks down four key microservice architecture patterns—data‑sharing, aggregation, sidecar proxy, and asynchronous messaging—detailing their purpose, typical use cases, benefits, and why some are only suitable as short‑term solutions during system migration.
This article explains how Airbnb broke a dangerous circular dependency in its observability stack by isolating metric collection onto dedicated Kubernetes clusters, adding a custom L7 network layer to decouple from the service mesh, and implementing meta‑monitoring with a dead‑man’s‑switch to keep monitoring systems reliable during failures.
This comprehensive guide explains Istio’s sidecar architecture, traffic management, mutual TLS security, and observability features, then walks through prerequisite checks, installation with istioctl and Helm, sample Bookinfo deployment, advanced configuration, troubleshooting, monitoring, and backup strategies for production‑grade service meshes.
Recent high‑profile outages—from AWS DynamoDB to Cloudflare—show that API failures can cripple enterprises, yet most teams lack visibility into their dependencies; this article examines real‑world API outage scenarios, outlines a four‑layer resilience architecture, and offers concrete steps such as audits, multi‑vendor redundancy, and chaos testing.
The article explains Service Mesh as a cloud‑native architecture that separates control and data planes, details its sidecar proxies, core components like Istio Pilot and Citadel, and outlines key capabilities such as traffic management, security, observability, and resilience to help exam candidates master the topic.
The article analyzes various API architecture patterns—monolithic API, microservice API, API Gateway, BFF, Service Mesh, API Mesh, Strangler Pattern, event‑driven API, and GraphQL Federation—explaining their origins, trade‑offs, hidden costs, and suitability for different team sizes and business scenarios, ultimately showing how the right pattern ensures long‑term system evolution and scalability.
The article explains how traditional microservice architectures embed network concerns such as time‑outs, retries, circuit breaking, traffic monitoring and mTLS in application code, why this leads to code coupling, upgrade difficulty and duplicated effort, and how Istio’s sidecar‑based service mesh cleanly separates those concerns while providing traffic management, observability and security features.
This article reviews the entire Spring Cloud microservices series, presents a full technology stack diagram, outlines production‑grade best practices for service decomposition, configuration, remote calls, rate limiting, databases, logging and monitoring, lists common pitfalls, offers performance‑tuning tips, discusses the pros and cons of microservices, and points to future directions such as service mesh, serverless and cloud‑native adoption.
During a high‑traffic load test, a Kubernetes 1.28 cluster appeared to stall despite low CPU and memory usage, revealing hidden bottlenecks across container limits, conntrack saturation, CoreDNS latency, and control‑plane overload; the article walks through a systematic root‑cause analysis and step‑by‑step remediation.
This guide provides a deep technical comparison of Nginx Ingress Controller, Traefik, and Envoy Proxy, covering architecture, configuration, performance, feature sets, deployment patterns, security hardening, monitoring, and troubleshooting to help operators select the best solution for their Kubernetes clusters.
This comprehensive guide explains why Kubernetes service discovery is more than name‑to‑IP mapping, details the control‑plane and data‑plane components, compares Service types, explores CoreDNS caching, EndpointSlice, kube‑proxy modes, multi‑cluster strategies, and provides production‑grade code samples and troubleshooting steps.
This article compares four microservice deployment approaches—standalone virtual machines, Docker containers, Kubernetes clusters, and service‑mesh‑enhanced Kubernetes—detailing their architectures, advantages, drawbacks, and ideal use cases to help teams select the most suitable strategy.
Traffic swimlanes provide logical isolation for microservice requests by tagging, propagating, and routing traffic based on lane metadata, enabling cost‑effective testing environments, canary releases, A/B testing, full‑link load testing, and parallel development while reducing resource consumption and improving stability.
This tutorial explains how to use Envoy Gateway on Kubernetes to implement circuit breaker and connection‑limit policies, walks through the necessary YAML configurations, demonstrates verification with the hey load‑testing tool, and shows how these mechanisms improve system resilience in microservice architectures.
This article explains how Kubernetes implements load balancing both inside the cluster through Services and kube-proxy, and outside the cluster via Ingress controllers or cloud provider load balancers, covering common algorithms such as round‑robin, least connections, consistent hashing, and weighted strategies.
This guide explains why gray (canary) releases are essential for production stability in internet companies, and provides step‑by‑step configurations using Istio’s VirtualService, Gateway, and DestinationRule resources to route traffic by percentage or request headers in a Kubernetes cluster.
When a Spring Boot service faces tens of thousands of QPS, stability depends less on code tweaks and more on how traffic is intercepted, distributed, and throttled across edge, gateway, Kubernetes, client, and mesh layers, making a layered load‑balancing architecture essential.
To keep Spring Boot applications stable under tens of thousands to millions of requests per second, this guide explains why load balancing evolves from a simple traffic splitter to a multi‑layer system and details seven critical strategies—from edge CDN to service mesh—required for resilient, cost‑effective high‑concurrency deployments.
The article explains how network protocols have evolved from raw TCP sockets to standardized HTTP and finally to RPC frameworks, showing that each step is an abstraction upgrade rather than a replacement, and clarifies when to use HTTP versus RPC based on system boundaries and engineering trade‑offs.
The article breaks down seven layered load‑balancing strategies—from edge CDN to traffic shaping—that a Spring Boot system must adopt to control latency, isolate failures, manage cost, and gracefully degrade when handling tens of millions of concurrent requests.
This guide explains how to set up Alibaba Cloud Service Mesh (ASM) on an ACK Kubernetes cluster, covering prerequisites, two methods of cluster registration, creation of north‑south and east‑west gateways, traffic routing with HTTPRoute, security policies using PeerAuthentication and AuthorizationPolicy, and observability configuration via Telemetry.
The article explains how Canary Deployment gradually rolls out new software to a small user subset, monitors performance, and rolls back quickly, offering lower risk, faster feedback, and higher release confidence for large‑scale, mission‑critical systems.
After a year of running Istio in production on a 80‑service, 200‑node Kubernetes fleet, we share six painful pitfalls—including unexpected latency, debugging complexity, upgrade nightmares, configuration explosion, compatibility issues, and mTLS challenges—plus practical mitigation steps and guidance on when Istio truly adds value.
The article explains how microservice projects often become cluttered with retry, timeout, circuit‑breaker, TLS, logging and traffic‑splitting code, and shows that delegating these concerns to a Service Mesh such as Istio—combined with Spring Boot 3.4.1 and Gateway API—removes the burden from application code while providing traffic management, security and observability.
This article outlines four common microservice deployment approaches—single‑machine multi‑process, containerized deployment with Docker/Kubernetes, serverless functions, and service‑mesh architecture—detailing their advantages, limitations, and suitable scenarios for each method.
This comprehensive guide breaks down microservice governance into four pillars—node management, load balancing, routing, and fault tolerance—providing concrete configurations, algorithm choices, and service‑mesh recommendations to achieve 99.99% availability, cut wasted resources by over 30%, and halve iteration cycles.
This article explains Envoy's request mirroring feature, shows how it copies live HTTP requests to a test backend without affecting the original response, and provides step‑by‑step configuration examples for mirroring all traffic, selective paths, percentage‑based sampling, and header‑driven routing, plus practical tips and typical use cases.
This article details a company’s step‑by‑step evolution from basic observability to a full‑stack traffic governance framework—including automated tracing, adaptive rate‑limiting, circuit‑breaking, and intelligent gray‑release—enabling stable operation of a microservice ecosystem with tens of thousands of instances while cutting MTTR to minutes and resource waste by over 20%.
Microservice architectures face severe communication bottlenecks due to network overhead, serialization costs, and connection management, but by adopting high‑performance protocols like gRPC, leveraging service meshes, optimizing load balancing, caching, connection pools, and robust monitoring, teams can dramatically improve latency and throughput.
This article explores the challenges and best practices of cloud‑native scaling, covering Horizontal and Vertical Pod Autoscalers, Cluster Autoscaler cost optimization, event‑driven scaling with KEDA, traffic‑aware scaling in service meshes, and intelligent cost‑aware strategies backed by monitoring and future AI‑driven trends.
The Higress 2.0 release introduces 30 changes—13 new features such as a RAG MCP server and ECDS‑based configuration refactor, 7 bug fixes, 5 refactorings, documentation updates and a test improvement—providing developers with enhanced knowledge‑management capabilities, more stable routing, and clearer documentation for cloud‑native service‑mesh environments.
This article presents a comprehensive roadmap for backend architects, covering microservice fundamentals, design principles, gateway patterns, communication protocols, service registration, configuration management, observability pillars, service mesh options, and a detailed comparison of modern message‑queue technologies.
This article examines the rising security risks in microservice architectures, explains why traditional perimeter defenses fall short, and presents a comprehensive zero‑trust strategy that combines service‑mesh mTLS, API‑gateway hardening, token‑exchange authentication, OPA policies, data‑level encryption, observability, and container‑level safeguards.
This article outlines six fundamental cloud‑native architecture principles—immutable infrastructure, service mesh, observability, declarative APIs, resilient design, and shift‑left security—explaining their purpose, key practices, code examples, and how they interrelate to build scalable, reliable, and secure distributed systems.
This guide explains why TLS and mTLS are essential for modern microservice communication, then walks through configuring Envoy for both simple TLS termination and full mutual TLS, covering listeners, clusters, certificate management, and provides runnable examples with verification commands.
An in‑depth look at how containers, Kubernetes, and Service Mesh together form the core of modern cloud‑native architectures, covering their evolution, practical adoption stages, trade‑offs in complexity, decision‑making matrices, best‑practice implementation tips, and emerging trends such as edge computing and WebAssembly.
Gateway API replaces the traditional Ingress API with a more powerful, standardized, role‑oriented model that supports advanced L4/L7 routing, multi‑protocol traffic, and seamless service‑mesh integration, addressing Ingress’s limitations in scalability, portability, and complex configuration for both platform and application teams.
This guide walks through diagnosing Envoy WebSocket proxy issues, explains the required backend environment, provides step‑by‑step configuration snippets, and shows how to verify the setup, ensuring reliable WebSocket traffic in cloud‑native deployments.
This article explains why backend services often see proxy IPs instead of the true client address in modern cloud‑native architectures, and provides a detailed walkthrough of configuring Envoy—including X‑Forwarded‑For handling, code snippets, testing, and security recommendations—to ensure the original client IP is correctly propagated.
This article explains how to implement safe, incremental gray releases in a microservice architecture using Envoy Proxy, covering weight‑based traffic splitting, header‑based canary routing, and cookie‑based routing with full configuration examples and testing commands.
This article explains how Envoy’s circuit‑breaker and outlier‑detection features protect micro‑service architectures from avalanche failures by limiting concurrent connections, ejecting unhealthy instances, and provides configuration examples, testing methods, and best‑practice tips for building resilient cloud‑native systems.
Envoy, the high‑performance edge and service‑mesh proxy, offers three core mechanisms—service discovery, load balancing, and health checking—each with multiple configurable options and code examples, enabling operators and developers to optimize distributed systems for scalability, reliability, and performance in cloud‑native environments.
This tutorial introduces Envoy Proxy, explains its core building blocks—listeners, routes, clusters, and filters—demonstrates a quick Docker-based setup, and walks through a complete configuration that routes traffic based on URI paths, providing a practical five‑minute overview of service‑mesh fundamentals.
This article explains the Ztunnel upgrade process in Alibaba Service Mesh Ambient mode, details the rolling and graceful‑shutdown mechanisms, presents performance test results with and without graceful shutdown, and offers best‑practice recommendations to minimize traffic interruption during upgrades.
Learn how ASM's Ambient mode and the Waypoint component streamline L7 egress traffic management in Kubernetes by replacing complex Sidecar configurations with simple ServiceEntry and Waypoint labels, reducing configuration overhead while preserving powerful security and observability features.
Alibaba Cloud Service Mesh (ASM) 1.25 introduces Ambient mode, a sidecar‑less architecture that decouples the mesh from pods, enabling instant mTLS, lower latency, reduced resource consumption, and optional Waypoint proxies for advanced L7 features, all without redeploying applications.
This article explains the concepts, implementation details, configuration steps, typical use cases, performance and security best practices, and future trends of Istio traffic mirroring for safe and controllable traffic replication in cloud‑native environments.
Learn how to set up a production-grade HashiCorp Consul service mesh on Kubernetes using Helm, covering prerequisites, chart handling, configuration files, deployment commands, and verification steps to ensure reliable service discovery, health checks, and secure communication in a cloud-native environment.
This article explains the concept, implementation principles, configuration details, and common use cases of Outlier Detection in Service Meshes, showing how it isolates faulty instances to improve stability, performance, and automated operations in cloud‑native environments.
The article explains what a Virtual Private Cloud (VPC) is, how it creates an isolated, customizable network on a cloud provider, outlines its core components such as subnets, gateways, and peering, and details security designs, traffic flows, and advanced scenarios like high‑availability and hybrid cloud integration.
This article traces the evolution of internet architecture from monolithic and MVC designs through multi‑application and distributed systems, explains service‑oriented architecture and its benefits, introduces Dubbo‑based service governance, and outlines the core concepts, features, and implementation approaches of microservices.
This article explains how to design custom routing rules, version‑based load balancing, and gray‑deployment strategies in distributed microservice systems to isolate service versions, ensure safe acceptance testing, and smoothly roll out new releases.
The article examines Meta’s warning that current microservice architectures will struggle with the upcoming AI explosion, outlines the performance, scalability, and cost challenges, and proposes serverless, service mesh, and hybrid redesigns as potential solutions.
The article explains what a service mesh is, its core components, key capabilities such as traffic management, security, observability, and resilience, reviews major tools like Istio, Linkerd and Consul Connect, and discusses the operational challenges and future directions within cloud‑native environments.
This article explains how Istio's sidecar proxy uses Envoy, iptables rules, and the xDS API to intercept and redirect traffic between Kubernetes pods, detailing the startup injection, traffic hijacking process, and how configuration is dynamically generated by istiod.
The article examines how microservice architecture, as a subset of distributed systems, expands the attack surface and introduces data fragmentation and communication complexities, and outlines comprehensive security strategies—including API protection, service‑to‑service encryption, infrastructure hardening, authentication, vulnerability management, and emerging technologies like service mesh and serverless computing—to safeguard modern applications.
This article explains how Alibaba Cloud Service Mesh (ASM) can be extended using EnvoyFilter, Lua scripts, WebAssembly plugins, External Processing filters, and custom authorization services, detailing their capabilities, limitations, and recommended use cases for cloud‑native microservice environments.
This guide explains how to achieve zone‑level disaster recovery on Alibaba Cloud by deploying multi‑AZ ACK clusters, configuring Service Mesh ASM for observability and traffic shifting, and using Prometheus‑based metrics and alerts to detect and isolate failures, including step‑by‑step instructions and sample YAML manifests.
Facing thousands of heterogeneous gateway configurations across multiple tech stacks, a Chinese cloud‑native platform consolidated its gateway layer by adopting Higress, Istio CRD, and APISIX, introducing a two‑tier rule model and automated migration tools that cut maintenance effort by 90% while preserving service continuity.
This guide explains how to use Alibaba Cloud Service Mesh (ASM) to add infrastructure‑level observability for large language model (LLM) traffic, covering custom access‑log fields, new Prometheus metrics for token usage, and adding model dimensions to native Istio metrics, with step‑by‑step commands and configuration examples.
This article explains the relationship between API gateways and service meshes, compares exposure methods, and provides a detailed, step‑by‑step guide for exposing services inside an Istio mesh using an Nginx Ingress Controller, including required annotations and configuration details.
This article explains how to handle intermittent 5xx errors and request timeouts in complex internet services using Istio service mesh, covering system availability levels, retry mechanisms, timeout settings, and concrete VirtualService configurations to improve reliability and user experience.
This article consolidates a series of ByteMonk videos covering essential microservice architecture patterns—including service registration and discovery with Eureka, API gateway design, event‑driven architecture, service mesh, aggregator pattern, per‑service databases, bulkhead and strangler patterns, and monolith decomposition case studies—providing practical insights for building scalable, resilient systems.
Tencent's PolarisMesh showcases cloud-native microservice governance by detailing the shift from monoliths to containerized services, outlining service splitting principles, Kubernetes deployment, dynamic routing, fault isolation, and real-world case studies that demonstrate cost savings, reliability improvements, and open-source availability.
This article explains four common microservice deployment approaches—multi‑instance, containerized, serverless, and service‑mesh—detailing their architectures, advantages, disadvantages, and suitable scenarios to help engineers choose the right strategy for scalable, resilient systems.
This article shares practical guidance on rolling out Istio service mesh to over ten business lines, covering selection of pilot projects, benefit analysis using access logs, sidecar injection, performance and resource impact, multi‑region active‑active architecture benefits, and rapid fault‑recovery tactics.
This article explains how Netflix built the Data Gateway platform to abstract and protect complex distributed databases, detailing its motivation, architecture, component overview, declarative runtime and deployment configurations, and real‑world case studies such as key‑value services, secure RDS, and seamless data migration.
Data GatewayDeclarative DeploymentKey-Value Service
This guide explains how to use Kmesh, an eBPF‑based high‑performance service‑mesh data plane, with Alibaba Cloud ASM by configuring the control plane, deploying the Kmesh DaemonSet, setting required environment variables, and verifying traffic routing and service status.
This article explains how Service Mesh can use traffic coloring to route requests based on headers, cookies, or query parameters, enabling safe canary releases, diversified version testing, and isolated QA environments in complex production systems.
This guide explains how to use Alibaba Cloud Service Mesh (ASM) loose‑mode traffic lanes to isolate WebSocket‑based services, configure context propagation via OpenTelemetry Baggage, and achieve full‑chain gray releases with step‑by‑step deployment, gateway routing, and testing procedures.
This tutorial walks you through connecting a test machine, downloading and installing Istio 1.8.6, configuring environment variables, deploying the BookInfo sample application, verifying pods and services, setting up inbound traffic, exposing dashboards, and introduces Istio’s core traffic‑management capabilities.
This article shares Soul's two‑year practice of using the cloud‑native Envoy proxy for high‑performance, high‑throughput, and highly available traffic management across north‑south and east‑west flows, covering architecture, dynamic service discovery, load balancing, health checks, WASM extensions, service‑mesh integration, Redis proxying, and future directions.
This article explains the fundamentals of Service Mesh and Istio, covering their architecture, control‑plane and data‑plane components, deployment modes, key capabilities such as traffic control and security, and the interaction workflow that enables modern cloud‑native microservice environments.
The article introduces Joylive Agent, a Java bytecode‑enhancement framework that implements a proxyless service‑mesh architecture for microservice governance, detailing its background, design principles, plugin system, bytecode manipulation techniques, traffic‑control strategies, multi‑active models, and deployment practices on Kubernetes.
This article explains the challenges of microservice communication and fault tolerance, introduces service mesh and its drawbacks, and presents a Java bytecode‑enhancement solution that combines SDK performance with sidecar‑less governance, detailing the Joylive Agent architecture, plugin system, request abstraction, governance strategies, and Kubernetes deployment practices.
This article explores the concept of traffic hijacking, compares front‑end and back‑end interception methods, and provides practical proxy‑based implementations for fetch, XMLHttpRequest, and ReadableStream to achieve seamless request and response manipulation in a unified authentication system.
This article introduces ten essential Kubernetes technologies—including Helm Charts, Operators, Service Mesh, StatefulSets, CRDs, Network Policies, Pod Disruption Budgets, HPA, Persistent Volumes, and Ingress Controllers—explaining their core concepts, key capabilities, and how they improve application reliability, scalability, and security.
The article details how Baidu’s Jarvis2.0 platform evolved from a few modules to over a thousand microservices, introducing a cloud‑native multi‑runtime architecture, automated deployment pipelines, and an xDS‑based control plane that dramatically improve deployment speed, governance efficiency, and system stability across dozens of product lines.
This article examines Baidu's Jarvis2.0 platform, detailing how its multi‑runtime architecture, unified control plane, and automated deployment pipelines transformed a sprawling microservice ecosystem of over 1,000 services into a highly efficient, cloud‑native system that dramatically reduced release times, improved stability, and enabled seamless multi‑language support.
Discover how Istio secures microservices with comprehensive authentication, authorization, and mutual TLS features, covering concepts, architecture, identity management, policy configuration, permissive mode, and practical YAML examples to protect services, data, and communication across any deployment environment.
This guide explains how to connect Dubbo microservices to Alibaba Cloud Service Mesh (ASM) to obtain mTLS, observability, and traffic management, covering prerequisites, step‑by‑step deployment, code examples, a registry‑based transition approach, and recommended best‑practice configurations.
This article explores Polaris‑Mesh’s server‑side health‑check mechanism, detailing how client heartbeat requests are received via gRPC, processed through Apiserver, Resource Auth Filter, Service, Healthcheck, and Checker Plugin, and how the system’s configuration, plugins, and time‑wheel ensure reliable instance health monitoring.