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 why clear application layering matters, outlines Alibaba's recommended layer structure, proposes an optimized layering model with distinct responsibilities, and details domain model conventions to improve code reuse, maintainability, and team collaboration in backend development.
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 principles of the Facade, Observer, Command, and Chain of Responsibility design patterns, illustrates how Tomcat implements each with class diagrams and code snippets, and shows how these patterns help organize subsystems, manage events, delegate actions, and streamline request processing in a Java server.
This article explores Tomcat’s modular design, detailing the roles of Service, Connector, Container, Server, and Lifecycle interfaces, and illustrates how requests flow through the servlet engine with code examples and component diagrams.
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.
This article provides a comprehensive overview of Alibaba's open‑source Dubbo framework, detailing its ten‑layer architecture, the roles of providers and consumers, service registration, monitoring, protocol support, and the organization of its Maven modules for building distributed backend services.
This article presents a comprehensive design of a flash‑sale (seckill) architecture, covering business characteristics, user scale, layered system components, optimization strategies, full‑link stress testing, and a complete SpringBoot code example with distributed locks, message queues, and database sharding.
This article examines the evolution of QTalk’s instant messaging platform, detailing its original centralized design, the motivations for decentralization, the new architecture with domain and public services, security benefits, deployment strategies, and real-world use cases, illustrating how a scalable, secure IM solution can be built for enterprise environments.
The article explains how the slowdown of Moore's Law drives the shift from monolithic applications to distributed systems, covering load balancing, session handling strategies, read‑write separation, and database sharding to achieve scalable, high‑availability backend architectures.
The article outlines how Tmall’s product‑detail service evolved through three architectural phases—system staticization, unified web caching, and CDN staticization—to handle Double‑11 traffic spikes with cost‑effective scalability, high availability, and improved performance.
This article reviews essential concepts of message queue middleware, covering why to use queues, their drawbacks, selection criteria, high‑availability strategies, deduplication, reliable transmission, ordering guarantees, and practical advice for interview preparation.
This article presents a practical, China‑focused microservice reference stack built on Spring Cloud, detailing core support components such as Zuul, Eureka, Apollo, and Spring Boot, as well as monitoring tools like Kafka, ELK, CAT, KairosDB, ZMon, and Hystrix, and explains when and how to apply each in production environments.
The talk details Tencent Xinge’s architecture and cloud‑native practices that enable hundred‑billion‑level mobile push, combining terminal integration, real‑time backend filtering, distributed bitmap selection, precise‑push AI models, and DevOps pipelines to deliver fast, scalable, data‑driven notifications with effect tracking.
This article presents a practical, China‑centric microservices reference stack built on Spring Cloud, detailing eleven core components—including Zuul, Eureka, Apollo, Kafka, ELK, and Hystrix—while comparing them with alternatives and offering guidance for architects to avoid common pitfalls and accelerate production‑grade deployments.
This article details the design of a unified MySQL data synchronization platform that consolidates offline sync, real‑time subscription, and real‑time sync into BatchJob, StreamJob, and PieJob abstractions, describing task implementations, cluster architecture, high‑availability mechanisms, and evolution challenges such as file loss and metadata handling.
This article explains how modular design and service extraction can reduce system complexity and improve reusability, illustrates practical before‑and‑after examples for red‑packet and notification services, and details high‑concurrency techniques such as caching, asynchronous processing, rate limiting, service degradation, anti‑fraud measures, and concurrency‑safe database operations.
This article outlines practical strategies for building high‑concurrency back‑end systems—including server architecture, load balancing, database clustering, caching, message queues, asynchronous processing, and service‑oriented design—to ensure smooth operation of traffic‑intensive e‑commerce services.
The article explains how to design a backend architecture that can handle millions of concurrent requests by applying principles such as service decomposition, high availability, idempotent business logic, and various rate‑limiting algorithms—including sliding window, leaky bucket and token bucket—with a runnable Java demo.
This article details the three‑stage evolution of Ctrip's image service architecture—from an early NFS‑backed design with Squid caching, through a Varnish‑and‑Lua powered middle stage, to the current Go‑based multi‑process system using FastDFS—highlighting the challenges, solutions, and performance outcomes.
This article details Snowball's evolution from a third‑party fund trading platform to a self‑developed backend system, covering business flow, architectural redesign, phased user migration, payment channel optimization, and the operational benefits achieved through the new solution.
The article examines the advantages and drawbacks of microservices versus monolithic architectures, outlines key factors that influence the decision to split, and walks through a real‑world shared‑points project, detailing a four‑step process for decomposing a monolith into independent services.
This article walks through the step‑by‑step evolution of a Java website—from a single‑machine setup to a multi‑tier, load‑balanced, sharded, cached, and service‑oriented architecture capable of handling billions of requests—detailing the challenges and solutions at each stage.
This article explains how a three‑layer caching architecture—combining Nginx, Redis, and Ehcache—along with template engines, double‑Nginx routing, persistence mechanisms, cluster setups, and various cache‑update strategies can dramatically improve hit rates, reduce database pressure, and prevent cache‑related failures in high‑traffic applications.
This article shares a seasoned developer’s perspective on selecting a message‑queue middleware, outlining typical adoption stages, three key evaluation criteria—coder expertise, current and future requirements, and community/ecosystem health—and offering candid advice on avoiding common pitfalls.
The article explains how Alibaba’s TMF 2.0 framework tackles massive transaction‑peak challenges by introducing visual, configurable, and manageable business definitions through a plug‑in architecture, unified business identity, and a clear separation of management and runtime domains.
This article explains what a flash‑sale (秒杀) is, outlines its technical challenges such as massive concurrency and database load, and presents practical strategies and architectural designs—including independent deployment, static pages, CDN bandwidth leasing, dynamic URL generation, and order‑handling mechanisms—to reliably support ultra‑high traffic spikes.
This article explores the defining traits of large‑scale websites and walks through the step‑by‑step evolution of their architecture—from single‑server setups to distributed systems with caching, load balancing, database sharding, and micro‑services—while highlighting common design pitfalls and best‑practice recommendations.
This article details the redesign of a TV app from a horizontal layout to a waterfall flow, explaining the project timeline, advantages, new seven‑layer architecture, CMS‑driven configuration, compatibility handling, pagination strategies, caching, and fault‑tolerance measures that together improved user conversion and system robustness.
This article traces Alibaba's e‑commerce technical evolution—from early LAMP‑based monoliths through Java‑centric 2.0 systems to a massive multi‑IDC, service‑oriented distributed architecture with HSF, Pandora, and advanced database sharding solutions—highlighting the challenges and innovations that enabled its massive scalability.
This article walks through the evolution from traditional three‑layer monolithic architecture to microservice architecture, explaining system design concepts, the drawbacks of monoliths, the benefits and challenges of microservices, and compares them with SOA, providing clear diagrams, pros and cons, and practical insights for backend engineers.
HSF 2.2 introduces a clear three‑domain architecture, async call interceptors, multi‑application support, and several serialization and map‑operation optimizations that together reduced CPU usage, network traffic and latency, enabling Alibaba to handle over 3.5 trillion calls during the 2017 Double‑11 event.
This article explains the architecture and key technologies of 360’s SSP advertising engine—including flexible micro‑service layers, DAG‑based topology, rule and template management, and high‑performance Go‑based HTTP frameworks—that enable billion‑scale ad delivery with low latency and high concurrency.
This guide walks beginners through the fundamental components of microservice infrastructure—configuration management, service registry, API gateway, authentication, message broker, BFF, circuit breaker, and load balancing—explaining their roles, interactions, and practical considerations for building resilient systems.
The article shares practical insights on planning, designing, developing, testing, and rolling out a large‑scale backend system refactor, emphasizing resource limits, pain points of legacy code, unit‑test protection, layering, decoupling, monitoring, and staged deployment to ensure stability during high‑traffic events.
This article reviews the Alibaba Java Development Manual, highlighting key best‑practice sections such as project structure, coding conventions, MySQL design, security, and concurrency, and provides detailed analysis of architecture layers, collection handling, thread‑pool creation, locking principles, and SQL performance optimization.
This article shares the author's experience and lessons learned from a two‑day intensive discussion on microservice migration, outlining a concrete implementation plan, current architectural challenges, key debates, and the final target architecture blueprint for a third‑party payment company.
This article explains the evolution of instant messaging systems, introduces the Timeline logical model for message synchronization and storage, compares traditional and modern architectures, and details how Alibaba Cloud TableStore can be used to build a high‑performance, multi‑device IM backend supporting millions of TPS and millisecond latency.
The two‑day Tongcheng Technology Conference in Suzhou featured six technical sessions covering serverless architecture, microservices with Go, Facebook‑style development tools, NewSQL database practices, hybrid cloud management at Sina Weibo, and high‑performance ticket search systems, offering practical insights for backend engineers.
This article details how Tencent's Mobile QQ grew from a half‑million online users to over 180 million by optimizing network access, evolving backend architecture from a single‑center to a three‑center design, and deploying a real‑time global smart‑scheduling system that reduces packet loss and login latency for both domestic and overseas users.
Database sharding, or splitting databases into multiple instances and tables, is essential for scaling backend systems; this article explains its importance, historical context, core concepts, storage stretching techniques, index and consistency handling, and provides a practical design example for transaction systems.
This article outlines essential principles for designing high‑concurrency and high‑availability systems, covering stateless architecture, service decomposition, caching strategies, message queues, data heterogeneity, degradation, rate limiting, traffic switching, rollback, and comprehensive business design rules such as idempotency, anti‑duplication, and documentation.
This article introduces Tencent Cloud Message Queue (CMQ), detailing its high‑reliability architecture, core features such as push/pull models, long polling, delayed and replayable messages, routing, large‑message handling, and encryption, and provides Python SDK code examples for each use case.
Over the past two years, Meipai Live streaming has transformed from a single‑CDN, single‑source setup to a multi‑CDN, multi‑source architecture with intelligent integrated scheduling, improving service stability, reducing costs, and enhancing user experience, as detailed by technical director Zhu Lei, who will discuss source‑station construction, CDN integration, and live‑stream optimization.
This article explains the concepts, history, and core mechanisms of web servers, web application containers, application servers, and reverse proxies, compares their functions and relationships, and provides a concise summary to help developers choose the right component for their backend architecture.
This article presents a comprehensive overview of Vipshop's message gateway redesign, covering its architectural positioning, internal modules, technical stack, monitoring, degradation strategies, and practical lessons learned to handle massive messaging traffic in a large‑scale e‑commerce environment.
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 recaps a technical talk by Qunar’s accommodation trading system lead, covering event‑driven design, flexible document schemas, and reliability techniques such as circuit breaking, gray releases, and automated testing to improve scalability and maintainability of backend transaction platforms.
This article details Ctrip's design and implementation of a high‑throughput, low‑latency user data collection platform that leverages Java NIO, Netty, and a custom Kafka‑based messaging layer, covering architecture, encryption, compression, disaster‑recovery, performance testing, and downstream analytics products.
This article describes the design, technology selection, and performance evaluation of Ctrip's real‑time user behavior data collection platform, covering Netty‑based network handling, Kafka/Hermes messaging, encryption, compression, Avro backup, and related analytics products, with detailed feasibility analysis and benchmark results.
An order system retrieved incorrect product size data due to master‑slave database lag causing stale Redis cache, and the article explains the original flawed flow, the revised solution that writes to cache during sync, and best practices for cache updates, read‑through, and QA testing.
This article explores the definitions of SOA and DDD, explains DDD's layered architecture, demonstrates how business relationships become domain models, and provides concrete C# examples of repositories, services, and factories to illustrate the integration of service‑oriented architecture with domain‑driven design.
The Wǔcǎi Shí project overhauled Alibaba's e‑commerce backend by introducing a shared‑service layer and distributed middleware, dramatically improving business scalability, technical extensibility, and enabling rapid creation of new market services with minimal overhead.
This article tells the story of a developer who first used a blocking email call, then switched to multithreading, and finally adopted a message queue to achieve asynchronous processing, decoupling, scalability, and reliability for user registration emails.
The article describes how Ctrip rebuilt its real‑time user behavior platform using a Java‑based stack (Kafka, Storm, Redis, MySQL) to achieve millisecond‑level latency, high availability, scalable performance, and robust handling of traffic spikes, failures, and data back‑pressure.
This article explains the design and improvements of WeChat's MQ 2.0 asynchronous queue, covering its cross‑machine consumption model, enhanced task scheduling, MapReduce‑style processing, stream tasks, and robust overload protection that together enable high‑performance, resilient backend services.
This article explains microservice architecture versus monolithic design, discusses communication, service discovery, ordering, and messaging strategies, and details GeTui’s practical implementation using OpenResty, API gateways, Zookeeper, and DevOps automation.
This article explains the producer‑consumer and publish‑subscribe messaging patterns, introduces RabbitMQ’s core concepts such as exchanges, queues, routing keys, and reliability mechanisms, and demonstrates how to apply these patterns to data ingestion and event distribution scenarios with practical diagrams.
This article explains Kafka's core concepts and compares producer‑consumer and publish‑subscribe models, illustrating how to apply each pattern for data ingestion and event distribution in distributed backend systems, and offers practical design alternatives when Kafka’s native capabilities fall short.
This article outlines how a massive e‑commerce platform like Taobao evolves its backend architecture step by step—from an all‑in‑one server through service separation, caching, load balancing, session management, database sharding, CDN acceleration, and finally distributed search—highlighting the motivations, trade‑offs, and key design considerations at each stage.
This article presents a comprehensive methodology for internet performance engineering, covering non‑functional quality goals, detailed metrics for application servers, databases, caches and message queues, a practical technical review outline, and a real‑world capacity‑planning case study with both maximal and minimal resource solutions.
This article examines the architecture of Weibo's high‑availability advertising platform, covering match service design with OpenResty, index sharding, business logic optimization, dynamic auto‑scaling, and a real‑time monitoring pipeline to ensure stable, high‑performance ad delivery at massive scale.
This article explains the evolution from heavyweight traditional SOA with enterprise service buses to lightweight, distributed microservice architectures, covering service design patterns, deep microservice principles, and a detailed e‑commerce inventory microservice case study, while illustrating a complete microservice system hierarchy.
This article explains the key challenges of high availability and scalability in distributed architectures and provides practical solutions for each layer—entry, business, cache, and database—using techniques such as heartbeat IPs, stateless services, consistent hashing, and sharding.
This article outlines a four‑layer game server framework—including gateway, logic, record, and database services—detailing their responsibilities, implementation models such as multithreaded reactors and coroutine libraries, service‑driven designs, and the common design patterns and algorithms used in backend game development.
This article outlines the motivation, requirements, modular decomposition, and architecture of a distributed web crawling platform that emphasizes reusability, lightweight modules, real‑time monitoring, and easy configuration for diverse data‑collection tasks.
This article describes the design, architecture, and operational features of Baidu Waimai's unified voucher issuance platform, detailing its four‑layer backend structure, permission and strategy configurations, flow‑control mechanisms, service isolation, monitoring visualizations, and re‑entrancy safeguards to support large‑scale marketing distribution.
The article explains how WeChat C2C’s backend uses progressive JPEG encoding combined with a streaming transmission approach and a dynamically adjustable minimal transport size to reduce image delivery latency and improve user experience under varying network conditions.
This article outlines a comprehensive approach to building high‑concurrency web systems by introducing layered architecture, modular segmentation, distributed deployment, server clustering, asynchronous processing with message queues, caching strategies, service‑oriented design, and automated redundancy to achieve high availability and scalability.
The article recounts Xu Haiyang’s hands‑on experience designing Baidu’s early Spider system, describing its pure C procedural architecture, bug‑fixing journey, PageRank processing, team‑management analogies, and his later moves into AI and education entrepreneurship.
This article explains the architecture of 360’s image hosting platform, detailing the Davinci upload pipeline and the Picasso download flow, the processing steps, caching layers, and the supporting infrastructure that enables billions of image requests daily.
This article examines various business load scenarios for a logistics management system and presents four progressive load‑balancing architectures—ranging from simple Nginx/Haproxy to DNS round‑robin with LVS and Keepalived—while defining key performance terms and outlining future discussion topics.
Taobao’s Open Platform sustains hundreds of billions of daily API calls and messages by employing a pipeline‑based high‑performance API gateway with multi‑level caching, asynchronous processing, granular traffic control, a highly reliable push‑pull messaging system, and a zero‑loss data‑sync service that dynamically balances resources during massive traffic spikes.
Message queues act as a crucial middleware component in distributed systems, addressing coupling, asynchronous processing, traffic shaping, and high availability, with real-world scenarios such as asynchronous handling, decoupling, traffic throttling, logging, and communication, while reviewing popular solutions like ActiveMQ, RabbitMQ, ZeroMQ, Kafka, and JMS.
The article analyzes the massive scale of Chinese New Year red‑packet activity on WeChat, presents usage statistics, and explains the backend architecture—including distributed KV storage, cache‑layer atomic operations, and database transaction handling—that enables high‑throughput red‑packet distribution.
This article examines the critical factors influencing web performance—including network latency, TCP/HTTP protocols, browser rendering, and server-side architecture—and provides practical optimization techniques such as TCP tuning, HTTP/2 adoption, resource compression, caching, load balancing, and distributed design to achieve fast, scalable web services.
The article describes how Hujiang built and iterated a three‑generation asynchronous task scheduling platform—Juice—using Mesos and Docker to achieve on‑demand resource allocation, horizontal scalability, and efficient handling of large multimedia processing workloads.
This article explains the architecture and challenges of network‑based scheduling systems, CDN and DNS‑driven video playback, the structure of the QQWry IP database, and proposes efficient IP‑based routing and quality‑monitoring methods for large‑scale backend services.
This article explains the challenges of visualizing service relationships in microservice environments and presents a fully automated, non‑intrusive approach that captures static topology and runtime characteristics through middleware and client hijacking, source tracing, and IPO modeling to build accurate service flow graphs.
This article explains the reasons for breaking up tightly‑coupled monolithic systems, outlines preparation steps such as assessing business complexity and defining service boundaries, and provides detailed practical guidance on database sharding, migration, query refactoring, cut‑over plans, consistency, and post‑split stability.
This article explains the fundamental ideas behind microservices, compares them with traditional SOA, discusses when to adopt microservices, outlines design principles, explores technology selections such as Spring Cloud and Docker, and addresses common challenges like service discovery, transaction handling, and operational costs.
This article outlines the challenges of high‑traffic scenarios such as flash sales and timed red‑packet distribution, and presents a comprehensive backend architecture—including load balancing, database clustering, NoSQL caching, CDN, concurrency testing, message queues, first‑level caching, and static data strategies—to ensure smooth operation and optimal user experience.
The article outlines the five‑year evolution of Qunar's payment platform from a tightly coupled monolith (1.0) to a highly available, service‑oriented distributed architecture (2.0), detailing component breakdown, challenges, and the resulting core transaction, payment, cashier, and API layers.
The live‑streaming gift system is built with a producer‑consumer message queue, KV store, cache, SQL and SSD layers, employing asynchronous leaderboard updates, unique transaction IDs with redo handling, end‑to‑end encryption and replay protection to ensure high‑consistency, real‑time, secure processing of monetary gifts.
In this interview, Ma Jin, lead of NetEase's distributed database DDB, discusses the system's evolution, technical challenges, performance‑optimization practices, cloud‑native proxy deployment, and future prospects for distributed databases within large‑scale applications.
The conference featured a series of high‑availability architecture talks covering performance‑driven design, RPC framework resilience, big‑data platform evolution, MySQL cluster consistency, and cloud infrastructure best practices, presented by experts from 58.com, Alibaba, Tencent, Baidu, and others.
This article chronicles the five‑year evolution of Qunar's payment platform from a tightly coupled monolithic system to a high‑concurrency, highly available distributed architecture, detailing the motivations, service‑oriented splits, core components, and checkout variations that enabled support for diverse payment scenarios.
The article explains the drawbacks of traditional two‑phase commit distributed transactions—reduced availability, performance, and scalability—and proposes a message‑queue‑plus‑state‑table pattern with idempotent processing to achieve eventual consistency while improving system throughput.
This guide explains how to design and test high‑concurrency systems by choosing appropriate server architectures, load‑balancing, database clustering, caching layers, message queues, first‑level caches, and static data strategies to ensure smooth operation under heavy user traffic.
This article explains the design of JD’s flash‑sale (抢购) system, covering its business model, core Redis‑based inventory management, Lua scripting for atomic stock deduction, rate‑limiting, asynchronous logging with JMQ, and fail‑over strategies to ensure high‑concurrency reliability.
This article explains what high concurrency is, its impact on servers and users, and provides concrete data‑handling techniques, architectural components, testing tools, and real‑world examples such as sign‑in, lottery, caching, message queues, first‑level cache, and static‑data strategies to build resilient backend systems.
The article details the Qunar Order Center's architecture evolution—addressing fragmented order data, introducing unified query APIs, JSON‑based storage, merge/diff services, asynchronous I/O, Elasticsearch integration, data sharding, business isolation, rate limiting, adapter layers, micro‑service decomposition, and a centralized configuration system to improve scalability, reliability, and maintainability.
Peter Marton, co‑founder and CTO of RisingStack, argues that Node.js excels for microservices due to its efficiency, performance, and developer happiness, citing PayPal’s reduced codebase, Netflix’s faster startup and scaling, and GoDaddy’s hardware savings after migrating from .NET.
This article dissects WhatsApp’s high‑reliability architecture that supports 450 million users, detailing its Erlang‑based backend, hardware choices, scaling techniques, monitoring tools, and the engineering lessons learned from pushing a single server to two‑million concurrent connections.
This article explains how breaking monolithic applications into Node.js‑based microservices improves scalability, deployment speed, and developer productivity, illustrated with real‑world case studies from PayPal, Netflix, and GoDaddy. It also highlights the efficiency of npm, the non‑blocking I/O model, and the rapid adoption by modern development teams.
The article examines how JD’s e‑commerce platform tackles massive traffic spikes and high concurrency by employing modular system decomposition, distributed architecture, API‑centric services, performance tuning, and virtual elasticity to ensure stability, scalability, and a smooth user experience during major promotional events.
This article presents a comprehensive technical case study of Qunar's Order Center, describing its initial architecture, the challenges faced with scaling and reliability, and the successive redesigns in versions 2.0 and 3.0 that introduced Elasticsearch, asynchronous I/O, micro‑service decomposition, rate‑limiting, and a configurable adapter layer to support massive, multi‑line order processing.
The article presents a detailed overview of Bilibili's GOIM live chat architecture, covering its high‑stability, high‑availability, low‑latency design, component breakdown, memory and module optimizations, network improvements, and performance testing results to achieve scalable real‑time messaging.
The talk recounts how Panda TV’s initial architecture supported rapid growth but eventually required higher performance and concurrency, prompting a migration to a Golang‑based system that refactored core services and produced a suite of utility libraries and tooling, with lessons and best‑practice insights shared.
This article details JD's One‑Yuan Grab Treasure platform redesign, covering business growth drivers, database sharding estimation, hash‑plus‑range routing implementation, Elasticsearch aggregation, Canal‑based sync, historical data migration, and downgrade mechanisms to ensure high‑throughput, reliable order processing during massive sales events.
