This article explains the concept of web load balancing, its underlying one‑to‑many mapping principle, and compares common techniques such as DNS round‑robin, CDN acceleration, IP‑level load balancing, HTTP redirects, and reverse‑proxy solutions, highlighting their advantages, limitations, and typical deployment scenarios.
This article explains how to achieve high‑availability software load balancing by combining the open‑source HAProxy reverse‑proxy with Keepalived, covering installation, configuration of VRRP, health checks, session persistence, SSL termination, and traffic routing on CentOS systems.
This article explains the role of load balancers in large-scale internet applications, introduces Linux Virtual Server (LVS) as a four‑layer software load‑balancing solution, describes its architecture, NAT/TUN/DR forwarding methods, and details various static and dynamic scheduling algorithms such as Round Robin, Weighted Least‑Connection, and locality‑based strategies.
This article explains the purpose of load balancing in distributed systems, describes its classification across OSI layers, outlines typical deployment topologies, reviews popular software solutions such as LVS, Nginx, and HAProxy, and summarizes both static and dynamic load‑balancing algorithms.
This article outlines the progressive evolution of system architecture—from a single‑server LAMP setup through service‑data separation, caching, clustering, read/write splitting, CDN, distributed databases, NoSQL, business splitting, and finally distributed services with messaging, service frameworks, service bus, communication patterns, and governance—highlighting the motivations, characteristics, and challenges at each stage.
This article provides a detailed introduction to load balancing, covering its purpose, layer‑based classifications, popular software solutions such as LVS, Nginx and HAProxy, and a wide range of static and dynamic balancing algorithms used to distribute traffic across server clusters.
This article explains how startup engineers can design and implement a scalable web architecture—covering server clustering, load balancing, distributed caching, database replication, and team organization—to handle rapid user growth without compromising performance or reliability.
This article examines the objectives, technical challenges, and evolutionary steps of large‑scale website architecture, covering resource separation, caching mechanisms, high‑availability techniques, CDN and distributed storage, as well as foundational design principles such as ACID/BASE and the CAP theorem.
The article explains how kernel‑level load balancing works, why naïve thread‑pool wake‑up can cause CPU imbalance, and proposes using thread affinity, priority layers and a custom layered condition variable to achieve better performance in multithreaded server applications on Linux.
This article describes a complete two‑machine high‑availability solution that uses keepalived to manage virtual IPs, Nginx for load‑balancing, MySQL GTID replication with Atlas as a proxy, and detailed configuration and fail‑over testing steps to ensure seamless service continuity.
This article examines the objectives, challenges, evolutionary technologies, design principles, and practical strategies such as resource separation, caching, load balancing, database read/write splitting, CDN, distributed storage, and consistency models that are essential for building and scaling large‑scale website architectures.
The article examines the progressive evolution of image server architectures—from early NFS‑based setups through distributed storage with load balancing and caching, to modern cloud‑based solutions like Alibaba OSS—highlighting design considerations, performance trade‑offs, and implementation details for scalable, high‑availability image services.
This article examines how load‑balancing technologies such as Nginx, LVS, and HAProxy are chosen according to website scale, outlines their respective strengths and weaknesses, and describes typical deployment stages from simple single‑point setups to complex multi‑layer architectures.
This article explains how Kubernetes routes traffic from a pod to a Service and back to another pod, details the role of kube‑proxy with iptables or ipvs, and discusses how long‑lived connections are managed and potential load‑balancing issues.
This article outlines a practical technology stack and architectural choices—including load balancing, CDN, distributed RPC frameworks, message queues, caching, databases, and search—for building a scalable backend that can support tens of thousands of daily active users in a mid‑size internet company.
The article outlines the characteristics of high‑traffic websites and traces the architectural evolution from a single‑server model to distributed, cache‑enabled, load‑balanced, and service‑oriented designs, highlighting techniques such as clustering, read/write splitting, CDN, NoSQL, and business micro‑services.
This article details the architecture, protocol design, permission control, reliability mechanisms, and scaling strategies of a long‑connection gateway built with OpenResty, Kafka, and Redis, illustrating how to share persistent connections across multiple business services while ensuring high performance and fault tolerance.
This article explains why native Kubernetes Service load balancing is limited, introduces the richer algorithms offered by Alibaba Cloud Service Mesh (ASM) such as RANDOM, ROUND_ROBIN, LEAST_REQUEST, and PEAK_EWMA, and provides a step‑by‑step deployment and testing guide to illustrate their behavior in real scenarios.
The ACM CCS 2023 distinguished paper 'Silence is not Golden: Disrupting the Load Balancing of Authoritative DNS Servers' by Alibaba Cloud and Tsinghua University reveals a novel attack that exploits silent‑response policies of authoritative DNS servers to manipulate load‑balancing in major recursive resolvers, affecting a significant portion of popular domains.
The article analyzes the challenges of scaling network devices to handle ten‑million concurrent connections (C10M) and describes Alibaba's AGW solution, which uses lock‑free data planes, hugepages, NUMA‑aware memory placement, and user‑space NIC drivers to achieve high‑performance four‑layer load balancing.