This article details how MaFengWo’s payment center evolved from a simple 1.0 implementation to a robust 2.0 architecture, covering core capabilities, modular design, monitoring, and the operational lessons learned for building a high‑availability, scalable payment platform.
This article explains how to design a high‑performance feed‑stream architecture—including product definition, data modeling, storage choices, synchronization modes, metadata handling, commenting, likes, sorting, search, and deletion—so that a system can support tens of millions to billions of users while remaining reliable and scalable.
This article uses Taobao as a case study to trace the evolution of its server‑side architecture from a single‑machine setup to a cloud‑native, micro‑service ecosystem, detailing each scaling milestone, the technologies involved, and the design principles that guide high‑availability, high‑concurrency systems.
This article reviews the Twelve-Factor App methodology, outlining twelve essential guidelines—including codebase management, explicit dependencies, configuration separation, backing services, build‑release‑run workflow, stateless processes, port binding, concurrency, disposability, environment parity, logging, and admin processes—to help developers design resilient, cloud‑native applications.
This article explains why Medium transitioned from a monolithic Node.js application to a microservice architecture, outlines the three core design principles, shares practical strategies for service creation, decoupling, observability, deployment, and how to avoid common microservice pitfalls.
This article explores Hadoop’s role in the big‑data era, detailing its architecture, core components such as HDFS, YARN, MapReduce, Ozone and Submarine, the challenges of trillion‑scale data, and why its scalability, cost efficiency, and a mature ecosystem give it a competitive edge.
This article uses Taobao as a case study to trace the evolution of a backend system from a single‑machine setup to a multi‑layer, highly available, horizontally scalable architecture that can handle tens of millions of concurrent users, summarizing key technologies and design principles at each stage.
This resource compiles a complete series of articles on distributed system theory covering consistency, consensus, high availability, scalability, performance, testing, and operations, offering both quick overviews for newcomers and in‑depth readings for practitioners seeking to master modern distributed architectures.
This article explains how Zhihu designed a scalable long‑connection gateway that decouples business logic via a publish‑subscribe model, implements ACL‑based authorization, ensures message reliability with acknowledgments and sliding windows, and leverages OpenResty, Redis, and Kafka for load‑balanced, fault‑tolerant backend services.
This article categorizes high‑concurrency challenges into read‑heavy and write‑heavy scenarios and presents practical strategies such as caching, sharding, asynchronous processing, batch operations, and architectural patterns to improve scalability and performance of backend systems.
This article uses Taobao as a case study to illustrate how a web service evolves from a single‑machine setup to a cloud‑native, micro‑service architecture capable of handling tens of millions of concurrent requests, detailing each technical milestone and the principles behind the design choices.
This article uses Taobao as a case study to trace the step‑by‑step evolution of server‑side architecture from a single‑machine deployment to distributed clusters, caching, load‑balancing, database sharding, micro‑services, containerization and finally cloud platforms, summarizing the key technologies and design principles at each stage.
This article explains how Weibo's video team designs a highly available, high‑concurrency architecture for short‑video services, covering team responsibilities, business scenarios, microservice design, caching layers, multi‑data‑center HA, and circuit‑breaker mechanisms to sustain unpredictable traffic spikes.
The article explains the Louvain community‑detection algorithm, detailing its modularity‑maximizing objective, two‑step iterative process, efficient graph data structures, practical implementation considerations, and performance results on large‑scale graphs, providing a comprehensive guide for practitioners.
The article describes a scalable placement system for Xianyu that links front‑end resource slots with multiple backend data sources via a visual‑schema‑driven API, enabling personalized banner and feed content, batch request optimization, rapid campaign management, and reduced developer effort while serving millions of users daily.
This article details Didi's evolution from a self‑built NoSQL system called Fusion to a NewSQL solution and outlines the challenges, architectural highlights, data migration mechanisms, and future distributed database design, providing concrete metrics, diagrams, and practical lessons learned.
This article presents a hybrid sharding approach that combines range partitioning to assign ID ranges to groups and hash modulo on the total number of tables to achieve uniform data distribution while avoiding hotspots and eliminating the need for data migration during scaling.
The article introduces the Cube Model for scalable microservice architectures, explaining how X‑axis (horizontal scaling), Y‑axis (functional decomposition) and Z‑axis (data partitioning and isolation) expansions address capacity, complexity, and differentiated service demands in high‑traffic distributed systems.
The article explains common database performance bottlenecks such as I/O and CPU limits, and details horizontal and vertical sharding techniques—including database and table partitioning—along with tools, implementation steps, common issues, scaling strategies, and practical examples for improving scalability and reliability.
This article explains how to build high‑performance, highly‑available, scalable, extensible, and secure recommendation services by outlining background concepts, defining quality criteria, discussing design challenges, and presenting concrete architectural principles and practical strategies.
This article examines core database architecture principles—high availability, performance, consistency, and scalability—and compares four common deployment patterns (primary‑standby, dual‑primary, primary‑replica with read/write separation, and a hybrid dual‑primary/replica design), followed by detailed consistency solutions and practical insights for real‑world implementation.
This article explains vertical and horizontal database partitioning, compares hash‑modulo and range sharding schemes, and proposes a hybrid approach that balances load, prevents hotspots, and eliminates the need for costly data migrations during scaling.
This article reviews the evolution of Youzan's order search architecture over two years, detailing challenges from data growth, the creation of a hot‑state index covering half of search traffic, time‑sharded indexes, and the AKF expansion cube that guides multi‑axis scalability.
Load balancing distributes incoming traffic across multiple servers to improve performance, ensure high availability, and enable scalability, and this article explains its core principles, various classifications such as DNS, IP, layer‑2 and hybrid methods, and common algorithms like round‑robin, least connections, hash and weighted distribution.
This comprehensive guide explains why load balancing is essential for high‑traffic websites, details vertical and horizontal scaling, compares DNS, IP, link‑layer, and hybrid approaches, outlines common algorithms such as round‑robin and weighted, and reviews hardware versus software solutions.
This article outlines three core architecture design principles—appropriateness, simplicity, and evolution—illustrated with Taobao’s journey from a simple PHP site to a sophisticated, self‑developed distributed system, showing how fitting solutions, keeping designs simple, and iteratively evolving with business needs lead to sustainable scalability.
OceanBase, a fully proprietary distributed NewSQL database, has evolved over eight years to support high‑availability, strong consistency via Paxos, flexible replica management, OBProxy routing, LSM‑Tree storage, and migration tools, enabling seamless scaling, disaster recovery, and Oracle compatibility for large‑scale financial services.
The article chronicles the design, implementation, and iterative evolution of JD Digital Technology’s in‑house host monitoring platform Diting, detailing its V1, V2, and V3 architectures, the challenges encountered at each stage, and future directions toward intelligent, automated operations.
This article details NetEase's journey in designing and implementing a large‑scale database automation platform, covering its requirements, tool‑based operations, architecture, AIOps integration, and the practical lessons learned for managing thousands of database clusters efficiently.
The 2019 Alipay New Year "Five Blessings" red‑envelope campaign, serving 450 million users, leveraged Ant Financial's GeaBase distributed graph database, a real‑time data‑intelligence platform, and OceanBase elastic resources to achieve millisecond‑level ranking, seconds‑level transaction audit, and seamless high‑concurrency performance.
Facing metadata inconsistency, ten‑thousand‑device scale, and the need for intelligent, event‑driven automation, Tencent Cloud Redis’s sole operations lead built a unified DB‑CMDB, a job‑platform for reusable workflows, and AI‑assisted scheduling, transforming DBAs into developer‑operators and driving 300% efficiency gains.
This article outlines Meituan’s transition of its database platform from manual, script‑based operations through tool‑ and product‑centric stages to a private‑cloud and automation era, discusses current challenges such as root‑cause analysis and staffing, and shares insights on moving toward fully intelligent, data‑driven database operations.
This article provides a thorough introduction to distributed systems, covering fundamental theories such as nodes, networks, time, ordering, consistency models (CAP, ACID, BASE), design patterns, scenario classifications, engineering practices, and the full technology stack needed to build and operate microservice‑based distributed applications.
Database sharding, a horizontal partitioning technique that splits a table’s rows across multiple nodes, enables scalable performance and fault isolation for high‑traffic applications, but introduces complexity, potential data imbalance, and recovery challenges, so it should be adopted only after simpler optimizations are exhausted.
This article explains how isolating systems and resources—through thread, process, cluster, data‑center, read/write, static/dynamic, crawler, hotspot, and resource isolation—prevents cascading failures and improves availability, scalability, and performance in high‑traffic applications.
This article recounts the evolution of Youzan's internal search platform—from a simple Elasticsearch cluster in 2015 through multiple architectural revisions, advanced query middleware, big‑data integration, and a proxy‑based service layer—highlighting the technical challenges and solutions that enabled scalable, reliable search for billions of records.
This article demonstrates how MySQL partition tables dramatically improve query speed for large datasets, compares partition-key, secondary-index, and full‑scan queries, outlines the practical performance gains, and details the numerous limitations and trade‑offs that influence when to adopt partitioning versus sharding.
This article explains the concept of state in software, contrasts stateful and stateless designs, and shows how moving state handling to the client or shared storage improves scalability, fault tolerance, and maintainability in distributed backend systems.
The article traces the evolution of backend services from monolithic applications through RPC-based scaling and database sharding, explains why sharding alone cannot achieve unlimited scalability due to connection limits, and proposes a unitized architecture that partitions databases per service to overcome these constraints.
The paper presents a highly scalable, low‑overhead Host‑based Intrusion Detection System architecture designed for hundreds of thousands of servers, emphasizing cluster high‑availability, strong consistency via a CP‑oriented etcd backend, Go‑based agents with efficient resource management, modular sandboxing, and robust process monitoring to ensure reliable, secure operation at massive scale.
Designing high‑concurrency applications requires adopting stateless services, modular decomposition, service‑oriented architecture, message queues, data heterogeneity handling, multi‑layer caching, and parallel processing, each illustrated with practical e‑commerce examples that balance scalability, fault tolerance, and eventual consistency.
The article examines how architects of large-scale systems like eBay and Amazon forgo traditional ACID transactions in favor of BASE principles, balancing consistency, availability, and scalability through application‑level designs, async processing, and strategic trade‑offs informed by the CAP theorem.
Discover 15 timeless architecture principles—from redundancy and rollback design to monitoring, horizontal scaling, and non‑intrusive components—that guide engineers in creating robust, scalable, and maintainable systems while balancing cost, risk, and future growth.
Software architecture defines the structural skeleton of a system, encompassing components, connectors, constraints, and guiding principles; this article explains its essence, various classifications—from business to deployment—and offers practical criteria for assessing stability, efficiency, and security in modern server‑based applications.
This article examines the benefits and drawbacks of database foreign key constraints, highlighting issues such as performance overhead, concurrency bottlenecks, scalability limitations, and increased operational complexity, and argues why handling relationships in the application layer is often preferable.
Meltwater’s media‑monitoring platform runs a custom Elasticsearch 1.7.6 cluster of over 400 nodes on AWS, handling 200 TB of primary data and 3 million daily documents while serving thousands of complex queries per minute, achieved through careful shard design, master‑node configuration, extensive performance tuning, and automated provisioning.
This article explains the design of a highly extensible, configurable marketing engine that handles complex business scenarios, supports massive concurrent requests, and provides comprehensive tooling for activity configuration, reward distribution, and real‑time monitoring.
The article uses a restaurant scenario to explain the differences between centralized, cluster, and distributed system deployments, illustrating how performance, security, scalability, and availability map to user requirements and why scaling from a single server to clusters and distributed architectures is essential as demand grows.
The article examines a real‑world Spring Cloud microservice case where naive timeout extensions mask deep performance issues, explains how massive data growth and complex SQL cause thread‑pool exhaustion, and provides step‑by‑step optimizations—including query refactoring, proper timeout settings, retries, and idempotency—to restore stability under high concurrency.
The article outlines how increasing business complexity and throughput demands drive the need for system splitting, architectural upgrades, and micro‑service adoption, detailing horizontal scaling, vertical and business partitioning, database sharding, and the evolution toward resilient, high‑performance backend infrastructures.
This article details how JD Daojia's order center migrated from MySQL to a multi‑stage Elasticsearch cluster—covering initial deployment, isolation, replica tuning, primary‑secondary setup, real‑time dual‑cluster upgrades, data synchronization methods, and key pitfalls—to achieve massive scalability, high availability, and performance for billions of orders.
Learn how response time (RT), queries per second (QPS), concurrent user count, and optimal thread settings interrelate, using a Disney park analogy to illustrate calculation methods and performance tuning strategies for web applications.
Microservice architecture, likened to the human body's independent systems, breaks monolithic applications into loosely‑coupled, high‑cohesion services with isolated data stores and well‑designed APIs, enabling flexibility, scalability, and continuous delivery, while requiring careful scope definition, automation, monitoring, and handling of added DevOps complexity.
This article explains why modern applications dealing with massive user, order, and transaction data must move beyond single‑table designs, compares partitioning, sharding (分库分表), and NoSQL/NewSQL solutions, and provides practical guidance on choosing middleware, sharding columns, and hybrid architectures such as es + HBase.
From its humble 2009 launch to the 2018 tenth anniversary, Alibaba’s Double 11 shopping festival evolved through relentless technical challenges—system crashes, CDN bottlenecks, over‑selling bugs, and massive load‑testing innovations—offering a decade‑long case study in operations, scalability, and resilience for large‑scale e‑commerce platforms.
This article explains load balancing as a clustering technology that distributes network services across multiple devices or links to improve performance, scalability, reliability, and manageability, and it details various types, strategies, and algorithms used in modern networks.
From the humble 2009 launch of Double 11 to the massive, cloud-native, multi-region architecture of 2018, Alibaba’s engineers chronicle yearly technical hurdles—traffic spikes, system crashes, CDN limits, over-selling, and the evolution of stress-testing, capacity planning, and operational safeguards that turned the shopping festival into a global engineering showcase.
This article describes the architecture, design requirements, and implementation of a modular transaction settlement testing system that separates testing from order modules, supports flexible split‑payment configurations, and ensures accurate fund flow verification across various business scenarios.
This article explains what load balancing is, compares it to navigation routing, and details five common strategies—round‑robin, weighted round‑robin, least connections, fastest response, and hash‑based—along with their pros, use‑cases, and health‑check mechanisms for achieving high availability.
This article outlines the progressive evolution of large‑scale web architectures—from monolithic mainframe‑style deployments to separated application and database servers, clustering, load balancing, read/write splitting, search integration, caching, sharding, and finally micro‑service decomposition—illustrated with a simple Java‑based e‑commerce example.
This article narrates the step‑by‑step evolution of a cross‑border e‑commerce logistics platform, detailing how its backend architecture was repeatedly redesigned—from a simple 1.0 system to a robust, fault‑tolerant 3.0 solution—driven by growing business needs, performance challenges, and reliability lessons.
In the era of big data, DBAs face higher demands and NoSQL technologies have risen, so this article shares GeTui's KV storage architecture evolution, operational challenges, NoSQL selection criteria, Codis+ enhancements, Aerospike evaluation, monitoring practices, and best‑practice recommendations for scalable database operations.
iQIYI migrated its critical Edge Control, Video Transcoding, and User Login services from MySQL to TiDB, gaining automatic sharding, high‑availability multi‑datacenter replication, and stable query performance that eliminated storage bottlenecks, complex sharding logic and frequent downtime, while enabling future OLTP/OLAP integration.
The article outlines how a startup’s web architecture evolves through five major phases—migrating from PHP to Java, adopting distributed micro‑services, enabling mobile access, building a mid‑platform layer, and finally internationalizing the system—to meet growing traffic and business complexity.
This article explains four common rate‑limiting algorithms—fixed‑window counter, sliding window, leaky bucket, and token bucket—detailing how each works, their pseudo‑code implementations, and when to use them to protect high‑traffic systems such as flash‑sale platforms.
This article provides a comprehensive overview of distributed file systems, covering their historical evolution, essential requirements, architectural models (centralized and decentralized), persistence strategies, scalability, high availability, performance optimization, security mechanisms, and additional considerations such as space allocation, file deletion, small‑file handling, and fingerprint‑based deduplication.
This article outlines the key characteristics of large‑scale websites and presents a comprehensive set of architectural goals, patterns, and techniques—including performance tuning, high availability, scalability, extensibility, security, and agile operations—to guide the design of robust, user‑centric online platforms.
This article explains why load balancing is essential for high‑traffic systems, describes its underlying principles and classifications from layer‑2 to layer‑7, outlines common software implementations, and presents typical scenarios such as scaling, high availability, and disaster recovery.
This article explains how to build private and hybrid cloud solutions, outlines essential technology stacks, discusses scalability, resource management, and storage options, and provides practical guidance on improving availability and handling errors in cloud systems.
This article outlines the progressive evolution of large-scale internet architectures, detailing the transition from simple monolithic designs through clustering, caching, read/write separation, static/dynamic separation, high‑availability clusters, distributed systems, SOA, microservices, and finally service mesh, highlighting their principles, benefits, and challenges.
This article explains 58.com’s database architecture, covering availability through replication and dual‑master setups, read‑performance enhancements with indexing, read replicas and caching, consistency solutions, rapid horizontal scaling methods, and a review of Codd’s twelve rules for relational design.
This article shares practical guidance on designing, protecting, and continuously improving high‑concurrency backend services—covering baseline capacity, rate limiting, data‑structure optimization, stateless architecture, and horizontal scaling—to help engineers evolve small systems into robust, production‑grade platforms.
This article explains the requirements for invitation codes, critiques simple random generation, and presents a custom base‑32 encoding method in Java that guarantees uniqueness, efficiency, and reversibility while allowing easy expansion.
This article outlines six fundamental microservice design patterns—Aggregator, Proxy, Chain, Branch, Data‑Sharing, and Asynchronous Messaging—explaining their structures, use‑cases, scalability characteristics, and potential pitfalls to help architects choose the right approach for their systems.
This article explains how to design data architecture for microservice systems, covering microservice fundamentals, advantages, decoupling, lightweight APIs, continuous delivery, database per service versus shared databases, polyglot persistence, scaling dimensions, sharding strategies, and why MongoDB is a suitable choice.
Meituan Delivery’s architecture has progressed from a rapid MVP with coarse services to a scalable, fine‑grained platform comprising fulfillment, operation, and master‑data subsystems, employing reliability engineering, capacity planning, AI‑driven simulation, and location services to ensure high availability, efficiency, and future‑ready scalability.
This article introduces Hadoop’s open‑source big‑data framework, explains its core components HDFS and MapReduce, and outlines four key advantages—ease of deployment, robustness, scalability, and simplicity—while also covering HBase as the Hadoop‑based column‑oriented database.
This article traces the step‑by‑step evolution of a web system—from a single‑server LAMP setup through service and data separation, caching, server clusters, read/write splitting, CDN acceleration, distributed databases, NoSQL integration, business splitting, and finally distributed services—highlighting the motivations, characteristics, and practical outcomes of each stage.
This article traces the progressive evolution of website architecture—from the early single‑server model through application‑data separation, caching, clustering, read‑write splitting, CDN deployment, distributed and NoSQL databases, and finally microservice architectures—illustrating each stage with diagrams and explaining the motivations behind each architectural upgrade.
This article explains why growing business complexity and throughput demands force system decoupling and architectural upgrades, then details practical approaches to system splitting—including horizontal scaling, vertical and business partitioning—and describes the subsequent structural evolution with caching, sharding, and micro‑service patterns.
This article explains the concept of distributed architecture, its key properties such as cohesion and transparency, various applications like distributed file systems, caches, databases, and services, and outlines the evolutionary stages from single‑server setups to modern micro‑service and cloud‑native designs.
The article shares Zhihu's multi‑year journey toward service‑oriented architecture, discussing the motivations, practical challenges, design trade‑offs, and lessons learned from microservice, RPC, and SSO‑based vertical splitting, as well as guidelines for defining service boundaries and layering.
The article reviews the ten‑year evolution of Ant Financial's message queue, detailing its core reliability, consistency, availability and performance requirements, the architectural mechanisms built to meet them, the shift to pull‑mode and API‑mode designs, and the recent integration of compute capabilities to create a smart data transmission platform.
This article explains the fundamentals of distributed systems, outlines common use cases such as distributed file systems, caches, databases, and web services, examines real‑world examples like MyCat, and traces the architectural evolution from single‑server setups to modern micro‑service clusters.
This article provides a comprehensive overview of performance testing, explaining its definition, key metrics such as throughput, response time and concurrent users, the relationship between these indicators, optimal testing timing, a step‑by‑step workflow from requirement analysis to reporting, and practical tips for effective load testing and system optimization.
To support Meituan’s rapid growth, this article examines the design and evolution of several industry-leading message-queue solutions—including Alibaba’s Notify and RocketMQ, Tencent’s Tube and Hippo, and Ctrip’s Herms—highlighting their reliability, scalability, and decoupling features, and extracting key insights for building robust MQ systems.
This article explains how WeChat redesigned its red‑packet system for the 2016 Chinese New Year, detailing the dual‑data‑center architecture, order and user data separation, caching layers, traffic routing, high‑concurrency controls, database sharding, and graceful degradation to handle tens of billions of requests per minute.
The Elasticsearch Team Development Constitution outlines a comprehensive set of principles and guidelines—covering design philosophy, code quality, interaction etiquette, and organizational responsibilities—to help the rapidly growing project evolve into a reliable, secure, scalable, and user‑friendly distributed search engine.
The article outlines the key characteristics of large-scale websites and traces their architectural evolution from single‑server setups to multi‑tier, cache‑enhanced, clustered, and distributed systems, highlighting strategies such as load balancing, database read/write separation, CDN usage, NoSQL adoption, and service‑oriented decomposition.
The article examines Ceph’s claimed infinite scalability, cost advantages, and operational stability from an SRE perspective, comparing it with centralized systems like HDFS, and reveals practical challenges such as expansion granularity, crushmap rebalancing, utilization limits, and maintenance overhead.
This article provides a comprehensive technical overview of large distributed website architecture, covering performance, high availability, scalability, security, and agility, and illustrates the evolution, design patterns, and practical optimization techniques for modern e‑commerce platforms.
The article outlines the four major stages of enterprise IT architecture—single‑machine, dual‑machine hot‑standby, multi‑node active‑active, and distributed architectures—explaining their motivations, advantages, limitations, and how businesses should choose the appropriate model based on performance, availability, and scalability requirements.
The article summarizes the author’s takeaways from the GIAC Shenzhen conference, analyzing various public‑chain projects, their architectural choices, competitive focuses such as scalability, asset tokenization, DApp support, and the role of alliance chains in finance, traceability, and anti‑counterfeiting.
This article traces the historical development of distributed architecture from early computers to modern large‑scale web systems, explains core concepts such as clustering, replication, and middleware, and outlines eight evolutionary stages that address scalability, reliability, and performance challenges.
JD.com’s review and share platform combines multi‑dimensional rating, text, image and video content with a modular middleware, MySQL/MongoDB/HBase storage, Solr search, Redis caching and a management backend, detailing its architecture, daily operations, component‑based design, scalability challenges and future enhancements.
This article explains microservices architecture, contrasting it with monolithic systems, outlines its core characteristics, communication patterns, advantages, disadvantages, design considerations, API importance, governance practices, fault‑tolerance strategies, container integration, and real‑world examples such as Netflix and Twitter.
This article outlines guiding principles, high‑availability strategies, and high‑concurrency techniques—covering stateless design, resource isolation, quota management, monitoring, degradation, rollback, and scaling—to help engineers build resilient, scalable systems while balancing cost and performance.
This article examines how to design a reliable group messaging system with read‑receipt support, comparing push and pull delivery, detailing data structures, acknowledgment flows, and optimization techniques to reduce traffic and storage while maintaining real‑time user experience.
This guide outlines the five essential architecture metrics—performance, availability, scalability, extensibility, and security—detailing practical optimization techniques for front‑end resources, server‑side caching, database tuning, load balancing, and security layers to build resilient, high‑performing web systems.
This article examines the evolution of a web crawler architecture across three versions, highlighting the importance of completeness, standardization with UML, clear goals, accuracy, and maintainability to build a scalable and cost‑effective backend system.
