This article explains how an event‑center abstracts domain events, offers a clear architecture and powerful features, compares it with raw message‑queue solutions, and provides Java code examples to help backend engineers adopt a more maintainable, decoupled design.
This article explains how to apply Domain‑Driven Design in a Java backend project, detailing the responsibilities of each layer—domain, infrastructure, application, adapter, client, and start—along with practical code examples for a work‑order system.
The article explains why microservices have become a mainstream architectural style, outlines the problems of monolithic systems, presents core microservice characteristics, offers practical decomposition principles and patterns, compares microservices with monolith, distributed, serverless, SOA and service‑mesh architectures, and lists common technology stacks for implementation.
This article outlines the design of an internal WebSocket communication service that abstracts real‑time messaging, reduces code coupling, supports various business scenarios, ensures reliable delivery with RabbitMQ, defines unified APIs and message formats, and demonstrates a DDD‑based project structure for easy integration.
Facing a 600k/min rate‑limit alert on a game’s product‑update MQ, the team analyzed scattered consumers, designed a new Flyweight‑Strategy architecture with Spring AOP idempotency, executed a three‑phase migration, and achieved a 50‑80% reduction in downstream interface calls.
The article explains why microservices have become a mainstream architectural choice, outlines the shortcomings of monolithic systems, presents core design principles and various service‑splitting methods, discusses the synergy with Domain‑Driven Design, compares microservices with other architectures, and lists typical technologies used in practice.
This article describes the background, objectives, core design, reliability mechanisms, message classification, API design, and unified calling approach of a company‑wide WebSocket abstraction layer that replaces polling, supports asynchronous communication, and ensures reliable message delivery using RabbitMQ and confirm mechanisms.
This article analyzes common data‑inconsistency problems in order‑placement workflows that involve many external services and presents a lightweight final‑consistency architecture with practical design guidelines, retry strategies, and compensation mechanisms to ensure reliable backend processing.
This article provides a comprehensive analysis of microservices, covering why they are adopted, the drawbacks of monolithic architectures, core characteristics, splitting principles and strategies, the relationship with Domain‑Driven Design, comparisons with other architectural styles, and a detailed overview of the common technical stack used to build and operate microservice systems.
This article explains microservice service governance, covering registration and discovery, load balancing, rate limiting, circuit breaking, dynamic configuration management, and monitoring using tools like Nacos, Dubbo, Sentinel, Prometheus, and SkyWalking.
This article explains the concept of high concurrency, its key metrics, and presents four practical backend solutions—static/dynamic separation with CDN, read‑write separation using NoSQL and CQRS, various caching techniques, and lightweight read‑optimisation—to improve performance and scalability of distributed systems.
This article details the architecture, design principles, data preparation methods, verification processes, and error‑handling strategies of ZuanZuan's payment reconciliation system, highlighting how large‑scale data, binlog ingestion, Hive archiving, and MQ‑based workflows ensure accurate and secure financial settlements.
This article examines whether a Service layer in a Spring‑based backend should use interfaces, critiques the common justifications, proposes a top‑down coding workflow, explores AOP proxy options, and presents modular project structures for single or multiple implementations.
This article explains the fundamentals of distributed architecture, covering its key characteristics, microservice principles, Spring Cloud implementations, Service Mesh concepts, and essential components like distributed storage, caching, and transaction management for building scalable, resilient backend systems.
This article explains the fundamentals of distributed RPC, outlines its end‑to‑end communication workflow, and compares major frameworks such as gRPC, Apache Thrift, Dubbo, Spring Cloud Netflix, ZeroMQ, Apache Avro, and gRPC‑Web, helping developers choose the right solution for their microservice architecture.
This article explains what a service gateway is, why it is needed in micro‑service architectures, outlines its core functions such as routing and filtering, discusses deployment considerations, and presents a practical technology stack including Spring Boot, Zuul, Consul, JWT, Prometheus, and ELK.
This article examines whether defining separate interfaces for Service and DAO layers is necessary in Spring projects, debunks common justifications, proposes a bottom‑up development workflow, and outlines project structures for single and multiple implementations, highlighting both benefits and drawbacks.
This article details how a large‑scale lottery service was architected and tuned for extreme traffic spikes by applying server‑side rate limiting, application‑level throttling, behavior‑based filtering, caching strategies, database optimizations, and hardware upgrades, resulting in a ten‑fold performance improvement.
The 2024 CCTV Spring Festival Gala live stream employed comprehensive stability assurance practices across signal encoding, CDN distribution, request handling, and playback—using multi‑source encoding, multi‑level origin redundancy, multi‑cluster HA, and P2P‑augmented delivery—to handle massive QPS spikes, ensure high availability, and provide a resilient, high‑quality viewing experience.
This article explains the relationship between MySQL and Redis, discusses why cache consistency is challenging, and details four cache update design patterns—delete‑then‑update, update‑then‑invalidate (Cache‑Aside), read/write‑through, and write‑behind—illustrating each with flow diagrams and practical considerations.
This article examines the challenges of service proliferation in a microservice‑based system, defines modularity and granularity, and presents systematic splitting and merging factors—such as responsibility, fault tolerance, performance, scalability, cost‑benefit, and team size—using a concrete Promise service case study to guide optimal service design.
The article outlines a comprehensive microservice architecture by describing essential backend components such as Nginx as the traffic entry, Spring Cloud Gateway, service registries like Nacos, Redis caching and distributed locks, MySQL persistence, Elasticsearch, message queues, ELK logging, distributed schedulers, and object storage solutions, while also noting related tooling and best‑practice considerations.
Bilibili’s video submission platform uses a layered micro‑service architecture with a DAG‑based scheduler, extensive observability, and HA tactics such as sharding, 64‑bit ID migration, full‑link stress tests, chaos engineering, and multi‑active data‑center deployment, while tooling like trace correlation and automated alerts ensures stability and guides future hybrid‑cloud migration.
This article walks through the evolution from a single‑Tomcat deployment to a multi‑layer load‑balancing architecture using Nginx, a gateway, LVS, and DNS, explaining static‑dynamic separation, high‑availability strategies, and performance trade‑offs for scalable backend systems.
This article provides a comprehensive overview of a typical microservice architecture, detailing the roles of Nginx as the traffic entry, gateways, business services, service registries, caching, databases, messaging, logging, scheduling, and distributed storage, and offering practical guidance for high‑availability deployment.
iQIYI’s Video Relay Service ensures uninterrupted video playback by employing a two‑region, three‑center hybrid cloud architecture, multi‑layer storage, cross‑AZ retry mechanisms, protective rate‑limiting and degradation paths, layered monitoring, and rigorous stress‑testing and chaos engineering to achieve high availability and disaster recovery.
This article explains the motivation, architecture, resource estimation, code generation algorithms, data modeling, database partitioning, caching strategies, and implementation details for building a scalable short URL system that handles billions of links and high QPS workloads.
The article shares ten real‑world problems encountered in a Spring Cloud Alibaba microservice project—ranging from poor service decomposition and shared databases to chaotic configuration, unnecessary components, and deployment mistakes—offering insights to help teams prevent similar pitfalls.
This article compares four distributed transaction solutions—local message tables, RocketMQ transactional messages, Seata AT mode, and Seata TCC mode—detailing their advantages, limitations, workflow phases, and common exception‑handling techniques for ensuring data consistency across services.
This article explores the key challenges of building a large‑scale instant‑messaging service—including message reliability, ordering, read‑sync, data security, avalanche effects, and weak‑network handling—and presents practical architectural and algorithmic solutions for each problem.
This article explains the roles, differences, and use‑cases of API gateways, load balancers, and reverse proxies, covering real‑world analogies, types, algorithms, advantages, disadvantages, and practical product examples to help you choose the right component for modern web architectures.
The article details a Golang‑based high‑throughput long‑connection service for live‑streaming, describing its five‑layer architecture, multi‑protocol support, load‑balancing, message‑queue decoupling, aggregation with brotli compression, multi‑region deployment, priority channels, and future enhancements for observability and intelligent endpoint selection.
This article dissects WeChat's early message‑sending and receiving architecture, explaining how the system meets real‑time delivery and no‑loss guarantees through a multi‑stage server pipeline, push notifications, and a sequence‑based acknowledgment mechanism, illustrated with concrete flow diagrams and numeric examples.
The article examines a complex supply‑chain system built on Spring Cloud, identifies issues with interface placement and tangled service dependencies, proposes an intermediate API layer and later a BFF pattern, and evaluates the trade‑offs, implementation details, and remaining challenges of these architectural changes.
This article provides a comprehensive overview of microservice architecture, detailing its definition, key characteristics, advantages and disadvantages, and presenting 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, and appropriate scenarios.
An in‑depth look at WeChat’s early messaging system reveals how its backend architecture—comprising ConnectSvr, SendSvr, PushSvr, and a sequence‑based loss‑prevention mechanism—ensured near‑real‑time delivery and prevented message loss, even under weak network conditions.
The article systematically compares eleven technical approaches for automatically closing expired e‑commerce orders, detailing each method’s implementation steps, trade‑offs, performance characteristics, and ideal deployment scenarios, and finally ranks them to guide practical selection.
This article examines practical strategies for automatically canceling unpaid orders, comparing simple timer‑based polling, cluster‑ready schedulers like Quartz, Elastic‑Job, and XXL‑JOB, as well as delayed‑message approaches using RocketMQ and Redis, and offers best‑practice guidelines for concurrency, monitoring, and fault tolerance.
The article explains how microservice systems handle service calls, compares RPC and event‑driven (message) communication, details various coupling types, discusses event notification and event sourcing, and offers practical guidance on reducing tight coupling through API gateways, versioning, and gRPC.
This article outlines the design of a unified solution platform for customer service, detailing the separation of dynamic workflows and static knowledge bases, the architecture of a custom process engine, and a resource engine for API integration, while highlighting implementation challenges and future automation goals.
This article explains what distributed systems are, why they are essential for scaling and high availability, and walks through core technologies such as service frameworks, caching, file systems, locks, ID generation, transactions, messaging, and other essential components.
This article explains how Kuaishou tackled the growing complexity of its recommendation system by developing the Dragonfly strategy engine framework, detailing the challenges, architectural abstractions, DSL-based workflow composition, data handling, ecosystem tools, and future development plans.
This article details the end‑to‑end design of a payment system, covering transaction flow, horizontal and vertical pre‑optimizations, task scheduling, sharding strategies, data structures, high‑availability mechanisms such as channel isolation and Hystrix, and future planning for dynamic scaling and intelligent routing.
This article presents a comprehensive case study of applying domain‑driven design, layered architecture, and microservice decomposition to a restaurant scenario, detailing domain analysis, modeling, upstream‑downstream relationships, architectural mapping, and functional design to guide backend developers in building maintainable systems.
This article details the design and implementation of a highly available membership system that handles billions of users and peak traffic of over 20,000 TPS, covering Elasticsearch dual‑center master‑slave clusters, traffic‑isolated three‑cluster architecture, Redis caching with distributed locks, and dual‑center MySQL partitioning.
This article explores how PayPal achieved the processing of billions of daily transactions using only eight virtual machines by adopting an actor‑model architecture built with Go, detailing the underlying challenges, network and resource optimizations, and providing a complete Go code example.
This article details Baidu’s internally built unified long‑connection service in Go, covering its motivation, architecture, functional implementation, performance optimizations, multi‑business support, deployment strategy, and lessons learned for delivering secure, high‑concurrency, low‑latency real‑time connectivity across mobile applications.
Baidu’s Go‑based unified long‑connection service delivers secure, high‑concurrency, low‑latency connections for multiple Baidu apps through a four‑layer architecture (SDK, control, access, routing), employing goroutine pooling, two‑layer connection models and binary routing to support tens of millions of concurrent users and million‑level QPS, while simplifying integration and reducing maintenance costs.
This article explains the concept, architecture, strategy configuration, and execution mechanisms of a gray (canary) release system for microservices, covering simple designs, Nginx and gateway implementations, and complex multi‑service and database scenarios with practical code snippets.
This article explains the concepts, design principles, and key differences among RESTful, SOAP, RPC, SOA, and microservices, and outlines why microservices have emerged as an evolution of SOA, illustrated with typical framework examples and architectural evolution diagrams.
This article explains the core design goals, sharding strategies, replication models, communication protocols, cache selection, and monitoring techniques needed to build high‑performance, highly available, and scalable distributed cache systems for large‑scale internet applications.
This article explains the essential "three high" goals of system design—high availability, high throughput, and high scalability—detailing their meanings, common architectural patterns such as Hot‑Hot, Hot‑Warm, leader‑based clusters, and practical techniques like caching, async processing, and micro‑service isolation to build robust, scalable services.
This article explains asynchronous messaging patterns, compares RabbitMQ and Apache Kafka in depth, and provides a step‑by‑step decision guide that highlights their architectural differences, strengths, weaknesses, and suitable use‑cases for modern software systems.
This article walks through the design of a billion‑user group chat platform, covering functional and non‑functional requirements, core components, database schema, face‑to‑face group creation, message flow, storage strategies, and performance‑optimizing techniques such as clustering, message queues, multithreading, and Redis caching.
This article explains how Bilibili's account platform was refactored into a unified multi‑tenant microservice system, covering the background problems, domain‑driven design, data isolation strategies, configuration‑driven tenant onboarding, deployment models, gray‑release migration, and solutions for bidirectional data sync loops.
Kuaishou’s Dragonfly framework replaces tightly‑coupled C++ recommendation code with a Python‑centric DSL that compiles to high‑performance JSON, offering DAG‑based operators, schema‑free dataframes, and a full ecosystem of debugging, tracing, and governance tools, dramatically cutting code volume while enabling fast, scalable scenario development.
A senior architect discusses the challenges of applying microservice architecture to real‑time game servers, highlighting latency, stateful processing, and network overhead, and shares multiple expert opinions on when microservices are appropriate versus when monolithic designs are preferable for high‑performance gaming.
This article describes how Kuaishou built the Dragonfly strategy engine framework—covering problem analysis, architecture design, DSL-based workflow orchestration, process and data abstractions, ecosystem tools, and future plans—to solve the scalability, coupling, and maintenance issues of its rapidly expanding recommendation services.
In a recent interview with a listed game company, the author explores why microservice architectures, despite their popularity for scalable web applications, often clash with the low‑latency, state‑heavy requirements of real‑time game servers, highlighting technical and team‑size considerations.
This article explains the concept of query separation, its suitable scenarios, implementation methods—including synchronous, asynchronous, and binlog approaches—storage options, MQ considerations, and how it can dramatically improve query performance for massive tables.
This article outlines nine practical best‑practice steps for designing a low‑complexity, high‑efficiency microservices ecosystem, covering principles such as the Single Responsibility Principle, cross‑functional team organization, appropriate tooling, asynchronous communication, DevSecOps security, independent data stores, isolated deployment, orchestration, and effective monitoring, each illustrated with concrete examples.
The article reflects on the promises and pitfalls of microservices, comparing them to monolithic architectures, and shares practical lessons about scalability, deployment complexity, data consistency, and when a monolith might actually be the better choice.
This article examines how YouTube achieved massive scalability using a simple tech stack, a "flywheel" process, strategic outsourcing, caching layers, and three core pillars—statelessness, replication, and partitioning—while keeping the engineering team lean and adaptable.
This article explains how PHP‑FPM and Nginx interact via FastCGI, detailing the roles of master and worker processes, configuration directives, and the differences between TCP and Unix socket communication methods.
This article details the architecture, core algorithms, security measures, and performance optimizations of a high‑throughput short‑link service, covering hash‑based ID generation, Base62 encoding, distributed ID schemes, caching, database indexing, sharding, and monitoring to ensure efficient and secure URL shortening.
This article explains the business scenarios that drive the need for globally unique distributed IDs, analyzes the challenges of uniqueness, performance, and availability, and details Vivo's self‑built LuBan ID service—including its architecture, three ID formats, custom extensions, SDK usage, performance optimizations, and real‑world deployment metrics.
This article explains Huolala’s multi‑group microservice architecture, covering its background, core principles, deployment, discovery, routing strategies, extension mechanisms, and practical application scenarios that enable flexible, versioned, and policy‑driven service routing.
This document outlines the business scope, value, overall and real‑time data layer architecture, design advantages, data model, extensibility, and future challenges of the order system, emphasizing decoupling, high availability, scalability, and cost control.
This article dissects the design of WeChat's group chat system, covering functional and non‑functional requirements, high‑level component architecture, database schemas, face‑to‑face group creation, real‑time messaging, red‑packet algorithms, and Go code implementation, revealing how massive concurrency, performance, and storage challenges are solved.
This article explains the different types of coupling in microservice architectures, compares RPC and event‑driven communication methods, discusses event notification and event sourcing, and offers practical guidance on choosing and combining these approaches to reduce tight coupling while maintaining system flexibility.
Vivo tackled high CPU overhead in large‑scale Dubbo deployments by disabling unused routers, caching routing results with BitMap intersections and epoch validation, optimizing weight calculations, and adding a grouping router, which together delivered over 100 % TPS gains for 20 k+ providers and cut CPU usage by roughly 27 %.
The article details JD Logistics' order system redesign using a four‑layer transaction architecture, describing its decoupled backend, unified data model, high‑availability components such as CQRS, Redis, JMQ, HBase, and Elasticsearch, and outlines design advantages, extensible data modeling, future challenges, and overall performance outcomes.
This article explains the core components of RocketMQ—including NameServer, Broker, Producer, and Consumer—detailing their functions, deployment diagrams, and how the middleware supports high‑concurrency scenarios such as peak shaving, asynchronous messaging, fault tolerance, and system decoupling.
This article introduces asynchronous messaging patterns, then compares RabbitMQ and Apache Kafka by examining their internal architectures, message models, and trade‑offs, helping architects choose the appropriate solution based on scenario requirements in modern.
The article examines the alluring promises of microservices—such as faster deployments, independent scaling, and team autonomy—while revealing the hidden complexities like deployment chaos, service discovery, data consistency, latency, and the nostalgic appeal of monolithic architectures, ultimately offering three key takeaways for architects.
This article details the design and optimization of a high‑throughput live‑streaming danmaku system, covering background requirements, bandwidth challenges, short‑polling versus WebSocket delivery, compression and frequency controls, service splitting with caching and lock‑free ring buffers, and reports successful handling of 700 k concurrent users during a major event.
This article presents a comprehensive guide to building a payment funds account system, covering core concepts such as account balance, ledger, and voucher, accounting principles like double‑entry bookkeeping, storage choices with TDSQL, security measures using the STRIDE model, consistency guarantees, distributed transactions, high‑availability design, and operational practices such as idempotency, rate limiting, and thorough auditing.
This article presents a comprehensive guide to designing and implementing a secure, cloud‑native funds account system for payment platforms, covering core concepts such as account structure, balance and transaction logs, accounting principles, storage selection, distributed transactions, security measures, consistency, availability, and best‑practice architectural patterns.
This article details the design of a decoupled, high‑availability order system, covering business scope, value propositions, layered architecture, real‑time data layer, read/write separation, caching, messaging, search, multi‑tenant support, data security, and future challenges such as personalized queries and cost‑effective scaling.
This article walks through the full lifecycle of building a ride‑hailing platform, covering the impact of emergencies, requirement analysis, high‑level and detailed architecture, long‑connection management, GeoHash location algorithms, and experience‑optimisation techniques to ensure reliable, real‑time dispatch.
This article explains how to design a practical feed‑flow system for enterprises, covering core concepts, feed types, initialization, push‑pull versus pure push strategies, and provides key Java code snippets that illustrate Redis‑based storage and update mechanisms.
This article explains the fundamentals of Reactor and Proactor event‑handling patterns, discusses Linux’s limited AIO support, and presents seven practical server concurrency models—from single‑threaded accept to multi‑process thread‑pool designs—detailing their workflows, advantages, drawbacks, and suitable use cases.
This article outlines essential architectural and operational strategies—including page static‑generation, CDN acceleration, caching layers, asynchronous processing, thread‑pool and MQ integration, sharding, connection pooling, read/write splitting, indexing, batch processing, clustering, load balancing, rate limiting, service degradation, failover, multi‑active deployment, stress testing, and monitoring—to build robust, high‑concurrency backend systems.
The article examines why many microservice migrations end up as distributed monoliths, highlighting the hidden costs, stability issues, and common pitfalls such as excessive synchronous calls and lack of protection mechanisms, and offers practical guidance to avoid these traps.
This article presents Xiaohongshu's evolving recommendation engineering architecture, detailing its modular backend design, graph-based Ark framework, hot deployment mechanisms, and the challenges and solutions for scaling personalized content delivery in a fast‑growing mobile platform.
This article examines the challenges of maintaining data consistency across micro‑service boundaries, walks through real‑world payment and gifting scenarios, compares classic solutions such as 2PC, saga, TCC, local‑message tables and transaction messages, and finally recommends a pragmatic approach for building reliable distributed transaction mechanisms.
This article explores comprehensive strategies for designing high‑concurrency systems, covering page staticization, CDN acceleration, caching layers, asynchronous processing, thread‑pool and MQ integration, sharding, connection pooling, read/write splitting, indexing, batch processing, clustering, load balancing, rate limiting, service degradation, failover, multi‑active deployment, stress testing, and monitoring.
The article outlines the design and evolution of an enterprise‑level unified push notification service, detailing its modular to service‑oriented architecture, multi‑channel support, high‑performance non‑functional requirements, and the comprehensive components such as clients, notification, template, distribution, priority queues, adapters, analytics, and database layers.
This article provides a detailed overview of popular message queue systems, explains their core concepts such as decoupling and eventual consistency, and compares the advantages and disadvantages of Kafka, RocketMQ, RabbitMQ, and other notable MQ solutions for high‑concurrency scenarios.
The article explains the principle of hot‑cold data separation, when it should be applied, how to distinguish hot versus cold data, and three practical implementation approaches—code modification, binlog listening, and scheduled scanning—to improve database performance and maintain consistency.
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.
