This article summarizes the evolution stages, architectural patterns, and key concerns such as performance, scalability, extensibility, high availability, and distributed design that large‑scale websites must address, providing practical insights and visual diagrams for each concept.
This article summarizes the origins, core principles, typical evolution stages, and common toolkits of large website architecture, highlighting how network growth, performance demands, and scalability challenges drive the adoption of caching, load balancing, database sharding, CDNs, and distributed services.
This article explains the relationships among Storm's core components, how parallelism is calculated from configuration parameters, and how Nimbus performs task assignment and load balancing across workers, supervisors, and executors in a distributed streaming topology.
This article reviews Alibaba Cloud's high‑performance load‑balancing solution, explaining the evolution from basic load‑balancing concepts to the architecture of LVS and Tengine, detailing their modes, optimizations, high‑availability designs across groups, AZs and regions, and outlining current use cases and future directions.
This article presents a step‑by‑step operations‑focused roadmap for evolving a website from a single‑server prototype to a highly available, horizontally scalable architecture using load balancing, caching, database replication, service‑oriented design, DNS round‑robin, CDN, and disaster‑recovery techniques.
This article explains how website systems achieve scalability through architectural designs such as physical function separation, server clustering, various load‑balancing techniques, distributed cache mechanisms, and both relational and NoSQL database scaling methods, providing practical guidance for large‑scale web deployments.
The article outlines the progressive architectural stages of large‑scale websites—starting with a single‑server setup and advancing through service separation, caching, load balancing, database read/write splitting, CDN/reverse proxy, distributed storage, NoSQL, business splitting, and distributed services—to illustrate how high concurrency, massive traffic, high availability, and massive data are handled.
The article reviews hardware and software load‑balancing, explains classic strategies such as round‑robin, random, minimum‑response‑time, least‑connections and hash, and quantitatively evaluates their fault‑tolerance using probability formulas and example scenarios in distributed systems.
This article chronicles the step‑by‑step evolution of a LNMP‑based website, detailing how increasing traffic drove architectural changes such as separating web and database servers, adding memcached, implementing MySQL master‑slave replication, load balancing, NFS sharing, and finally integrating NoSQL caching to handle millions of daily visits.
This article summarizes the evolution, patterns, and five core factors—performance, availability, scalability, extensibility, and security—of large‑scale website architecture, covering server tiers, caching, clustering, load balancing, data redundancy, and security measures.
Google’s internal Maglev load balancer, described in a recent research paper, bypasses the kernel to operate directly on the NIC, uses ECMP routing, consistent hashing, and memory‑shared queues to achieve sub‑microsecond packet processing while scaling horizontally across clusters.
The article outlines how mature large‑site architectures evolve from a single‑server setup to multi‑layered systems featuring separated application, data and file tiers, caching, load‑balancing, database sharding, CDN, distributed file systems, NoSQL/search, business‑level service decomposition and distributed service frameworks.
This article explains the fundamentals of load balancing, compares common techniques such as DNS round‑robin, hardware and software load balancers, discusses their advantages and drawbacks, and introduces Alibaba's VIPServer as a mid‑tier, seven‑layer load‑balancing solution with advanced health‑check and traffic‑routing features.
This article explains load balancing fundamentals, differentiates layer‑4 and layer‑7 balancing, describes hardware and software solutions, local and global deployment, various algorithms and health‑check methods, and discusses performance, scalability, security, and management considerations for modern network operations.
This article explains how to design and optimize web system architecture—including load‑balancing methods, multi‑level caching, MySQL scaling, distributed deployment, and disaster‑recovery techniques—to handle traffic growth from hundreds of thousands to hundreds of millions of daily visits.
This article traces the historical progression of game server architectures—from simple HTTP‑based servers for low‑interaction mobile games, through the first‑generation MUDOS engine, second‑generation database‑driven designs, third‑generation seamless world nodes with dynamic load balancing, to specialized Battle.net, casual, and modern action MMO server models—highlighting the technical motivations and challenges at each stage.
The article details Meizu's large‑scale real‑time push architecture, covering system scale, four‑layer design, mobile power‑saving optimizations, network instability handling, massive connection techniques, load‑balancing strategies, comprehensive monitoring, and gray‑release deployment practices.
This article explains how increasing consumers affects RocketMQ message backlog, details conditions where adding consumers helps or not, describes ProcessQueue flow control, outlines six load‑balancing strategies—including average, round‑robin, custom, machine‑room, nearby, and consistent‑hash—and provides corresponding Java code examples.
This article explains how to streamline OpenFeign usage during local development by creating a custom ImportBeanDefinitionRegistrar that registers Feign clients with configurable URLs, avoiding manual URL changes in annotations and ensuring seamless switching between local and production environments.
This article explains the challenges of using WebSocket in a microservice environment, introduces a load‑balancing library that forwards messages between service instances, shows how to enable it with Spring annotations, and details the underlying connection, subscription, and selector mechanisms for reliable message routing.