This article examines the role of order systems in traditional e‑commerce, outlines their core functional modules, explains their relationships with upstream and downstream services, and discusses design considerations, workflow engines, state machines, and future architectural evolution.
This article recounts the author's three‑year journey evolving a Python‑based SaaS backend from a simple MVC setup through service splitting and microservices, detailing architectural choices, performance challenges, optimization tactics, and the move toward domain‑driven design, while sharing practical lessons and resources.
This comprehensive guide explains microservice architecture, its key characteristics, advantages, disadvantages, and when to adopt it, then details ten crucial design patterns—including database per service, event sourcing, CQRS, Saga, BFF, API gateway, Strangler, circuit breaker, externalized configuration, and consumer‑driven contract testing—complete with pros, cons, use‑cases, and technology examples.
This case study details how JD’s "Browse" UGC project evolved from rapid agile delivery to a performance bottleneck as data grew, and how introducing Elasticsearch, redesigning the query flow, and refactoring storage components restored fast, flexible searches for both front‑end and operations users.
Baidu’s Transaction Middle Platform Order System provides a unified, cloud‑native architecture that supports diverse Baidu products by orchestrating modular commands, handling order lifecycle, payment, refunds, and splitting, while employing caching, asynchronous processing, and sharded databases to achieve high throughput and low latency.
From a simple CRUD application to a robust distributed architecture, this article explains why vertical scaling hits limits, how horizontal scaling and system partitioning work, the goals of transparency, scalability and reliability, and key concepts such as sharding, load balancing, CAP and BASE theories.
This article distills Bilibili's technical director insights on building high‑service‑quality architectures, covering systematic load‑balancing strategies, sophisticated rate‑limiting mechanisms, robust retry policies, precise timeout controls, and comprehensive approaches to prevent cascading failures in large‑scale systems.
This article explores the challenges of designing a flash‑sale (秒杀) system—such as overselling, high concurrency, request flooding, URL protection, and database bottlenecks—and presents a complete backend architecture using Redis, Nginx, rate‑limiting, asynchronous order processing, and service degradation to achieve a stable, high‑throughput solution.
The article defines componentization (shared JAR) and serviceization (independent service), compares their performance, cost, maintainability, and resource trade‑offs, outlines ideal use‑cases such as high‑throughput, no‑DB calls versus DB‑access or lower‑concurrency needs, and provides Vivo case studies to guide selection.
This article analyzes Baidu's live‑stream messaging system, compares it with ordinary group chat, identifies scalability challenges, proposes a multicast (mcast) architecture, evaluates performance, bandwidth, and client impact, and outlines further enhancements such as historical and gift messages.
This article examines stateful backend services and compares various high‑availability strategies—including cold backup, dual‑machine hot standby, same‑city and cross‑city active‑active, and multi‑active architectures—highlighting their benefits, drawbacks, and practical implementation considerations.
This article details a step‑by‑step migration of a content‑community tag system from a monolithic design to separate classification and attribute services, covering storage synchronization, isolation‑layer construction, read/write migration, dependency handling, and final rollout while ensuring speed, stability, and data accuracy.
This article introduces RabbitMQ, explains its core concepts and typical scenarios such as decoupling, asynchronous processing, and traffic shaping, and discusses the benefits and challenges of integrating a message queue into backend architectures.
This article examines the chronic decay of a long‑standing warehouse inventory system, identifies its tangled business boundaries, chaotic architecture, and uncontrolled delivery efficiency, then presents a domain‑driven design solution with clear modeling, onion‑style layering, CQRS, and practical implementation steps to restore maintainability.
The Vivo App Store recommendation system uses a modular, hot‑plug architecture—layered from plugins to base services and employing Template Method, Strategy, and Composite patterns—to integrate unchanged data sources, deliver high‑performance personalized recommendations, reduce development effort by ~75%, and enable rapid, low‑bug scene‑specific upgrades.
This article explores the evolution of business architecture from functional to domain‑based microservice splitting, outlines service grading, identifies code coupling and unreasonable dependencies, and presents practical governance techniques such as on‑demand loading, event‑driven design, and anti‑corruption layers to improve stability and maintainability.
This article details the motivation, design choices, architecture, performance optimizations, and operational lessons learned while implementing a distributed ID generation system using Leaf's segment mode to achieve global uniqueness, high availability, and low latency for large‑scale e‑commerce services.
This article explains why Kuaishou needed a dedicated online messaging system, how RocketMQ was chosen and integrated, the deployment strategies, client SDK design, load‑balancing and disaster‑recovery mechanisms, diverse message features, distributed reconciliation monitoring, and performance‑tuning parameters.
The article outlines a microservice‑based user‑center architecture for handling over one hundred million users, detailing gateway, core, and async services, interface design, vertical and horizontal database sharding, token graceful degradation, multi‑layer password security, event‑driven async processing, and comprehensive monitoring for high availability, performance, and security.
This article explains how Domain‑Driven Design complements microservice architecture by addressing functional partitioning, clarifying bounded contexts, and improving scalability, while also discussing microservice drawbacks and practical guidelines for splitting complex systems in modern applications.
This article examines high‑availability strategies for stateful backend services, covering cold backup, dual‑machine hot standby, same‑city active‑active, and remote multi‑active solutions, while discussing their benefits, trade‑offs, and architectural patterns for resilient distributed systems.
The article explains why shifting batch jobs, reporting, and machine‑learning model training from traditional backend services to a dedicated data platform can simplify development, improve fault tolerance, and scale analytics, using real‑world examples from Spotify and best‑practice guidelines.
This article walks through the journey of transforming a simple online supermarket from a monolithic web application to a fully fledged microservice architecture, covering the motivations, common pitfalls, service decomposition, monitoring, tracing, logging, gateway, service discovery, circuit breaking, testing strategies, and the role of service mesh.
This article traces Taobao's backend architecture evolution—from a single‑server setup to distributed clusters, caching, load balancing, database sharding, microservices, containerization, and finally cloud‑native deployment—highlighting the technologies and design principles that enable scaling from hundreds to millions of concurrent users.
This article outlines the step‑by‑step evolution of a high‑traffic server architecture—from a single‑machine deployment to distributed clusters, caching, load balancing, database sharding, microservices, containerization, and cloud platforms—highlighting the technologies involved at each stage and summarizing key design principles for scalable, highly available systems.
The article explains that while a Service layer may seem unnecessary for simple business logic, it becomes essential as applications grow, offering benefits such as handling complex operations, supporting reuse across controllers, facilitating unit testing, and enabling flexible business logic composition.
The article recounts how Postman's Service Foundation team identified the limitations of the monolithic Sync service, designed and built the Bifrost WebSocket gateway using Fastify, AWS ElastiCache for Redis, and a private API, and scaled it through horizontal expansion and custom load‑factor metrics while sharing practical engineering insights.
The article compares three approaches—synchronous dual write, asynchronous dual write with a message queue, and CDC via Canal—to keep Elasticsearch and a relational database consistent for cross‑database aggregated full‑text search, outlining their steps, advantages, and drawbacks.
This article examines the four major API architectural styles—RPC, SOAP, REST, and GraphQL—explaining how each works, their strengths and weaknesses, and the scenarios where they shine, helping developers choose the best fit for their projects.
The article explores practical design principles for microservice architecture, covering core concepts, team and database partitioning, API granularity, domain‑composed services, gateway strategies, shared JAR dependencies, decoupling techniques, and change‑impact analysis to guide robust backend system development.
This article presents a comprehensive overview of the 58.com alliance advertising platform, detailing its business model, core modules such as SSP, direct‑investment, DSP and creative platforms, media integration flow, performance optimizations, GC tuning, indexing strategies, and future directions for programmatic creative generation.
This article surveys the evolution of software complexity, defines microservice architecture, outlines its key advantages and drawbacks, and then details ten crucial design patterns—including database per service, event sourcing, CQRS, saga, BFF, API gateway, strangler, circuit breaker, externalized configuration, and consumer‑driven contract testing—while explaining when each should be applied.
This article shares the author's experience migrating a high‑traffic platform from PHP to Go, detailing the challenges of framework selection, layered architecture design, incremental refactoring, and the eventual adoption of go‑kit for scalable microservices.
This article explores the key challenges of designing a flash‑sale (秒杀) system—such as overselling, high concurrency, request flooding, and database strain—and presents a comprehensive backend architecture with database design, dynamic URLs, caching, rate limiting, async ordering, and service degradation techniques.
This article explains why massive traffic spikes can cripple database performance, introduces cache layers and common caching patterns, and offers practical solutions to consistency, concurrency, penetration, and avalanche problems for large‑scale internet applications.
The article explains how decoupling persistence from a specific database engine and moving ID generation to the domain layer using 64‑bit integer identifiers—leveraging the Twitter Snowflake algorithm and the IdGen library—improves scalability, reduces coupling, and avoids the storage overhead of UUIDs.
This article presents the design, architecture, and implementation details of a visual, real‑time, and highly available configuration platform for commercial‑real‑estate advertising, covering requirements analysis, data modeling, CAP‑theorem considerations, consistency mechanisms, client design, long‑connection strategy, performance testing, and future outlook.
This article examines whether a Service layer in a Spring‑based backend project truly requires an interface, debunks common justifications, proposes practical development workflows, and outlines the advantages and drawbacks of using or omitting interfaces in various architectural scenarios.
This article presents a comprehensive, step‑by‑step guide on why and how to split monolithic applications and databases, covering business complexity analysis, service boundary definition, migration planning, global ID generation, data sync, query refactoring, switch‑over strategies, consistency guarantees, and post‑split stability measures.
This article explains how to design a configuration center, covering storage selection, environment isolation, push‑pull update mechanisms, Spring integration, permission auditing, metrics monitoring, and open APIs or multi‑language SDKs for practical implementation.
This article explains why monolithic systems need to be split, how to assess business complexity, define service boundaries, perform vertical and horizontal database sharding, adopt global ID generators, migrate data safely, and ensure consistency and stability during cut‑over using stop‑write or dual‑write strategies.
The article analyzes why many game server architectures avoid microservices, highlighting real‑time latency requirements, stateful processing, network overhead, and the mismatch between typical microservice patterns and the high‑performance demands of multiplayer online battle arena games.
This article describes how a hotel pricing platform was refactored using Domain-Driven Design, detailing the strategic, tactical, and implementation phases that clarified domain boundaries, introduced a layered architecture, standardized processes, and delivered faster development, better maintainability, and improved operational visibility.
The article compares five data synchronization approaches—periodic Logstash pulls, synchronous dual writes, asynchronous dual writes with MQ, Canal-based binlog streaming, and a Canal‑MQ hybrid—detailing their architectures, advantages, drawbacks, and suitable scenarios for integrating databases with Elasticsearch.
This article explains why monolithic systems need to be split, outlines multi‑dimensional preparation steps, details database vertical and horizontal partitioning, global ID generation, cut‑over strategies, consistency handling, and operational safeguards to ensure a smooth migration.
This article walks through the evolution of an online supermarket from a simple monolithic website to a fully decoupled microservice architecture, highlighting common pitfalls, design decisions, component choices such as monitoring, tracing, service discovery, circuit breaking, testing, and the trade‑offs of each step.
This article explains the Command‑Query Separation principle, introduces the CQRS architectural pattern, and compares three implementations—single‑database, dual‑database, and event‑sourced—detailing their workflows, benefits, and trade‑offs for optimizing read and write operations in backend systems.
This article explores how Domain‑Driven Design helps the Tongtian Tower platform manage rapidly growing business complexity by separating business and technical concerns, introducing strategic and tactical design, bounded contexts, layered and hexagonal architectures, and complementary patterns such as CQRS and domain primitives.
To overcome aging hardware and code limitations, QQ Mail rebuilt its full‑text search using Tencent Cloud Elasticsearch, adding an esproxy layer, MQ‑driven updates, HTML‑to‑text extraction, protobuf‑JSON conversion, index sorting, two‑stage precise/fuzzy queries, and custom tokenizers, delivering scalable, low‑latency email search.
This article explains the distinctions between SOA and microservice architectures, describes ESB and API gateway roles, outlines the characteristics of both architectures, and provides practical Dubbo service design guidelines such as packaging, granularity, versioning, and pre‑release environment configuration.
This article examines the challenges of microservice communication and explains how to transform an Nginx+Lua layer into an OpenResty‑based API gateway, covering core concepts, usage scenarios, security, performance, high‑availability, extensibility, and a comparative review of popular open‑source gateway solutions such as Nginx, Spring Cloud Zuul, Kong, Tyk and others.
This article explains the evolution of project architectures—from single‑server MVC to RPC, SOA, and micro‑services—while defining key terms such as clusters, load balancing methods, and various caching strategies essential for high‑concurrency, large‑scale backend systems.
The article examines the scaling challenges of Cainiao's logistics platform during Alibaba's Double‑11 shopping festivals and explains how adopting RocketMQ for asynchronous decoupling dramatically reduced costs, stabilized the transaction‑logistics chain, and enabled sustainable high‑throughput processing.
This report recaps a technical closed‑door session where experts from Weibo and Ziroom shared real‑world API gateway implementations, discussed centralized versus decentralized designs, explored the evolution of Ziroom's gateway, introduced the Gamma‑RPC framework, and debated future trends like service mesh.
This article explains how to design a high‑performance feed‑stream system—covering product definition, data categories, storage options, synchronization modes, metadata handling, commenting, likes, search, sorting, deletion, and update—so you can build a solution that scales to millions or billions of users.
This article walks through the step‑by‑step evolution of a high‑concurrency backend—from a single‑machine setup to a cloud‑native, micro‑service architecture—highlighting the technical challenges, key technologies, and design principles at each stage.
This article compares three seasoned experts' approaches to microservice splitting—vertical vs. horizontal, business‑driven, stability‑driven, and performance‑driven—highlighting trade‑offs, team size considerations, and practical guidelines for achieving scalable, maintainable architectures.
This article explains the business challenges of handling marketing assets during refunds, defines asset types and trigger conditions, and details a domain‑driven backend architecture—including entities, value objects, aggregates, services, and model‑mapping configurations—to implement a configurable reverse‑operation system.
This article examines the critical issues of overselling, high concurrency, request throttling, and database design in flash‑sale systems, then outlines a comprehensive backend architecture with Redis clustering, Nginx load balancing, dynamic URLs, rate‑limiting, asynchronous order processing, and Java code examples to achieve a resilient high‑throughput solution.
The article reviews the design and implementation of 58.com’s intelligent voice robot backend, detailing its four‑layer architecture, SIP/SDP/RTP protocols, multi‑round voice interaction flow, algorithm service modularization, SIP scheduling optimizations, and Java thread‑pool system tuning for high‑concurrency scenarios.
This article explains the classic Cache‑Aside pattern, analyzes common cache‑database consistency problems in high‑traffic systems, and presents practical solutions—including delete‑first updates, internal JVM queues, lazy recomputation, and routing considerations—to ensure reliable data synchronization under heavy concurrency.
This article explains why database caching is essential, outlines the consistency challenges of using Redis as a MySQL cache, and compares four practical synchronization solutions—ranging from simple TTL expiration to binlog subscription—highlighting their advantages, drawbacks, and appropriate selection criteria.
iQIYI’s contract platform replaced a cumbersome Activiti workflow with a lightweight combination of Axon Framework and Spring StateMachine, leveraging DDD, CQRS, and event sourcing to achieve clear layered architecture, traceable events, and flexible state transitions, while confronting distributed‑transaction sagas, batch limits, and integration complexities, and planning future Axon Server adoption.
This article chronicles Yuque's evolution from a hobbyist prototype to a commercial cloud‑native knowledge platform, detailing its backend migrations, adoption of Node.js, Egg, React, serverless function compute, micro‑service splits, and the architectural lessons learned for stability, cost efficiency, and scalability.
The article examines microservice architecture as an abstract concept and presents three practical decomposition strategies—vertical/horizontal business split, business‑driven and team‑oriented considerations, and criteria based on logic, stability, reliability and performance—while also discussing cost, release frequency, and team size implications.
This article examines why many game companies avoid microservice architectures, highlighting the real‑time latency, stateful memory requirements, and networking constraints that make traditional microservice patterns unsuitable for fast, multiplayer game servers.
This article presents a comprehensive design of a flash‑sale (seckill) system for an automotive e‑commerce platform, covering business requirements, model selection, stock‑deduction strategies, high‑performance and high‑availability architecture, security mechanisms, and future optimization directions, all built on cloud‑native backend technologies.
The article explains how QA engineers should adapt their testing approach when a live‑streaming service evolves from a simple business‑focused system to a modular, scalable platform, covering architecture changes, testing directions such as interface, data preparation, performance, and comprehensive project control.
This article examines the motivations, resource granularity, rule definition, and calculation logic behind implementing rate limiting and circuit breaking in microservice architectures, using examples like Sentinel and Hystrix, and outlines a step-by-step design for integrating these controls with API gateways.
The article details the design and deployment of an AI-powered intelligent voice quality inspection system at 58.com, covering its overall architecture, speech recognition, role identification, tag detection, rechecking platform, and backend infrastructure, and demonstrates its impact on call‑center efficiency and service quality.
This article explains what microservices are, how they communicate, compares Spring Cloud with Dubbo, describes the relationship between Spring Boot and Spring Cloud, and discusses circuit breaking, service degradation, advantages, disadvantages, service discovery tools, and typical technology stacks.
This article explains the fundamental differences between microservice architecture and traditional SOA, emphasizes the importance of proper service boundaries and DDD‑guided decomposition, and compares transaction‑script (anemic) and rich‑model approaches with code examples to illustrate how domain‑centric design improves microservice implementations.
The article examines why tightly coupled microservices cause reliability issues, then presents practical techniques—such as converting synchronous calls to asynchronous messaging, adopting event‑driven architecture, using CQRS, caching, and strategic refactoring—to achieve loose coupling and improve system resilience.
This article explains the real‑world origin of message queues, illustrates how they enable asynchronous processing, traffic control, and service decoupling, and compares their benefits and drawbacks with concrete examples such as flash‑sale systems and token‑bucket flow control.
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 building and operating services, and warns about common pitfalls such as the microservice syndrome.
This article explains the role of message‑queue middleware in distributed systems, covering its core functions, common use cases such as asynchronous processing, application decoupling, traffic shaping, log handling and messaging, and provides concrete architectural examples illustrating performance improvements and design patterns.
FastDFS is an open‑source lightweight distributed file system that tackles large‑scale file storage and load‑balancing by using dedicated Tracker, Storage, and Client roles, offering high performance, easy horizontal scaling, and clear upload/download workflows for web applications.
This article explains the concept of failure‑oriented design, why it matters for large‑scale streaming services, and details concrete architectural patterns—such as layered services, database fallback, cache redundancy, consistency checks, and dynamic traffic switching—used by a production playback control platform.
This article describes how Dada Group tackled rapid micro‑service growth by designing a language‑agnostic, lightweight service governance and traffic routing engine that uses Consul metadata, configurable routing rules, and link‑based isolation to enable online pressure testing, parallel development, hot‑cold service separation, gray releases, and dynamic rate limiting.
Facing soaring order peaks each Double‑11, Alibaba's logistics arm re‑engineered its architecture with RocketMQ, using asynchronous decoupling to handle payment‑order traffic, dramatically reduce hardware spend, and keep logistics QPS stable without sacrificing user experience.
This article provides a comprehensive overview of microservices, covering their definition, independent communication methods, differences between Spring Cloud and Dubbo, the relationship between Spring Boot and Spring Cloud, fault‑tolerance mechanisms like circuit breaking and degradation, advantages and disadvantages, and a comparison of Eureka and Zookeeper for service registration and discovery.
Microservices, introduced in 2012 and popularized by Martin Fowler, decompose applications into small, independent services that communicate via lightweight protocols, enabling modular development, flexible technology choices, independent deployment, and improved scalability, while also introducing challenges such as distributed data consistency, testing complexity, and operational overhead.
This article explains the core concepts, architecture, and practical techniques—including load‑balancing, caching, async processing, and Redis sharding—required to design and implement a high‑concurrency seckill system that can handle millions of requests in a short time window.
The article explains why and how to use message queues to achieve low‑coupling, better performance, fault tolerance, and eventual consistency in an e‑commerce order‑processing flow, discusses common pitfalls such as message loss and duplication, and compares popular queue products like RabbitMQ, Kafka, and RocketMQ.
This article examines the logistical challenges faced by Alibaba's Cainiao platform during Double‑11, explains why traditional databases and Redis fall short, and shows how adopting RocketMQ for asynchronous decoupling dramatically reduced costs and stabilized high‑volume order processing.
This article presents a comprehensive case study on how the 58 rental platform refactored its services and optimized performance by splitting common modules, adopting async interfaces, leveraging nginx + swoole, implementing data caching and pre‑loading, resulting in significant reductions in page rendering time and service latency across major app pages.
This article explains the background, challenges, and architectural design of Tencent Cloud Task (TCT), a distributed scheduling platform that offers precise real‑time task execution, modular microservice architecture, stateless scaling, rich trigger rules, comprehensive monitoring, and advanced workflow orchestration for large‑scale cloud environments.
This article explores the key challenges of designing a flash‑sale (秒杀) backend—such as overselling, high concurrency, request throttling, and database bottlenecks—and presents a complete solution that includes database schema, dynamic URLs, static page rendering, Redis clustering, Nginx load balancing, SQL optimization, token‑bucket rate limiting, asynchronous order processing, and service degradation strategies.
This article explains the product features, technical challenges, technology choices, and detailed architecture design for a live‑streaming quiz application that must support up to one million concurrent users, high QPS, low latency, and secure financial transactions.
This article explains the business scenarios that demand massive, precise, and reliable scheduled tasks, reviews the shortcomings of existing open‑source schedulers, and details the design, architecture, and key features of Tencent Cloud’s distributed task scheduling system TCT, highlighting its modular, stateless, and fully featured approach.
Youku completed a six‑month, full‑scale IPv6 migration in 2018, upgrading client and server stacks, deploying dual‑stack then IPv6‑only networks with 4over6, solving challenges like lack of IPv6 environments, OS module updates, MTU handling, address libraries, CDN coordination, and robust fallback, testing, and monitoring.
This article recounts the four‑year journey of Ele.me's order platform, detailing the transition from a monolithic Zeus system to service‑oriented components, the challenges of sharding, message broadcasting, performance testing, Redis optimization, and the cultural practices that shaped a resilient backend architecture.
This article uses Taobao as a case study to illustrate the step‑by‑step evolution of server‑side architecture from a single‑machine setup to a cloud‑native, highly available system capable of handling tens of millions of concurrent requests, highlighting the technologies and design principles involved at each stage.
This article explores Youzan's enterprise search middle platform, detailing the challenges of siloed architectures, the concept of cognitive folding, comprehensive index design, write/read mechanisms, configuration-driven routing, monitoring, and practical implementations that enable scalable, reusable search capabilities across diverse business domains.
This article examines whether microservice architecture suits large organizations by outlining its cultural, technical, and operational impacts, the reasons to decompose monolithic systems, key considerations for architects, and practical guidance on avoiding deployment coupling while managing complexity.
This article explains the design and implementation of an ABT (Auto‑Bidding Test) system that automates A/B decision cycles, covering client SDK architecture, protocol specifications, data‑point collection, resource‑placement experiments, and home‑page integration to accelerate product growth.
This article walks through the step‑by‑step evolution of a Java‑based e‑commerce platform, illustrating how a single‑machine deployment can be transformed into a scalable architecture using techniques such as server‑database separation, clustering, load‑balancing algorithms, read‑write splitting, caching, sharding, micro‑services and message queues.
This article examines the challenges of building a flash‑sale (秒杀) system—such as overselling, massive concurrent requests, URL exposure, and database overload—and presents a comprehensive backend architecture that leverages Redis clustering, dynamic URLs, Nginx load balancing, rate‑limiting, asynchronous order processing, and service degradation techniques to achieve robust, scalable performance.
This article examines the origins, principles, advantages, and drawbacks of microservice architecture, outlines when it should be adopted, describes its evolution stages, presents design patterns, service‑splitting strategies, and reviews popular frameworks and tools to help teams decide if microservices fit their system complexity and organizational capabilities.
The article details the design principles, modular architecture, and engineering optimizations of a backend algorithm platform that uses APIs, micro‑services, and asynchronous processing to enable fast, reliable, and scalable online algorithm services, including recall, ranking, metadata, feature reporting, and A/B testing.
