This article explains what clusters, distributed systems, and microservices are, compares their characteristics such as scalability, high availability, and load balancing, and shows how they complement each other in modern backend architecture.
This article explains how to design a highly scalable system for tens of millions of users by starting with a simple single‑server setup, applying vertical and horizontal scaling, using load balancers, expanding relational databases, choosing between SQL and NoSQL, and employing advanced techniques such as caching, CDN, and GeoDNS.
This article systematically explains the relationships among high concurrency, high availability, performance, and scalability, defines their quantitative metrics, categorizes sources of change that affect system reliability, and outlines strategies for fault prediction, impact reduction, and rapid recovery in large‑scale services.
The article chronicles Tencent’s shift from QQ chat to enterprise‑grade Tencent Cloud IM, showing how a former QQ team built a globally‑scaled 2800‑node acceleration network and self‑designed storage and QUIC‑optimized messaging engine to support hundreds of millions of concurrent users, meet data‑sovereignty rules, and drive digital transformation in e‑commerce, automotive, education and other sectors, now serving over 100,000 clients and a billion users.
The article outlines a comprehensive, multi‑layer architecture—including DNS routing, L4/L7 load balancing, micro‑service or monolithic deployment, caching, database sharding, hybrid‑cloud deployment, elastic scaling, and tiered degradation—to reliably support systems handling from millions to billions of daily active users under sudden traffic spikes.
Gaode Map transformed its navigation and recommendation services by adopting a Serverless, cloud‑native platform that reduces operational costs, enables millisecond‑level scaling, and eliminates the need for on‑site duty during peak holiday periods, while supporting rapid UI and strategy changes.
The article details Meituan's five‑year journey in instant logistics, describing how its distributed high‑concurrency architecture, AI‑driven optimization, micro‑service evolution, and reliability engineering practices have been continuously refined to achieve low latency, high availability, and cost‑effective scaling.
The article describes Meituan's five‑year journey in instant logistics, detailing the challenges of massive order‑rider matching, high traffic spikes, ultra‑low latency requirements, and how a layered, micro‑service‑based distributed architecture combined with AI techniques was progressively adopted to achieve scalability, reliability, and cost efficiency.
This article provides a comprehensive technical overview of large‑scale distributed website architecture, covering characteristics, goals, patterns, high‑performance, high‑availability, scalability, extensibility, security, and agility considerations, and walks through the evolution of an e‑commerce system with concrete examples and diagrams.
This article explains database sharding fundamentals, including terminology, when to adopt sharding, various global ID generation methods such as auto‑increment, UUID, COMB, and Snowflake, different partitioning strategies, challenges like distributed transactions, and practical expansion and migration solutions.
This article details how Vivo's push notification platform leverages Redis for massive message throughput, identifies bottlenecks encountered during peak traffic, and outlines a series of capacity, clustering, hot‑key, and client‑side optimizations that reduced load by up to 15% and improved response times dramatically.
This article details the evolution of an e‑commerce recommendation system through three architectural versions, highlighting the initial simple design, the challenges that prompted vertical and horizontal splits, the introduction of a configurable pipeline and AB testing, and the final micro‑service‑based, dynamically configurable V3.0 architecture.
This article presents thirty concise architectural principles covering simplicity, iterative development, automation, scalability, concurrency, distributed system design, user experience, and practical trade‑offs, offering a comprehensive guide for architects and engineers to build robust, maintainable software.
The article examines synchronous request‑response microservices, outlining their numerous drawbacks such as tight coupling, scalability limits, failure handling, API versioning challenges, data access coupling, distributed monolith risks, and testing difficulties, while also acknowledging their undeniable advantages and the prevalence of hybrid architectures.
When selecting a storage engine, evaluate business metrics such as user and data volume, read/write bias, and consistency needs, then match those requirements to the strengths and limits of relational databases, key‑value caches, column‑stores, document stores, search engines, and other NoSQL options to achieve the right balance of performance, scalability, and operational cost.
The article walks through the challenges of growing data volumes, compares master‑slave, vertical, horizontal, and sharding‑plus‑partitioning architectures, explains their pros and cons, and provides concrete guidance on selecting and implementing a suitable database solution, including middleware options and real‑world case studies.
This article describes the progressive redesign of an e‑commerce recommendation platform—from a simple strategy‑factory V1.0 through a vertically split V2.0 to a fully configurable, pipeline‑driven V3.0—highlighting architectural challenges, Redis clustering, dynamic configuration, recall and prediction services, and future directions for fine‑grained, explainable recommendations.
This article details the three‑stage evolution of an e‑commerce recommendation framework—V1.0’s simple strategy‑factory design, V2.0’s vertical business split, and V3.0’s configurable pipeline with dynamic server‑client configuration, addressing scalability, isolation, and AB‑testing challenges.
The article outlines a comprehensive backend architecture for handling millions of daily active users, covering DNS routing, layer‑4/7 load balancing, monolithic versus microservice deployment, caching, database sharding, hybrid‑cloud strategies, elastic scaling, and multi‑level degradation mechanisms.
The article explains what hybrid cloud is, outlines five typical use cases such as load scaling, disaster recovery, data backup, application deployment, and dev‑test‑prod workflows, and discusses three major challenges including ecosystem innovation, unified multi‑cloud management, and cloud‑network collaboration.
This article details how the Beike instant‑messaging system was analyzed, bottlenecks identified, and a series of backend optimizations—including business isolation, increased concurrency, computation reduction, and Redis connection‑pool redesign—were applied to boost 300‑person group‑chat throughput from 15 QPS to over 320 QPS, achieving more than a twenty‑fold performance gain.
This article recounts Tencent's journey from its legacy TFS storage to the cloud‑native YottaStore system, detailing the technical challenges, strategic decisions, team dynamics, and the impressive scalability, reliability, and cost benefits that now power major Tencent services and external customers.
This article examines the step‑by‑step evolution of the recommendation framework used by a major e‑commerce service, detailing the shortcomings of the initial V1.0 design, the vertical and modular refinements introduced in V2.0, and the dynamic configuration, pipeline, and service‑oriented enhancements implemented in V3.0 to improve scalability, stability, and fine‑grained experimentation.
This article details how Baidu's search middle platform migrated from script‑based processing to a serverless business‑framework architecture, outlining the technical challenges, design of data ingestion, processing, scheduling, and control layers, and summarizing the efficiency, cost, and performance gains achieved.
This talk introduces the motivation, design, theoretical analysis, and extensive experimental results of Tencent Angel Graph's Graph Attention Multi‑Layer Perceptron (GAMLP) and Node‑Dependent Local Smoothing (NDLS), which address GNN scalability and flexibility by using node‑wise adaptive propagation, attention‑based feature fusion, and a lightweight training pipeline.
This presentation introduces Tencent Angel Graph's NDLS and GAMLP techniques that address GNN scalability and flexibility by adaptively selecting propagation depth per node, employing node‑wise feature and label propagation with attention mechanisms, and demonstrating superior performance on large‑scale and sparse graph benchmarks.
The article outlines a comprehensive backend architecture for handling million‑level daily active users, covering DNS routing, L4/L7 load balancing, monolithic versus microservice deployment, caching, database sharding, hybrid‑cloud deployment, elastic scaling, and multi‑level degradation strategies to ensure high availability under sudden traffic spikes.
This article explains why deploying Kubernetes on bare‑metal servers offers six key benefits—simpler networking, better cost efficiency for demanding workloads, superior performance, stronger security, workload‑specific optimization, and freedom from vendor lock‑in—making it a smarter choice than virtual‑machine‑based solutions.
This article explains SaaS as a software‑delivery model, outlines its presentation, scheduling, business, and data layers, describes essential components such as security, data isolation, configurability, scalability, zero‑downtime upgrades, and multi‑tenant support, and details maturity levels, storage options, tenant identification, and performance optimizations.
This article walks through the step‑by‑step evolution of a basic single‑server MVP architecture into a large‑scale distributed system, using a simulated Taobao example to illustrate ten‑plus architectural stages, key technologies, design principles, and the eventual shift to cloud‑native microservices.
This article explains the role, challenges, and solution of JD Daojia's business gateway, detailing how it aggregates multiple backend services, adopts workflow orchestration to improve code consistency, scalability, and development efficiency, and outlines future architectural considerations.
A group of e‑commerce engineers share their real‑world experiences on selecting technologies, designing architectures, handling rapid growth, and avoiding common mistakes when building a new online store from scratch, offering practical guidance on infrastructure, DevOps, and team organization.
This article explains microservice fundamentals, outlines their advantages and technical traits, and provides practical guidance on data design, database selection, polyglot persistence, scaling strategies, and why MongoDB often fits microservice architectures best.
This article explains what Serverless architecture is, compares it with traditional monolithic setups, outlines its cost and scalability benefits, discusses its drawbacks, and provides a practical guide on the knowledge and tools needed to build Serverless solutions in production.
This article outlines the functional and non‑functional requirements, traffic calculations, service decomposition, and detailed microservice designs needed to build a highly available, scalable Twitter‑style system using distributed caches, databases, and asynchronous processing.
The article examines the definition, pain points, and industry approaches to managing ultra‑complex microservice call networks, highlighting ByteDance's layered architecture, traffic identity marking, and practical recommendations for scaling and governing massive service ecosystems.
The article explains what multi‑cloud means, why it matters for scalability, security and cost management, and outlines a four‑step approach to designing and measuring an effective multi‑cloud strategy for modern enterprises.
This article explains how to transform product requirements into robust technical architectures by addressing uncertainty through strategic principles—suitability, simplicity, evolution—and tactical guidelines covering high concurrency, high availability, and business design, illustrated with logical and physical diagrams.
This article explains microservice fundamentals, outlines their advantages, and dives deep into data‑design considerations such as one‑database‑per‑service, polyglot persistence versus multi‑model databases, and why MongoDB’s dynamic schema, change streams, and sharding make it a strong fit for scalable microservice architectures.
This article explains microservice fundamentals, their advantages, technical characteristics, and detailed data‑design considerations, comparing shared versus per‑service databases, polyglot persistence versus multi‑model databases, and demonstrates why MongoDB is a strong fit for scalable, resilient microservice architectures.
This article explains the fundamentals of load balancing, covering why it is needed for high‑traffic services, the difference between vertical and horizontal scaling, various load‑balancing techniques (DNS, HTTP, IP, link‑layer, hybrid), common algorithms, and the trade‑offs of software versus hardware solutions.
This article explores how integrating Serverless into SaaS platforms can simplify operations, improve tenant isolation, reduce costs, and enable scalable multi‑tenant architectures that better serve large enterprises while addressing the challenges faced by both SaaS providers and Serverless services.
Designing a distributed system involves overcoming major challenges such as heterogeneity, transparency, openness, concurrency, security, scalability, and fault tolerance, each of which must be addressed to build a reliable, extensible, and performant system.
This article presents a comprehensive, practical design for an ultra‑large‑scale user center, covering microservice architecture, API separation, token generation with graceful degradation, data‑sharding strategies, password encryption, asynchronous processing, and detailed monitoring to ensure high availability, performance, and security.
This article details the architecture, data flow, module responsibilities, and successive optimizations of Baidu's short‑video push system, covering personalized timing estimation, user‑group management, frequency‑control redesign, and protobuf‑based compression to handle billion‑scale traffic efficiently.
This article explains how to design and evolve server architectures, load‑balancing, database clustering, caching, message queues, and other techniques to handle high‑concurrency scenarios such as flash sales and timed red‑packet distribution in large‑scale e‑commerce systems.
This article presents a comprehensive set of design practices for building a highly available, high‑performance, and secure user‑center system that can handle hundreds of millions of users, covering service architecture, API design, token degradation, data sharding, security, asynchronous processing, and monitoring.
Zhihu’s Moneta service stores over a trillion rows and faces massive write and read loads; this article explains why TiDB was chosen, how its architecture and features such as HTAP, Raft, Titan and table partitioning enable millisecond‑level query latency, high availability, and seamless scaling.
Large‑scale website architecture must balance massive user traffic, data volume, security threats, and rapid feature changes by adopting layered, distributed designs that emphasize high performance, high availability, scalability, extensibility, and agility, employing techniques such as caching, load balancing, clustering, sharding, and service‑oriented components.
The article explains how shifting complex filtering, validation, and join operations from the database to the application layer reduces scarce database resource usage, improves scalability, and enables more flexible resource allocation for modern web applications.
This article provides a comprehensive technical summary of large‑scale distributed website architecture, covering characteristics, goals, architectural patterns, performance, high‑availability, scalability, extensibility, security, agility, and a detailed evolution roadmap with practical examples and recommendations.
This article explains how to evolve a large‑scale website architecture through stages such as initial single‑server setups, application‑data separation, caching, server clustering, read‑write separation, CDN/reverse proxy, distributed storage, micro‑services, and automation to achieve high availability, scalability, performance and security.
This article analyzes the evolution of large‑scale website architecture, covering stages from single‑server setups to layered, distributed, and clustered designs, and explains how caching, read‑write separation, CDN, asynchronous messaging, redundancy, automation, and security collectively achieve high performance, availability, scalability, and extensibility.
This article provides a thorough overview of distributed systems, explaining their definition, core concepts such as partition and replication, key challenges, essential characteristics, typical components and protocols, a practical request flow example, and a curated list of real‑world implementations to help readers build a solid learning roadmap.
This article provides a comprehensive overview of software architecture, covering its definition, essential concepts such as systems, subsystems, modules, and frameworks, various architectural layers and classifications, evolution from monolithic to microservices, design principles, evaluation criteria, and typical misconceptions to avoid.
This article provides a comprehensive overview of the design principles, architectural patterns, performance, availability, scalability, security, and operational considerations for building large distributed web sites, illustrated with a step‑by‑step evolution from a single‑server setup to a multi‑layer, cloud‑native architecture.
This article presents a comprehensive engineering guide for building a high‑availability, high‑performance, and secure user‑center system that can serve hundreds of millions of users, covering service architecture, API design, sharding, token fallback, data protection, asynchronous processing, and observability.
This article explores how to design a cloud‑native distributed database architecture by examining TiDB’s current structure, proposing a storage‑compute separation that leverages cloud services like S3 and EBS, and discussing implications for cost, scalability, fault‑tolerance, and multi‑tenant deployment.
This article explores how to design a cloud‑native distributed database architecture using TiDB as a case study, discussing cost reduction, storage choices, compute‑storage separation, fault tolerance, scaling strategies, and the trade‑offs of caching and persistent storage in modern cloud environments.
The article details Tencent Cloud's TDSQL‑C database, explaining traditional database limitations, its cloud‑native architecture, four standout capabilities such as petabyte storage and serverless billing, and the extensive kernel optimizations that enable rapid scaling, backup, indexing, and future cross‑region reads.
The article details Tencent Cloud's TDSQL‑C cloud‑native database, explaining traditional database bottlenecks, its four standout features—PB‑level storage, second‑level scaling, rapid snapshot backup, and serverless pay‑as‑you‑go—and the deep kernel optimizations that enable these capabilities while outlining future performance and cross‑region goals.
This article explains why and how to apply vertical (business‑oriented) and horizontal (data‑oriented) sharding, covering single‑database, table splitting, database splitting, combined sharding, read‑write separation, routing algorithms, and real‑world case studies to improve scalability and performance.
This article examines cloud computing’s core principle of using interchangeable machines, compares parallel‑first and single‑storage‑first database architectures, outlines the advantages such as scalability, cost efficiency, and integration, and discusses the weaknesses including maturity gaps, latency, and vendor lock‑in.
This article explains the concepts, characteristics, and architectural design of a flash‑sale (秒杀) system, covering rate‑limiting, peak‑shaving, asynchronous processing, caching, scalability, and concrete Redis‑based implementation details for handling massive concurrent requests.
This article explores how to transform product requirements into robust technical architectures by outlining strategic principles—appropriateness, simplicity, evolution—and tactical guidelines such as high concurrency, high availability, and business design, while addressing uncertainty, component complexity, and practical implementation with Java‑centric examples.
The article explains the AKF microservice splitting principle, describing how X‑axis horizontal replication, Y‑axis business‑oriented partitioning, and Z‑axis data‑oriented partitioning together address single‑point failures, capacity limits, and performance bottlenecks in clustered backend systems.
This article examines the disadvantages of serverless web development—including vendor lock‑in, unpredictable costs, and integration complexity—while outlining the scenarios where serverless offers clear benefits such as rapid iteration, low upfront investment, and automatic scaling for small‑to‑medium applications.
This article compiles Baidu engineers' QCon 2021 talks, covering micro‑service evolution, large‑scale container elastic scaling, search system elasticity, AI‑chip deployment at massive scale, and cost‑focused monitoring, each with abstracts, outlines and key takeaways for practitioners.
This article explains why and how to split databases and tables in high‑concurrency systems, covering vertical (business‑domain) and horizontal (data‑volume) sharding, practical architectures, read‑write separation, routing algorithms, and real‑world case studies from gaming, membership points, and restaurant ordering platforms.
Cloud‑native storage is a set of storage technologies designed for cloud‑native environments, offering high availability, scalability, performance, consistency, durability, and dynamic deployment options across public, private, and on‑premises solutions, and addressing the unique challenges of stateful applications running on Kubernetes and similar platforms.
Alibaba’s AServer access gateway, handling billions of users and millions of QPS, transitioned from a monolithic tengine‑based system to a cloud‑native, containerized architecture with Kubernetes, Pilot, and Envoy, improving operational complexity, dynamic routing, traffic isolation, and scalability for massive e‑commerce traffic.
This article explains micro‑frontend architecture, its roots in micro‑services, core principles such as technical independence and team isolation, and outlines the advantages—including scalability, independent deployment, and easier testing—while advising when the approach is appropriate for a project.
This article defines hybrid cloud as an IT architecture interconnecting multiple clouds, distinguishes it from multi‑cloud, examines four common hybrid forms, outlines key characteristics such as elasticity, scalability and security, and presents the five‑connectivity design goals that make hybrid cloud the cornerstone of new infrastructure.
This article explains how to build a highly available, scalable system by decoupling components, adding redundancy, choosing appropriate scaling strategies, employing load balancers, caching, CDN, database replication, sharding, and stateless design to support over 100 million users.
This article provides a comprehensive overview of large‑scale distributed website architecture, covering its characteristics, design goals, architectural patterns, performance, high‑availability, scalability, extensibility, security, agility, evolution stages, and practical implementation techniques such as caching, load balancing, database sharding, service‑orientation and message queues.
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 explains the concepts, characteristics, and practical scenarios of vertical and horizontal table partitioning as well as vertical and horizontal database sharding in MySQL, helping developers decide when and how to apply each strategy for large‑scale applications.
This article outlines essential strategic and tactical principles for technical architecture, addressing uncertainty in technology choices, and detailing the suitability, simplicity, and evolution principles, as well as high‑concurrency, high‑availability, and business design guidelines to build stable, scalable systems.
Node.js offers unparalleled advantages for real‑time application development—including single‑language JavaScript, cost‑effectiveness, modular architecture, event‑driven non‑blocking I/O, rapid development, SEO friendliness, and easy scalability—making it the preferred framework for live video, IoT, notifications, and instant messaging solutions.
This article explains microservice fundamentals, their advantages, technical characteristics, and provides a comprehensive guide to data design in microservice architectures, covering decoupling, lightweight APIs, continuous delivery, database per service versus shared databases, polyglot persistence, scaling strategies, and why MongoDB is a suitable choice.
This article explains how to decide between database and table sharding, describes vertical, horizontal, and range partitioning techniques, discusses their trade‑offs and implementation details, and offers practical guidance for solving query challenges in high‑traffic, write‑intensive systems.
This article examines the fundamental characteristics of Redis, explains why network latency often dominates performance, and presents practical optimization strategies such as using Unix IPC, multi-key commands, transactions, scripts, pipelining, avoiding slow commands, tuning persistence, adjusting OS settings, and adopting distributed architectures to achieve higher throughput and lower latency.
This article provides a comprehensive technical overview of large-scale distributed website architecture, detailing its characteristics, goals, layered design patterns, performance and high‑availability optimizations, scalability strategies, extensibility practices, security measures, agile management, and evolutionary case studies for e‑commerce platforms.
This article analyzes Elasticsearch’s distributed architecture, explaining core concepts such as nodes, indices, shards and replicas, comparing mixed and layered deployment models, and discussing data‑layer design choices and their trade‑offs in modern distributed storage and search systems.
This article provides a comprehensive technical overview of large‑scale distributed website architecture, covering its characteristics, design goals, architectural patterns, performance, high availability, scalability, extensibility, security, agility, and a detailed example evolution from a single‑server setup to a multi‑layer, service‑oriented system.
The Xianyu instant‑messaging system evolved from a 2014 MVP to a robust, multi‑version architecture—adding distributed storage, hybrid sync, ACK‑based delivery, and feature‑driven monitoring—to handle billions of messages, improve stability, and boost user satisfaction, cutting technical complaints by half.
This article examines the core challenges of running large‑scale A/B testing platforms—supporting thousands of engineers, generating fast reports from massive data sets, and reducing sampling variance—to enable data‑driven product decisions in the AI era.
This article examines essential considerations such as data volume, personnel support, scalability, and pricing models when selecting a data warehouse solution, comparing on‑premise options with modern cloud services like Redshift, BigQuery, and Snowflake for various workload sizes.
The article outlines six fundamental traits of serverless architecture—low barrier-to-entry, hostless, stateless, elasticity, distributed, and event-driven—explains why they matter, discusses the benefits and hidden challenges each introduces, and offers concise recommendations for developers to successfully adopt serverless solutions.
This article explains how Redis Cluster uses hash slots for data partitioning, enables near‑linear scaling and fault‑tolerant failover through master‑slave replication, and requires client‑side routing support, while discussing the trade‑off between performance and consistency in distributed systems.
The article outlines the defining traits of large-scale websites—high concurrency, massive data, 24/7 availability, security, and rapid iteration—and discusses major technical challenges such as scaling, caching, clustering, database read/write separation, CDN acceleration, distributed storage, and service decomposition.
This article explains the fundamentals of load balancing, why a single entry point is needed for multi‑server deployments, how different network layers (L2‑L7) implement balancing, and the practical trade‑offs of hardware versus software solutions such as Nginx, HAProxy, and LVS.
Tencent Docs was completely rebuilt on a modular, serverless architecture that integrates micro‑services such as SSR, OCR and plugin back‑ends, enabling automatic scaling for traffic spikes, versioned gray releases, pay‑per‑use cost savings, and faster development cycles for its tens‑of‑millions‑user base.
This article explains how object storage emerged as a cloud-native solution that surpasses traditional DAS, SAN, and NAS architectures by offering virtually unlimited capacity, robust metadata handling, and simple RESTful APIs for modern applications and large‑scale data workloads.
The article outlines four essential cloud‑application design dimensions—scalability, availability, manageability, and feasibility—providing discussion points and questions for each to guide stakeholders toward robust, cost‑effective, and secure cloud solutions through comprehensive evaluation of capacity, platform constraints, load handling, SLA commitments, disaster recovery, performance tuning, and security considerations.
The article details Meituan’s five‑year evolution of its instant logistics platform, describing the distributed backend architecture, AI‑driven optimization, scalability and high‑availability practices, as well as future challenges in microservice complexity and operational automation.
This guide explains how to build a highly available, scalable architecture for supporting hundreds of millions of users, covering decoupling, redundancy, vertical and horizontal scaling, load balancing, database replication, sharding, caching, CDN, GeoDNS, and best practices for progressive system expansion.
The article explains what high concurrency means, outlines key performance metrics such as response time, throughput, QPS, TPS and concurrent users, and presents vertical and horizontal scaling techniques—including hardware upgrades, caching, load balancing, sharding, micro‑services, multithreading and CDN—to improve a system's ability to handle massive parallel requests.
The article compiles expert experiences from major Chinese tech firms on progressive system refactoring, platform‑centric redesign, service‑oriented evolution, and high‑performance architecture, highlighting practical steps, technology choices, and lessons learned for modern backend and operations engineering.
This article explains the fundamentals of microservices architecture, compares it with monolithic (integrated) systems, outlines the problems solved by microservices, details their advantages and disadvantages, provides a practical Java Spring example with code snippets, and discusses strategies for service decomposition and migration.
