This article explains how layered thinking and layered models—covering decomposition, integration, cloud three‑layer architecture, SOA layering, and application architecture—provide a systematic approach to designing balanced, cohesive, and loosely‑coupled software systems.
The article outlines Vivo's live streaming platform evolution, detailing its business scenarios, underlying architecture, key technical challenges such as beautification, messaging, latency, and cost, and the concrete solutions implemented across entertainment, interactive, and corporate event live streams.
This article compiles a selection of Qunar's 2021 technical writings covering architecture design, big data processing, front‑end engineering, and cloud‑native practices, providing titles, authors, brief abstracts, and direct links for readers seeking in‑depth engineering insights.
This article examines the step‑by‑step evolution of the recommendation framework used by a major e‑commerce service, detailing the shortcomings of the initial V1.0 design, the vertical and modular refinements introduced in V2.0, and the dynamic configuration, pipeline, and service‑oriented enhancements implemented in V3.0 to improve scalability, stability, and fine‑grained experimentation.
The article explains mid‑platform architecture as an organizational and technical strategy that abstracts reusable components, defines business identities for isolated yet flexible capabilities, and offers three extension patterns—local JAR integration, remote SPI calls, and shared JARs—to balance performance, isolation, and version management while enabling rapid business line onboarding and scalable growth.
The article details how a business‑oriented company built an architecture committee, secured leadership support, defined clear design principles, restructured a monolithic common package into modular base projects, and used concrete case studies and team‑wide promotion to successfully evolve its technical architecture.
This article explains the concept of architecture, distinguishes business and technical architecture, describes digital‑transformation architecture, outlines why architecture is essential for digital initiatives, compares enterprise‑architecture and agile‑development approaches, and provides practical guidance for designing business and technology architectures in a transformation journey.
This article details how Baidu's search middle platform migrated from script‑based processing to a serverless business‑framework architecture, outlining the technical challenges, design of data ingestion, processing, scheduling, and control layers, and summarizing the efficiency, cost, and performance gains achieved.
Serverless architecture, a cloud‑native design that eliminates server management, offers elastic scaling, cost efficiency, and rapid iteration, while also presenting challenges such as vendor lock‑in, operational complexity, and debugging difficulties; this article compares it with traditional setups and outlines essential knowledge and tools for implementation.
This article explains SaaS as a software‑delivery model, outlines its presentation, scheduling, business, and data layers, describes essential components such as security, data isolation, configurability, scalability, zero‑downtime upgrades, and multi‑tenant support, and details maturity levels, storage options, tenant identification, and performance optimizations.
QTalk, Qunar's internal IM tool, was re‑engineered using Flutter to unify Android, iOS, QT, and desktop platforms, addressing code duplication, low development efficiency, and architectural complexity through a new data‑logic‑UI framework, mixed‑stack integration, state‑management choices, and performance optimizations.
This talk explains Alibaba's three‑year journey designing a unified low‑code infrastructure, covering architectural thinking, the engine and UIPaaS implementation, ecosystem plugins, and real‑world platform examples, highlighting how protocol‑first design enables multi‑stack, role‑empowering, cost‑effective development across the enterprise.
This article walks through the step‑by‑step evolution of a basic single‑server MVP architecture into a large‑scale distributed system, using a simulated Taobao example to illustrate ten‑plus architectural stages, key technologies, design principles, and the eventual shift to cloud‑native microservices.
The AiFanFan Communication system was refactored by applying domain‑driven design and micro‑services, replacing an outdated Windows C++ client and excessive middleware with a five‑layer architecture, streamlined protocols, and a cross‑platform Electron‑Vue UI, resulting in clearer modules, higher stability, reduced team size, and faster feature delivery.
This article explains why and how to separate front‑end and back‑end responsibilities, introduces the SPA‑based architecture, outlines development processes, and provides a detailed API specification (including request/response formats, pagination, and special field rules) to improve collaboration and reduce integration effort.
A group of e‑commerce engineers share their real‑world experiences on selecting technologies, designing architectures, handling rapid growth, and avoiding common mistakes when building a new online store from scratch, offering practical guidance on infrastructure, DevOps, and team organization.
This article outlines why microservice architecture is preferred over monolithic designs, presents a clear learning roadmap, and details essential concerns such as Docker, orchestration, API gateways, load balancing, service discovery, logging, monitoring, tracing, persistence, caching, and cloud providers, with recommended tools for each.
This article explains the purpose, evolution, business logic, architectural design, and key design principles of a payment operations platform, detailing its user groups, system architecture, interaction model, permission management, and security considerations for internal staff in payment companies.
This article explains the concepts, use cases, advantages, and limitations of server‑side rendering (SSR) for Vue applications, details the Vue SSR architecture and core packages, and provides practical code examples and ready‑to‑use scaffolds for building SSR projects.
From architecture tweaks like distributed caching and read‑write separation to hardware upgrades, DB instance tuning, and concrete SQL refactoring, this guide walks through four optimization layers, illustrates each with diagrams and a full‑scale MySQL case study, and shows how performance can improve up to twentyfold.
The article compares B2B and B2C business models, highlights differences in demand certainty and service‑quality tolerance, and proposes a four‑layer, cloud‑native technical architecture—including container, middleware, business, and low‑code platform layers—to guide B2B system and vision construction.
The article examines the definition, pain points, and industry approaches to managing ultra‑complex microservice call networks, highlighting ByteDance's layered architecture, traffic identity marking, and practical recommendations for scaling and governing massive service ecosystems.
This article outlines a practical technology stack and architectural choices—including load balancing, CDN, distributed RPC frameworks, message queues, caching, databases, and search—for building a scalable backend that can support tens of thousands of daily active users in a mid‑size internet company.
This article provides a comprehensive overview of HBase, covering its origins, column‑family storage model, key components such as HMaster and HRegionServer, data‑location process, row‑key design strategies, practical use cases, and comparisons with relational and other NoSQL databases.
This article presents ten GraphQL principles—grouped into integrity, agility, and operations—that guide the design, evolution, and safe production deployment of a unified data graph, emphasizing a single schema, collaborative implementation, versioned registries, performance monitoring, and robust access and demand controls.
This article chronicles Taobao's evolution from a simple LAMP stack to a sophisticated cloud-native architecture, detailing the technical decisions, challenges, and best‑practice solutions—including database migration, caching, CDN, and distributed services—that enable high availability, scalability, and performance for large‑scale e‑commerce platforms.
This article traces the evolution of mini programs, explains their dual‑thread model, details the core components such as WAWebview, WAService, the virtual DOM and JSBridge, and shows how wcc and wcsc compile wxml and wxss into executable JavaScript and styles.
This article details the architecture, data flow, module responsibilities, and successive optimizations of Baidu's short‑video push system, covering personalized timing estimation, user‑group management, frequency‑control redesign, and protobuf‑based compression to handle billion‑scale traffic efficiently.
The article chronicles Taobao’s architectural evolution from a LAMP stack to an Oracle‑IBM mainframe setup, then to a Java‑centric distributed system, and finally to a cloud‑native solution on Alibaba Cloud, highlighting key design decisions, scalability challenges, and migration best practices across storage, services, OLTP and OLAP workloads.
This article examines the lingering challenges of microservice architecture—such as service granularity, development complexity, infrastructure management, and cost—while introducing Serverless computing, its definition, key technologies, and the technical and operational advantages that make it a compelling evolution for modern cloud applications.
This article provides a comprehensive technical summary of large‑scale distributed website architecture, covering characteristics, goals, architectural patterns, performance, high‑availability, scalability, extensibility, security, agility, and a detailed evolution roadmap with practical examples and recommendations.
This article provides a comprehensive, practical guide to applying Domain‑Driven Design (DDD) in enterprise Java projects, covering architectural principles, project management steps, design patterns, code generation, testing, deployment, and a detailed loan‑processing example that demonstrates how to model, implement, and evolve a rich domain model using Spring, DI, AOP, and related technologies.
This article explains the functional purpose, layered and cluster designs, distributed architecture, caching strategies, asynchronous checks, storage heterogeneity, payment solutions, and anti‑bot mechanisms of a cloud‑based shopping cart, highlighting stability, high performance, elasticity, and fault‑tolerance.
This article explains how to evolve a large‑scale website architecture through stages such as initial single‑server setups, application‑data separation, caching, server clustering, read‑write separation, CDN/reverse proxy, distributed storage, micro‑services, and automation to achieve high availability, scalability, performance and security.
This article analyzes the evolution of large‑scale website architecture, covering stages from single‑server setups to layered, distributed, and clustered designs, and explains how caching, read‑write separation, CDN, asynchronous messaging, redundancy, automation, and security collectively achieve high performance, availability, scalability, and extensibility.
This article provides a detailed, step‑by‑step guide for startups to design and select a complete backend technology stack, covering language choices, components, processes, systemization, and the practical evaluation of tools such as project management, DNS, load balancing, databases, messaging, CI/CD, monitoring, and deployment.
This article outlines the objectives, call flow, architectural design, and potential challenges of a payment center system that unifies transaction, payment, and finance services, detailing its four main modules, data handling, and integration with third‑party payment channels.
This article traces the evolution of software architecture from early monolithic Web 1.0 applications through SOA and the rise of microservices, explaining how cloud‑native technologies like containers, Kubernetes, and service mesh reshape development, deployment, and traffic management while highlighting associated challenges and best practices.
The article examines the microapp architecture pattern—derived from microservices—to modularize mobile codebases, accelerate build and test cycles, and improve team autonomy, while also discussing its foundations, challenges, trade‑offs, and practical adoption steps.
This article explores how to design a cloud‑native distributed database architecture by examining TiDB’s current structure, proposing a storage‑compute separation that leverages cloud services like S3 and EBS, and discussing implications for cost, scalability, fault‑tolerance, and multi‑tenant deployment.
This article explores how to design a cloud‑native distributed database architecture using TiDB as a case study, discussing cost reduction, storage choices, compute‑storage separation, fault tolerance, scaling strategies, and the trade‑offs of caching and persistent storage in modern cloud environments.
This article provides a comprehensive overview of microservices architecture, covering its definition, comparison with monolithic systems, design principles, communication methods, benefits, drawbacks, governance, and practical considerations such as DevOps, containers, and real‑world case studies.
The article explains what a data lake is, compares various vendor definitions, outlines its four essential components, describes three evolutionary architecture stages from self‑hosted Hadoop to cloud‑native storage‑compute separation, and discusses the benefits and challenges of adopting data lake solutions in modern big‑data platforms.
This article explains why, when, and how to split a monolithic application into microservices, covering the goals of splitting, timing decisions, guiding principles, granularity considerations, functional and non‑functional strategies, merging practices, and associated risks.
This article provides a comprehensive overview of microservices, covering its origin, core architectural principles, key characteristics, advantages and drawbacks, suitable organizational contexts, and essential technical components such as service discovery, gateways, configuration centers, monitoring, circuit breaking, and container orchestration.
This article provides a comprehensive overview of microservices architecture, explaining its definition, core principles such as small independent services, process isolation, lightweight communication, independent deployment and management, while also discussing advantages, drawbacks, suitable organizations, service discovery, gateway, configuration center, monitoring, containerization, orchestration and related tooling.
The article examines why multi‑cloud active‑active (multi‑active) deployments are essential for high availability, outlines common disaster‑recovery patterns such as primary‑backup and active‑active, details the technical workflow of traffic routing, business and storage layers, and discusses the practical advantages and drawbacks of this approach.
This article explains the concept of layered architecture, covering decomposition and integration, cloud three‑layer models, SOA layering, database and service layers, application and domain layers, and provides guidance on constructing clear, multi‑view architecture diagrams for complex systems.
The article provides a comprehensive analysis of China's domestic CPU ecosystem, examining the technical distinctions between architectures and instruction sets, the security implications of relying on foreign designs, and the strategic balance needed between indigenous development and imported technologies to advance the nation's semiconductor industry.
This article explores UCloud’s comprehensive developer‑tool ecosystem, detailing its layered product architecture, open‑source principles, and a code‑generation pipeline that transforms API specifications into SDKs, CLIs, CDKs, and SaaS tools, dramatically reducing development costs and enhancing cloud‑native productivity.
This article compares MySQL and HBase across architecture, storage engine, indexing structures (B+ tree vs LSM tree), data access features, and ecosystem integration, highlighting each system's strengths, limitations, and the scenarios where HBase is a suitable complement to MySQL for large‑scale data workloads.
This article explains why Redis needs high availability, defines common failure scenarios, compares several HA architectures—including single‑instance, master‑slave with one or multiple Sentinel processes, and VIP‑based solutions—and provides step‑by‑step guidance for deploying a robust Redis Sentinel cluster.
This article explores how to transform product requirements into robust technical architectures by outlining strategic principles—appropriateness, simplicity, evolution—and tactical guidelines such as high concurrency, high availability, and business design, while addressing uncertainty, component complexity, and practical implementation with Java‑centric examples.
The article explains the AKF microservice splitting principle, describing how X‑axis horizontal replication, Y‑axis business‑oriented partitioning, and Z‑axis data‑oriented partitioning together address single‑point failures, capacity limits, and performance bottlenecks in clustered backend systems.
This article details the redesign of Snowball's Android network framework using OkHttp and Retrofit, covering motivations, architectural layers, solutions for domain switching, custom annotations, data validation, migration strategy, and the resulting performance and maintainability improvements.
The article reviews the most frequent errors encountered while adopting microservice architecture—excessive customization, uncontrolled complexity, and vague definitions—illustrating each with real‑world experiences, a saga implementation using Redis streams and Go, and practical advice to avoid similar pitfalls.
The article explains how an iOS video‑editing app adopts a Flux‑style, single‑direction data flow by extracting a shared playback controller and encapsulating features as weak‑referenced plugins that register with a central dispatcher, enabling predictable state management and extensible, decoupled UI interactions.
This article examines the concept of idempotency, illustrates typical business scenarios such as order placement and fund transfer, analyzes which layers of a classic system architecture should enforce idempotency, and provides concrete database‑level strategies and code examples to achieve reliable, repeatable operations.
This article examines RocketMQ's routing registration process, identifies its two main shortcomings—delayed failure detection and NameServer inconsistency—and explores how network partitions can cause prolonged data inconsistency, uneven message distribution, and partitioned consumption, while discussing the architectural trade‑offs behind these design choices.
This article explains how to build a highly available Redis service using Redis Sentinel, discusses common failure scenarios, compares several architectural options from a single instance to a three‑node Sentinel setup, and provides practical tips such as using virtual IPs for seamless client access.
This article presents a comprehensive overview of technical middle‑platform architectures, covering core platform diagrams, banking data structures, retail industry models, backend design principles, real‑time data pipelines, enterprise evolution stages, and case studies from Alibaba and NetEase, illustrated with numerous diagrams.
Douyu’s senior streaming engineer Zhou Sha details the company’s self‑developed P2P live‑video solution, covering its background, architecture, core technologies like sub‑streaming, WebRTC, data slicing, SDK design, sharing‑rate optimizations, and future roadmap for broader media applications.
This article explains how Databend, a cloud‑native OLAP data warehouse, addresses modern data‑warehouse challenges by separating storage and compute, providing elastic scaling, multi‑cloud support, and efficient query planning and execution to deliver low‑cost, on‑demand analytics.
This article explains how applying the five SOLID principles, choosing appropriate system architectures, using clear naming, drawing diagrams, and refactoring code—including guard clauses, responsibility‑chain patterns, and composition over inheritance—can dramatically improve Python program design and maintainability.
This article compares MySQL and HBase by examining their architectural designs, storage engines, data access patterns, and ecosystem features, highlighting the strengths and trade‑offs of each system and outlining the scenarios where HBase is a suitable complement to MySQL.
This article shares practical insights on why engineers and leaders must conduct code reviews, identifies common causes of poor code such as duplication and premature decisions, and presents concrete design principles—including simplicity, composition, transparency, and disciplined logging—illustrated with Go code examples to help teams build maintainable, high‑quality backend systems.
This article presents a practical methodology for creating clear, effective software architecture diagrams, explaining fundamental concepts, various view types such as context, container, component, and class diagrams, and offering tips on audience targeting, common pitfalls, and tool recommendations to improve communication among stakeholders.
This article compares the architectures of RabbitMQ and Kafka, explaining their queue models, master‑mirror and partition mechanisms, performance trade‑offs, and provides guidance on choosing between them based on throughput requirements and system design considerations.
The article details how a legacy e‑commerce supply‑chain system plagued by unclear boundaries, inventory inaccuracies, and tangled dependencies was redesigned using domain‑driven design, hexagonal architecture, CQRS, and an EventStore solution, resulting in accurate inventory, easier extensions, and a reusable event‑driven component.
This article provides a comprehensive analysis of CPU architecture evolution, workflow, historical milestones, CISC versus RISC competition, the emergence of RISC‑V, China's domestic processor initiatives, and current market share trends across servers, desktops, and mobile devices.
This article provides an in‑depth overview of microservice concepts, motivations, architectural principles, design patterns, service splitting strategies, essential infrastructure, popular frameworks such as Spring Boot, Spring Cloud, Dubbo, and Service Mesh, and practical recommendations for adopting microservices in real‑world projects.
This article explores how to write maintainable, readable, and scalable CSS by adopting consistent team guidelines, covering major architectures like OOCSS, BEM, SMACSS, ITCSS, and ACSS, as well as commenting, spacing, and core design principles for high‑quality front‑end code.
This article explains microservice fundamentals, their advantages, technical characteristics, and provides a comprehensive guide to data design in microservice architectures, covering decoupling, lightweight APIs, continuous delivery, database per service versus shared databases, polyglot persistence, scaling strategies, and why MongoDB is a suitable choice.
In this interview, Baidu's chief infrastructure architect explains the high‑performance, data‑intensive demands of its core search business, the role of middle‑platform and microservice architectures, the evolution and impact of cloud‑native technologies, and practical advice for SME architects designing modern IT systems.
The article details how refactoring the Haokan Android short‑video client from a single global player to per‑holder multi‑player instances, combined with lifecycle‑lite event handling, pre‑loading, and dedicated thread operations, cut start‑up latency by ~150 ms, reduced frame‑drops dramatically, and boosted overall user experience and business metrics.
The interview with Kuaishou senior architect Zhao Jianbo details the three‑phase evolution of its trillion‑scale big data platform, covering foundational Hadoop services, real‑time and OLAP extensions, deep customizations, Spring Festival Gala challenges, scheduling innovations, Hadoop usage, and the relationship between big data and cloud architectures.
This article provides a comprehensive overview of microservice architecture, tracing its history, explaining its benefits over monolithic and SOA approaches, and detailing common cognitive, time, cost, development, testing, and operational traps along with practical mitigation strategies for successful adoption.
This article explains how software architects can conduct effective software design by building abstract models and textual specifications, using UML diagrams such as class, sequence, component, deployment, use‑case, state, and activity diagrams to communicate functional and non‑functional requirements throughout requirement analysis, conceptual design, and detailed design phases.
This article explains why and when to break a monolithic application into micro‑services, outlines practical splitting strategies, essential design principles, and the risks involved, while providing concrete guidelines for teams, business scale, and technical readiness.
This article explains how software architects can use UML modeling and design documentation to capture both functional and non‑functional requirements, communicate with stakeholders, and guide developers through requirement analysis, high‑level design, and detailed design phases.
This article provides a comprehensive overview of Kubernetes, covering its core features, resource‑estimation examples, evolution of service deployment models, the relationship between cloud and Kubernetes, cloud‑native principles, and a detailed look at its historical background and architectural components.
An in‑depth case study of Alibaba.com’s iOS client reveals how architectural decay—manifested as tangled module dependencies, slow builds, and outdated tooling—drains developer productivity, and outlines data‑driven, layered, and automated strategies—including dependency analysis, modular refactoring, and CI safeguards—to restore a healthy, scalable mobile codebase.
This session explains why Kubernetes monitoring is essential for end-to-end observability, describes the five data sources and layers it covers, and walks through discovering and locating architecture, performance, resource, scheduling, and network issues using topology, anomaly detection, and correlation techniques.
This article examines the key problems message middleware must address—such as publish/subscribe, ordering, filtering, persistence, reliability, latency, and transaction support—and explains how Apache RocketMQ’s architecture and design choices provide high‑performance, high‑throughput solutions to each of these challenges.
This article explains the concepts, differences, and appropriate usage scenarios of various Java objects such as Persistent Object (PO), Domain Object (DO), Data Transfer Object (DTO), Value Object (VO), Business Object (BO), POJO, Data Access Object (DAO), and Transfer Object (TO) to help developers design clean and maintainable backend architectures.
This article explores the evolution and current state of API gateways and load‑balancing techniques in distributed, micro‑service, cloud‑native systems, detailing client‑side versus server‑side balancing, architectural patterns, key features, open‑source solutions, and recent performance optimizations.
The article outlines six fundamental traits of serverless architecture—low barrier-to-entry, hostless, stateless, elasticity, distributed, and event-driven—explains why they matter, discusses the benefits and hidden challenges each introduces, and offers concise recommendations for developers to successfully adopt serverless solutions.
This article explains the core concepts, patterns, and architectural styles of Domain-Driven Design, covering model‑driven design, bounded contexts, layered and hexagonal architectures, building blocks such as entities, value objects, aggregates, repositories, factories, and services, with practical examples and diagrams.
Docker announced a subscription‑based Business edition of Docker Desktop, outlining its enterprise‑focused features, pricing, the continued free Personal tier, and a detailed look at the platform’s architecture, workflow, and the company’s turbulent growth and two perceived “deaths.”
This article examines four major API architectural styles—RPC, SOAP, REST, and GraphQL—detailing their mechanisms, strengths, weaknesses, and typical use cases, and provides guidance on selecting the most suitable style for a given project based on technical and business constraints.
This article outlines the objectives, detailed call process, architectural modules, and potential challenges of a payment center system that unifies order, payment, and finance services while ensuring security, scalability, and data support for downstream applications.
This essay explores why digital product interfaces rarely venture into "weird" territory unlike architecture, fashion, and art, examines the tension between shape and function, and offers practical guidance for designers on when and how to experiment with bold, unconventional UI designs.
This article reviews Redis's latest features and compares various deployment architectures—including single‑replica, dual‑replica, cluster, and read‑write‑separation modes—detailing their reliability, performance characteristics, suitable use cases, and provides a Java Jedis example for configuring a direct‑connect cluster.
This article compares RabbitMQ and Kafka by explaining their architectures, queue consumption and production mechanisms, highlighting RabbitMQ's single‑master limitation and Kafka's partition‑based design for higher throughput, and provides guidance on selecting the appropriate middleware based on performance needs.
This article explains Flink’s three‑layer architecture (APIs & Libraries, Core, Deploy), details its programming interfaces, runtime engine, deployment options, and core concepts such as stateful computation and time semantics, providing a comprehensive guide for building robust stream and batch applications.
This article explains why well‑crafted architecture diagrams are essential for technical communication, outlines common pitfalls, introduces the C4 modeling approach with its five views, and provides practical advice on drawing self‑describing diagrams that match audience needs and code reality.
This article examines the transition from monolithic to microservice architectures, outlining the advantages and costs of microservices, the conditions under which they should be adopted, practical implementation options, risk assessments, service‑splitting strategies, and a concise comparison with SOA.
This article chronicles SegmentFault's evolution from a single‑instance VPS to a cloud‑native platform on KubeSphere, explaining why Kubernetes was chosen, how front‑end/back‑end separation reshaped the system, and the operational lessons learned for cost‑effective, automated deployments.
This article traces RocketMQ's evolution from its early Alibaba projects, explains its core components and communication roles, walks through the startup process, client message flow, remoting layer, broker handling, storage mechanisms, flush strategies, HA synchronization, and finally details the implementation of transactional messages.
This article outlines the new features of Redis 6.0 and 5.0, compares various deployment architectures such as master‑replica, single‑replica, cluster and read‑write split, presents typical usage scenarios, and provides a Java Jedis code sample for connecting to a Redis cluster.
