This article introduces a DDD scaffolding project, explains its theoretical foundations, presents the layered architecture and generation commands, details coding conventions for each module, and addresses frequent questions and solutions for practical adoption.
This article explains what microservices are, compares them with monolithic architecture, outlines their benefits and challenges, highlights the importance of observability, and reviews the top ten microservice frameworks and best‑practice guidelines for 2023.
This article analyzes the high‑concurrency contract‑query workload of JD Logistics, examines call sources, query dimensions and volume patterns, and proposes a three‑layer protection architecture—Bloom filter, Redis cache, and database fallback—along with strategies for cache penetration, breakdown, and avalanche mitigation.
This article provides a thorough overview of message queues, covering their definition, core components, types (point‑to‑point and publish/subscribe), key characteristics such as asynchrony, loose coupling, distribution and reliability, selection criteria among popular MQ products, and typical application scenarios in high‑concurrency systems.
This article describes how a game‑account order system with scattered core code and no design patterns was refactored into a clean three‑layer interface architecture using a strategy‑template approach, detailing the design, implementation, testing, gray‑release strategy, and post‑deployment safeguards.
Microservice design patterns provide proven solutions for common challenges such as service decomposition, communication, governance, and testing, and this article introduces ten key patterns—including API Gateway, Service Discovery, Circuit Breaker, Bulkhead, CQRS, Event‑Driven, Saga, Strangler, Sidecar, and BFF—to help build efficient, reliable, and scalable systems.
This article presents a detailed collection of 31 Java‑related architecture diagrams—including class loader, JVM, Spring, Hibernate, Struts, Android, cloud computing, Linux kernel, and various enterprise frameworks—providing a visual guide for backend developers seeking a broad understanding of Java ecosystem structures.
The Gaode Business Framework (GBF) is a lightweight, domain‑driven solution that unifies disparate industry portals by partitioning stable domains, standardizing interfaces, and providing customizable implementations, thereby eliminating duplicated glue code, improving design quality, reducing development costs, and enhancing stability and cross‑team collaboration.
This article details the architectural redesign of QQ Music's comment platform—migrating to MongoDB, introducing threaded comments, and employing caching and message‑queue decoupling—to handle massive read/write spikes during celebrity live‑drop events while maintaining high availability and performance.
QQ Music’s comment system was re‑engineered with a MongoDB backend, cache layer, asynchronous writes, split read/write services, priority queues and rate‑limiting, enabling it to endure celebrity‑driven traffic spikes, maintain data consistency, and deliver high‑availability, low‑latency user experiences.
The article presents a modular seller‑fulfillment architecture that replaces order‑type‑centric logic with a fulfillment‑mode‑driven “business identity” abstraction, enabling reusable capabilities, unified APIs, easier maintenance, faster onboarding of new order types, and improved testability and scalability for large e‑commerce platforms.
The article details JDV, JD.com’s internal visual‑big‑screen data platform, describing its architecture, the demanding real‑time, cross‑midnight, and high‑stability requirements during the 618 promotion, the technical challenges faced, and the innovative solutions—including request state control, heartbeat monitoring, video recording, orchestration tools, precise stop handling, and proxy data sources—that ensured reliable large‑scale screen deployment.
Backend Architecturedata visualizationlarge-scale systems
The article outlines the background, design, challenges, and future roadmap of a business search platform within the Weimob Operating System, detailing its architecture, event ingestion, index building, and retrieval services that enable low‑cost, high‑performance search across multiple business domains.
The article presents a comprehensive design and implementation of a unified push notification platform that abstracts variable configurations, systematizes immutable logic, and employs asynchronous processing, sharding, rate limiting, and resource allocation strategies to achieve scalable, reliable, and maintainable multi‑business push services.
Shopee’s unified Image Service consolidates upload, processing, and delivery into a single platform that overcomes legacy fragmentation and heterogeneous networks through resumable SDKs, adaptive ID schemes, link‑level and HTTP/3 transport optimizations, dynamic CDN scheduling, and device‑aware resizing, boosting upload success to 99.67 %, halving latency, cutting storage by 25 % and bandwidth by 56 % while markedly improving app performance.
This article describes the background, design principles, implementation details, performance optimizations, and operational results of a unified push notification platform that abstracts variable configurations, systematizes invariant logic, and supports high‑throughput, reliable messaging across multiple business lines.
Didi’s ride‑hailing backend evolved from a monolithic service to a DDD‑split architecture and the DuKang framework, then standardized components, rendering gateways, function access, and logging to solve multi‑terminal inconsistency, complex rendering logic, cross‑process integration, and data visibility, creating a unified cross‑end rendering platform supporting over twenty pages.
The article describes how a membership system serving billions of users across multiple platforms achieves high performance and high availability through dual‑center Elasticsearch clusters, traffic‑isolated three‑cluster ES architecture, Redis caching with distributed locks, dual‑center MySQL partitioning, and fine‑grained flow‑control and degradation strategies.
This article provides a comprehensive overview of microservice architecture, detailing its core concepts, key characteristics, benefits and drawbacks, and presents ten essential design patterns—including database per service, event sourcing, CQRS, Saga, BFF, API gateway, Strangler, circuit breaker, externalized configuration, and consumer‑driven contract testing—along with their pros, cons, usage scenarios, and technology examples.
This article walks through the step‑by‑step transformation of a simple online supermarket from a single‑node monolith to a fully fledged microservice architecture, highlighting the motivations, common pitfalls, component choices, monitoring, tracing, logging, resilience patterns, testing strategies, and the trade‑offs of frameworks versus service mesh.
This article explains how large hotel‑booking platforms such as Airbnb, Booking.com and OYO use a micro‑service architecture—including hotel management, customer search/booking, and view‑booking services—combined with load balancers, Kafka, Elasticsearch, Redis, Cassandra and Hadoop to achieve a seamless, high‑throughput booking flow.
This article details the evolution from the initial Kaldi‑based speech recognition architecture (version 1.0) to a re‑engineered version 2.0, describing business background, service components, identified shortcomings, and a series of performance, concurrency, GPU, I/O, GC, and dispatch optimizations that dramatically improve resource utilization, latency, and reliability for large‑scale voice processing at 58.com.
The article details how Bilibili's relationship‑chain service scaled from a MySQL‑based design to a distributed KV store, introduced successive caching layers (memcached, Redis hash, Redis KV, bloom filter), and implemented hotspot mitigation techniques to sustain near‑million QPS traffic while ensuring high availability and data consistency.
This article outlines the essential design principles, client optimizations, CDN usage, clustering, caching, database tuning, and service governance techniques needed to create robust high‑traffic, high‑concurrency systems that scale reliably and maintain performance.
This article explains what an API gateway is, outlines its required high‑performance, high‑availability, and extensibility characteristics, details core functions such as routing, load balancing, authentication, rate limiting, and compares popular solutions like Spring Cloud Gateway, Zuul, OpenResty, and Kong.
This article explains the role of API gateways in microservice architectures, outlines their four core functions, discusses design priorities such as high performance, availability, and scalability, and compares major open‑source gateway solutions like OpenResty, Kong, Zuul, and Spring Cloud Gateway.
The article explains distributed ID concepts and business scenarios, compares nine common generation schemes, and details Vivo’s LuBan service architecture—including three built‑in ID formats, custom SPI extensions, Spring‑Boot SDK usage, performance optimizations, and large‑scale deployment metrics—offering practical guidance for building high‑throughput, globally unique ID systems.
This article outlines the essential principles, architectural patterns, client optimizations, CDN usage, clustering, caching strategies, database tuning, and service governance techniques required to design, build, and maintain high‑traffic, high‑concurrency backend systems effectively.
This article explains what microservices are, outlines essential design principles, and details the most important microservices design patterns—including Aggregator, API Gateway, Chain of Responsibility, Asynchronous Messaging, Shared Database, Event Sourcing, Branch, CQRS, Circuit Breaker, and Decomposition—to help developers build robust, scalable applications.
The Prime Video engineering team replaced a costly, scaling‑limited serverless microservice architecture with a streamlined monolithic solution on EC2/ECS, achieving more than a 90% reduction in infrastructure expenses while improving scalability, sparking widespread debate about the true value of microservices and serverless approaches.
The article explains Baidu's need for low‑cost, high‑latency full‑user notifications, analyzes existing IM architecture limitations, introduces a public mailbox read‑expansion approach, compares three push strategies, and details the design, management, caching, tiered release, advantages, drawbacks, and real‑world applications of this solution.
This article explains the principles, process management, sequence, and structural design of a message notification system within microservice architectures, highlighting production‑consumption patterns, task handling, state transitions, channel integration, and practical considerations for effective backend implementation.
Backend ArchitectureMessage Notificationmessage center
This article examines data dependency challenges among microservices in a supply‑chain system, compares initial data‑redundancy designs with a decoupled real‑time synchronization approach, evaluates open‑source middleware options, and explains why Bifrost was chosen to achieve stable, low‑latency data sharing.
This article explains why API gateways are essential in micro‑service architectures, outlines their four core functions, discusses high‑performance, high‑availability, and scalability design goals, and compares major open‑source gateways such as OpenResty, Kong, Zuul, and Spring Cloud Gateway to help engineers choose the right solution.
This article presents a comprehensive engineering case study of a high‑traffic membership system, detailing the dual‑center Elasticsearch high‑availability design, traffic‑isolated three‑cluster ES architecture, Redis caching strategy, dual‑center MySQL partitioning and migration plan, abnormal member relationship governance, and future fine‑grained flow‑control and downgrade policies.
This article explains why microservice architecture is preferred over monolithic applications, outlines a clear learning roadmap, and details essential components such as Docker, container orchestration, API gateways, load balancing, service discovery, event buses, logging, monitoring, distributed tracing, persistence, caching, and cloud providers.
This article presents a comprehensive overview of component-based development at ZhaiZhai, detailing the background, current challenges, the component model, classification, design, deployment process, performance gains, supporting ecosystem, and concluding insights, all supported by references and practical examples.
BFFBackend ArchitectureComponent-based Development
This article details the end‑to‑end design of a coupon system for a rental listing platform, covering business flow, database schema, state management, caching strategies, distributed locking, and optimization techniques using design patterns, Redis, MySQL, and message queues.
The article explores the challenges and motivations behind large‑scale system refactoring, covering stability, coding standards, business rule changes, meeting structures, requirement juggling, technology selection, service division, migration, and implementation strategies, while emphasizing the need for strong team coordination and strategic trade‑offs.
This article provides a comprehensive technical overview of Kafka, covering its core message‑queue value, architecture components such as producers, consumers, topics, partitions and replication, high‑performance mechanisms like zero‑copy and OS cache, resource planning for disks, memory, CPU and network, operational tools and commands, consumer‑group management, rebalance strategies, and internal scheduling mechanisms such as the time‑wheel.
Event sourcing models state changes as immutable logs, and when combined with CQRS and Kafka Streams, it enables scalable, fault‑tolerant architectures where write and read paths are decoupled, supporting local or external state stores, interactive queries, and zero‑downtime upgrades.
This article explains the core concepts, design principles, and key differences among RESTful, SOAP, RPC, SOA, and microservices, illustrating how they relate to each other and why modern architectures increasingly adopt microservices for scalability and business agility.
This article provides a comprehensive overview of API gateway fundamentals, compares popular open‑source gateways, and details a custom Traefik‑based microservice gateway architecture with routing, authentication, protocol conversion, and high‑performance connection pooling.
API GatewayBackend ArchitectureProtocol Conversion
The article by Tencent backend expert Lv Yuanfang explains how to design scalable mobile‑internet backend architectures and push services by defining clear protocol boundaries, aligning system components with team organization through a conversion‑layer service, and implementing comprehensive feedback loops—including health metrics, monitoring, and data‑driven analysis—to ensure high availability and low coupling.
The ZZ Business Check Platform (ZZBCP) is a backend system designed to detect and correct real‑time data anomalies across complex C2C, C2B, B2B, B2C, and C2B2C transaction flows by integrating message subscription, rule execution, alerting, automatic repair, and monitoring modules.
This article presents a comprehensive, seven‑dimensional design for a flash‑sale (秒杀) system, covering business characteristics, overall architecture, peak‑limiting, Nginx configuration, page optimization, Redis clustering, message‑queue throttling, database design, captcha mechanisms, and key precautions for achieving high throughput and reliability.
This article explores the comprehensive design of order business systems, covering background considerations, order lifecycle management, technical solutions such as ID generation, parallel and asynchronous processing, timeout handling, distributed transactions, and data strategies like sharding and synchronization.
This article explains the reasons for splitting monolithic applications, outlines preparation steps, and provides detailed practical guidance on database vertical and horizontal splitting, global ID generation, migration, cut‑over strategies, consistency, and post‑split stability measures.
This article explains Alibaba's Java development specifications for layered domain models, detailing the roles, naming conventions, and usage of objects such as DO, DTO, BO, VO, PO, DAO, and POJO to improve code organization and reduce coupling across application layers.
This article examines the open‑source Twitter recommendation algorithm released by Elon Musk, detailing its main services, machine‑learning models, data sources, programming languages, and the GitHub repositories that host the core components such as SimClusters, TwHIN, rankers, and the Rust‑based navi framework.
The article examines the pitfalls of turning a monolithic application into a ‘distributed monolith’ during microservice migration, highlighting how improper domain splitting, excessive synchronous remote calls, and lack of protective mechanisms can degrade stability and negate expected productivity gains.
This article explains how to design a high‑performance short‑URL service capable of handling 1 million queries per second, covering system background, URL shortening principles, base‑62 encoding, distributed ID generation options, storage sharding, ambiguity checking with Bloom filters, multi‑level caching, and redirect handling.
This article details the architecture, component‑based design, dynamic template generation, batch processing, activity management, and technical challenges such as custom component rendering, condition‑expression creation, and high‑concurrency coupon issuance for a scalable e‑commerce coupon platform.
This article explains how to build a highly reusable shared order service by clearly defining its boundaries, abstracting its internal data model and interfaces, and handling order status management with both main and sub‑status mechanisms, while avoiding tight coupling with other services.
The article describes the design and implementation of Taobao Dou Dizhu’s new single‑player endgame mode, which generates daily unique puzzles with a guaranteed single solution, manages activity triggers, Redis caching, AI interaction, fault tolerance, consistency, and reward idempotency, boosting user retention during promotions.
This article explains how event sourcing models state changes as immutable logs, discusses the trade‑offs of the pattern, and shows how Apache Kafka and Kafka Streams enable CQRS and interactive queries for building scalable, resilient backend applications.
This article examines how modern modular monoliths, especially Spring Modulith, can provide scalable, low‑overhead alternatives to microservices by isolating modules, reducing remote calls, and simplifying deployment while addressing common concerns about complexity and performance.
This article explains what domain events are, how to define them with proper naming and attributes, explores multiple techniques for publishing events in Go—including parameter injection, static-like helpers, return‑based and repository‑based approaches—and describes strategies for consuming events safely and atomically.
The article examines how microservices interact, compares RPC and event‑driven approaches, analyzes different types of coupling, discusses event notification, event sourcing, API gateways, versioning, and offers practical guidance on reducing tight coupling and deciding the appropriate microservice architecture.
This article explains how application services act as a façade for domain models, outlines key design principles, shows practical Go/Java implementation patterns, discusses transaction propagation and security handling, and provides concrete best‑practice recommendations for building thin, framework‑agnostic backend services.
This article explains the role of an order system in traditional e‑commerce, outlines its main functional modules, describes the end‑to‑end order flow—including creation, payment, production, confirmation and completion—covers inventory reduction strategies, order splitting, reverse processes, state‑machine design, and discusses future evolution toward a unified order center.
This article details Meituan's three‑stage evolution of its self‑developed Code platform—from a single‑machine service to a multi‑machine read‑write‑separated system and finally to a distributed, sharded architecture—highlighting the scalability and high‑availability challenges faced and the engineering solutions implemented.
This article introduces the DuoliXiong local‑service platform, analyzes the challenges of its multi‑platform permission management, and details the design of a role‑based access control (RBAC) system—including model selection, database schema, tree‑structured permission representation, multi‑business‑line isolation, and data‑level (row/column) permissions—culminating in a scalable solution for complex B‑end and O‑end applications.
The article discusses various expert approaches to microservice decomposition, highlighting vertical and horizontal splits, business logic, stability, reliability, performance considerations, and team size implications, offering practical guidance for backend architects in design.
This article details GitHub’s 12‑step journey from a 12‑year‑old Ruby on Rails monolith to a modular microservices architecture, covering rapid growth, data partitioning, service extraction, operational shifts, and resilient design principles to empower developers while maintaining product value.
This article describes how a review middle‑platform for a video service standardizes communication protocols with RocketMQ, defines unified data processing flows, and implements an automated business‑access detector with Java code to reduce duplication and improve development efficiency.
To support Southeast Asian live-streaming, we designed a custom danmaku system capable of handling up to a million concurrent users per room, tackling bandwidth pressure, weak-network latency, and reliability by employing HTTP compression, response simplification, short-polling, local caching, and lock-free ring buffers.
A seemingly simple API change revealed deep flaws in parameter handling, prompting a review of technical, business, and flow‑control parameters and outlining essential API design principles to keep internal logic hidden and maintain clean, maintainable services.
This article provides a comprehensive overview of microservice architecture, outlining four major technology domains—management, storage, business support, and DevOps—and lists the most relevant tools and platforms for each, helping architects choose optimal solutions for their projects.
This article examines why game companies' servers often avoid microservice architectures, emphasizing the real‑time latency, stateful processing, and networking constraints that make traditional microservice approaches unsuitable for high‑performance game back‑ends and why alternative designs such as custom TCP solutions or stateful server clusters are preferred.
The Xianyu team introduced a lightweight, API‑driven state‑machine framework that replaces massive IF‑ELSE order‑fulfillment code with a three‑layer architecture—core topology, glue adapters, and business processors—enabling concise topology definitions, reusable validation/action logic, automatic logging, monitoring, and effortless extension across recycling, consignment, and inspection services.
The iDesk service platform is a comprehensive internal tool that evolved through three development phases, adopts a BS+Service architecture with modular local services, offers extensive software management and self‑service utilities, integrates tightly with TripPal and service accounts, and implements robust operational monitoring to achieve high availability and user satisfaction.
This article analyzes the functional decomposition, data structures, system architecture, push‑pull mode selection, and message flow of a one‑to‑one instant messaging service, providing practical design guidelines and example Redis/MySQL schemas for building a scalable chat backend.
This article explains how a fintech payment platform achieves high availability and optimal channel selection by using decision‑tree routing, sliding‑window negative‑feedback, pressure‑detection services, and component fallback strategies such as RabbitMQ with Redis, supporting millions of daily transactions.
The article explains various high‑availability solutions for stateful backend services, comparing cold backup, dual‑machine active/standby, same‑city active‑active, cross‑city active‑active, and cross‑city multi‑active approaches, and discusses their trade‑offs, implementation details, and real‑world examples from large internet companies.
This article explains Baidu's Duoli Bear permission system, detailing its business context, challenges of multi‑role and platform isolation, and the custom RBAC design that uses a tree‑structured menu, role‑based data rules, and business‑line isolation to manage access across diverse services.
This article presents a practical methodology for handling complex business scenarios by combining top‑down process decomposition with bottom‑up domain modeling, illustrating the approach with a retail product onboarding case, code examples, and guidance on capability sinking and model‑driven design.
This article shares engineering practices for constructing a tag‑profile system, covering core concepts, minimal architecture, technology selection, key modules such as estimation, selection, deployment, and validation, and offers design details and implementation tips for large‑scale marketing scenarios.
A technical discussion explains that game servers prioritize ultra‑low latency and stateful in‑memory communication, making micro‑service architectures impractical despite their benefits for modularity and scaling, especially in fast‑paced MOBA titles.
This article explains how a large‑scale membership system achieves high performance and high availability by using a dual‑center Elasticsearch cluster, traffic‑isolated three‑cluster architecture, Redis caching with dual‑center clusters, and a MySQL partitioned dual‑center setup, while also detailing optimization, migration, and fine‑grained flow‑control strategies.
This article explains practical ways to achieve extensibility at multiple layers—code, API, framework, and system platform—by using design patterns, JSON‑based APIs, SPI mechanisms, and extension‑point architectures to minimize impact on existing functionality.
This article presents a complete end‑to‑end design of a coupon system for a rental‑listing platform, covering business flow, database schema, activity management, coupon issuance, binding, user redemption, state‑machine implementation, caching strategies, stock deduction, redemption handling, and future scalability optimizations.
This article details the business flow, database schema, micro‑service architecture, caching strategies, state‑machine implementation, and concurrency handling for building a robust coupon system that enables merchants to bind coupons to rental listings and attract end‑users.
This article explains the role of domain services in Go‑based Domain‑Driven Design, outlines three situations where they are appropriate, shows how to implement them statelessly, recommends functional package organization, and demonstrates dependency inversion with interfaces and infrastructure implementations.
This article analyzes Baidu's Janus gateway—why it was built despite BFE, its architecture and deployment, three‑layer routing design, variable and condition expression languages, performance benchmarks versus raw Go code, and how its plugin system enables both generic and highly customized traffic‑dispatch solutions.
This article details the redesign of a service health‑check component, covering its original limitations, industry alternatives, the chosen centralized active checking approach, architectural modules, concurrency model, scaling mechanisms, gray‑release strategy, and performance optimizations for reliable distributed systems.
This article explains why monolithic applications should transition to microservices, defines microservice architecture, compares Dubbo and Spring Cloud frameworks, and provides detailed strategies for decomposition, CI/CD, container orchestration, automated operations, and governance to achieve a scalable, maintainable system.
This article outlines product analysis and positioning, microservice architecture principles, the evolution of real‑time message push technologies, strategies for ensuring request idempotency, and comprehensive service governance practices, providing practical guidelines for building robust backend systems.
NetEase’s advertising engine platform evolved from a monolithic, high‑concurrency system handling over a billion daily requests into a layered, distributed architecture that unifies indexing, billing, user‑tagging, and monitoring services, leverages Elasticsearch and custom extensions for fast retrieval, and plans further upgrades such as a custom retrieval kernel and Go‑based services.
Advertising PlatformBackend ArchitectureDistributed Systems
This article examines the technical challenges of B‑end contract advertising systems, tracing the evolution of Baidu's ad‑placement platform from a monolithic architecture through multiple business stages to a domain‑driven microservices design, and discusses service governance, observability, anti‑corruption, and iterative development practices.
This article introduces a modular backend service architecture based on Domain-Driven Design, explaining project structure, module composition, hexagonal architecture, and practical code examples using Spring Cloud, illustrating how to achieve flexible, maintainable services through domain models, adapters, and proper boundary definitions.
This article provides a comprehensive overview of process engines, explaining their definition, common scenarios such as workflow and BPM, various design approaches for process designers, form designers, and interfaces, and detailed architectural guidance for building and deploying BPM solutions in backend systems.
This article uses Taobao's backend as a case study to illustrate how a high‑traffic e‑commerce system evolves through ten‑plus architectural stages—introducing distribution, high availability, load balancing, caching, database sharding, micro‑services, ESB, containerization, and cloud platforms—while highlighting the bottlenecks each stage resolves and the design principles that guide the evolution.
This article describes how Meituan built Logan, a high‑performance, end‑to‑end real‑time logging platform for mobile, web, mini‑programs and IoT, covering its background, architecture, data collection, processing, consumption, monitoring, deployment strategies, achieved results and future roadmap.
This article provides an in‑depth overview of API gateways, explaining their basic concepts, design principles, key features such as request routing, service registration, load balancing, resilience and security, and compares popular gateway solutions like OpenResty, Kong, Zuul and Spring Cloud Gateway for microservice architectures.
This article explains the role, architecture, core modules, workflow, inventory management strategies, and future evolution of order systems in traditional e‑commerce enterprises, illustrating design considerations, process steps, and state‑machine modeling for efficient order handling.
The article recaps DeWu Technology's inaugural Hangzhou tech salon, highlighting speaker insights on e‑commerce backend service stability, intelligent customer‑service evolution, anti‑spoofing facial‑recognition technology, and a six‑module fulfillment platform architecture, while showcasing the team's rapid growth and future goals.
AI Customer ServiceBackend ArchitectureSupply Chain