This article explains the origin and dual‑thread architecture of WeChat Mini Programs, detailing how the view (WebView) layer and the JSCore logic layer operate, communicate via JSBridge, and transform WXML/WXSS into HTML/CSS.
This article analyzes the limitations of classic iOS MVC, explores MVVM's benefits and drawbacks, and proposes a new service‑oriented architecture with a simple DSL to define and compose atomic business functions, aiming for cleaner, more maintainable mobile code.
This article provides a comprehensive overview of microservice concepts, their differences from traditional SOA, the benefits of agility, scalability and independent deployment, and details RongShu Data's architectural choices, technology stack, design principles, DevOps platform, team organization, and practical implementation guidelines.
This article outlines core database architecture principles, compares four common deployment schemes (master‑slave, dual‑master, master‑slave with read/write separation, and hybrid), and presents practical consistency solutions for both primary‑replica and DB‑cache mismatches, followed by personal evolution insights.
The article explores the fundamental concepts of software architecture, illustrating how massive platforms like Weibo handle millions of users through layered design, service decomposition, multi‑level caching, distributed tracing, and capacity planning to achieve high scalability and reliability.
This article explains the signs that indicate a legacy system needs refactoring, describes the challenges of a monolithic architecture with massive tables, outlines goals such as zero business impact and migration to microservices, and details a step‑by‑step migration strategy using data pipelines and careful interface compatibility.
The article examines the evolution of front‑end architecture using Baidu's mobile search result page as a case study, outlining challenges such as massive codebases, coupling, and outdated tech stacks, and presenting a three‑layer solution involving foundation, modularization, and componentization with SSR optimization.
This article traces the evolution of web architecture from tightly coupled JSP‑Servlet models through semi‑separated Ajax/SPAs to fully decoupled front‑back end designs, highlighting how Node.js as a middle layer improves adaptability, performance, and maintainability for multi‑client applications.
This article explains why using GraphQL instead of REST offers significant architectural benefits, covering hexagonal architecture, infrastructure components, the data graph concept, self‑documenting schemas, federation, and how it empowers frontend developers while simplifying versioning and development.
Baidu’s live‑streaming message service evolved from a basic group‑chat model to a scalable multicast architecture that delivers up to a million concurrent users per room with sub‑second latency, using message aggregation, compression, and priority channels to manage QPS, bandwidth, and reliable gift delivery.
This article explores the fundamental principles of system architecture, illustrating how large‑scale services such as Uber and Weibo handle massive traffic through strategic abstraction, modularization, performance optimization, multi‑level caching, distributed tracing, and operational best practices to achieve scalability and reliability.
The article presents a comprehensive cloud computing reference architecture, illustrating private and hybrid cloud designs, discussing platform choices, storage solutions, scalability, elasticity, and key considerations such as availability, manageability, and feasibility for building robust, cost‑effective systems.
This article examines the chronic decay of a complex warehouse inbound/outbound system, analyzes its tangled business logic and chaotic architecture, and presents a domain‑driven design solution with onion architecture, CQRS, and practical implementation steps to achieve clearer boundaries, higher cohesion, and sustainable evolution.
This article humorously explains 23 classic software design patterns—such as Factory Method, Builder, Abstract Factory, Prototype, Singleton, Adapter, Bridge, Composite, Decorator, Facade, Flyweight, Proxy, Chain of Responsibility, Command, Interpreter, Iterator, Mediator, Memento, Observer, State, Strategy, Template Method, and Visitor—using playful dating scenarios to illustrate each pattern’s intent, structure, and trade‑offs.
This article explains how layered thinking and layered models guide architecture design, covering decomposition and integration, cloud three‑tier (IaaS‑PaaS‑SaaS) and SOA layering, the role of service and data layers, and how to combine cloud and SOA concepts into coherent architectural diagrams.
This article provides a comprehensive overview of NVIDIA's GPU architecture evolution—covering Fermi, Kepler, Maxwell, Pascal, Volta, Turing, and Ampere—detailing compute capabilities, SM structures, specialized units such as Tensor Cores, and their impact on AI and high‑performance computing workloads.
This article introduces seven widely used software architecture patterns—layered, multi‑layer, pipe‑filter, client‑server, MVC, event‑driven, and microservices—explaining their context, problems they address, core solutions, drawbacks, and typical application scenarios.
This article explores the fundamental concepts of system architecture, illustrating how large‑scale services like Weibo handle massive traffic through layered design, sharding, caching, service decomposition, monitoring, and operational practices to achieve high performance and reliability.
Xianyu, Alibaba’s C2C platform, transformed its massive legacy system into a cloud‑native, serverless architecture—integrating Flutter, a unified development framework, and a suite of tools like Nexus API and GCLI—to dramatically cut development cycles, lower operational costs, and support a GMV of over 2 trillion yuan.
This article presents multiple real‑world Elasticsearch deployments across Chinese tech giants, detailing how they handle massive query loads, scale clusters, integrate with Kafka and Kibana, and apply the Elastic Stack for search, analytics, and security monitoring.
This article explains why architecture diagrams are essential for developers, outlines the main categories of diagrams, introduces the Zachman framework and its six-by-six matrix, and provides step‑by‑step examples for creating selection, microservice, and technical architecture diagrams.
The article explains that migrating legacy monolithic systems to the cloud is far from a simple lift‑and‑shift, highlighting the pitfalls of inflexible on‑premise infrastructure, the importance of horizontal scaling, stateless application design, micro‑service decomposition, and asynchronous communication to fully leverage cloud elasticity and cost efficiency.
This article explains the overall architecture, data structures, login and messaging flows, common real‑time, reliability and consistency challenges, and high‑availability and high‑concurrency techniques used in a production instant‑messaging service.
An Operations Workbench built on a micro‑frontend architecture unifies fragmented e‑commerce tools into standardized Process Units and SOPs, boosting operational efficiency, reducing technical duplication, and providing data‑driven, consistent experiences for thousands of operators across hundreds of business scenarios.
This comprehensive guide walks through the essential layers of a backend technology stack—languages, components, processes, and systems—offering practical recommendations on project management, DNS, load balancing, databases, monitoring, and deployment to help startups design a robust, cloud‑native backend architecture.
This guide walks through the essential layers of a backend technology stack for startups, covering language choices, core components like DNS, load balancing, CDN, RPC frameworks, databases, messaging, logging, monitoring, configuration, deployment, and operational best‑practice processes.
This article presents a detailed walkthrough of the FunTester testing framework architecture, covering its layered design, core modules for single‑ and multi‑project setups, multi‑protocol support, common request handling, business logic encapsulation, test flow, data construction techniques, and auxiliary tools such as moco API and JsonPath.
During the Chinese New Year break the author used draw.io (now diagrams.net) to create a comprehensive architecture diagram of the FunTester testing framework, outlining its functional and performance layers, supported protocols, utility modules, and multithreaded execution model.
The article traces Taobao’s architectural journey from its early LAMP stack through Oracle‑IBM mainframe solutions to a cloud‑native design on Alibaba Cloud, highlighting the challenges of availability, consistency, performance and scalability, and presenting concrete migration best‑practice patterns such as CDN, distributed caching, service‑oriented decomposition, and database sharding.
The article details Android 10’s fingerprint recognition architecture—four layers from application to driver—and explains the independent startup sequences of the framework and HAL, describing how the system repeatedly binds services, loads vendor modules, and establishes end‑to‑end data flow to the secure element.
This article presents a comprehensive guide to building a robust, fully managed serverless web application on AWS, covering the selection of services, micro‑service design, event‑driven communication, front‑end integration, security, monitoring, and cost‑effective best practices.
Xianyu’s server‑side rendering solution uses a serverless Node.js app on Alibaba Cloud to aggregate backend data and render HTML, routing through Nginx and caching via CDN, which cuts first‑meaningful‑paint time, maintains high stability with low O&M, and seamlessly falls back to client‑side rendering when needed.
This article explains how to design and implement a flexible, accurate data reporting platform using Elasticsearch aggregation, covering architecture, data synchronization, metric definition, SDK integration, and future scaling considerations for enterprise analytics.
This article details the challenges of JD Pay's Android SDK growth, proposes a refactor using Scene, Interactor, and UserCase concepts to decouple business logic, presents architectural redesign, code examples, and quantitative performance improvements after the overhaul.
Drawing on years at Alibaba, the author shares insights on top‑level design, physical and application architecture, the evolving role of architects, and the essential skills—problem discovery, definition, solution, communication, breadth, and continuous learning—required to tackle complex, global system challenges.
From 2020 to 2021, Zhenkunxing built a visual‑editing service, a unified UI component library, standardized development, compilation and deployment pipelines, a front‑end portal, an online‑form system, an OKR tool, and a micro‑frontend BOSS platform, while planning a low‑code platform to boost efficiency and scalability.
This article presents a comprehensive guide on mobile video editing, covering the historical background of montage, fundamental editing concepts, the component structure of a video editing SDK, detailed performance‑optimisation techniques, compatibility handling, and future directions such as AI‑driven and cloud‑assisted workflows.
This article explains the limitations of traditional REST APIs, introduces GraphQL as a flexible alternative, details its core concepts such as schema, types, queries, mutations and subscriptions, and outlines various deployment architectures and implementation considerations for backend development.
The article shares a solution architect’s practical experience with microservice architecture, outlining five key insights, the cultural shift toward product‑centric teams, challenges of transitioning from monoliths, and why microservices, while powerful, must be adopted only after careful business evaluation.
This article explains the evolution and limitations of REST APIs, introduces GraphQL as a more flexible, declarative alternative, details its core concepts such as schema and type system, compares execution models, and outlines various backend integration architectures for adopting GraphQL.
This article explains why message queues are essential for decoupling systems, enabling asynchronous processing and peak‑shaving, outlines their advantages and disadvantages, compares popular MQ products, and provides practical guidance on high availability, reliability, ordering, and architectural design.
This article explains the purpose of message systems, compares various solutions such as RabbitMQ, Redis, ZeroMQ, ActiveMQ, RocketMQ and Kafka, then details Kafka's design goals, core concepts, architecture, replication, retention policies, zero‑copy transfer, batching, and performance optimizations for high‑throughput distributed messaging.
This comprehensive guide explains the evolution, core concepts, advantages, drawbacks, and practical usage scenarios of microservice architecture, then details ten critical design patterns—including database per service, event sourcing, CQRS, Saga, BFF, API gateway, Strangler, circuit breaker, externalized configuration, and consumer‑driven contract testing—providing concrete examples, pros, cons, and technology recommendations.
This article details the design and implementation of iceluna, a low‑code PaaS platform for building middle‑office systems, covering its product background, architecture, core infrastructure, PaaS services, collaboration features, performance measurement, and future outlook.
San CLI UI combines a San‑based client, a Node.js/Express GraphQL server, and lowdb file storage, enabling custom routing, component enhancements, and a versatile plugin system—supporting widgets, configurations, tasks, and custom views—managed through ClientAddonApi and PluginManager with IPC communication.
The article explains microservices as small, single‑purpose services delivered via APIs, describes how they operate and scale with Kubernetes, provides real‑world examples such as Uber, and outlines how APIs enable communication and deployment across cloud‑native architectures.
This article explains the fundamentals of software architecture diagrams, outlines the purpose and classification of different diagram types, describes common pitfalls, and provides a step‑by‑step guide to using the C4 model—including system context, container, component, and class diagrams—plus a real‑world case study.
The JD App checkout team replaced its hybrid H5‑native architecture with a pure native solution, redesigning the client and server interfaces to shorten the payment flow, improve stability and security, and achieve significant performance and cost reductions while maintaining configurability for dynamic content.
The article chronicles Taobao’s architectural evolution from a LAMP stack to Oracle/IBM mainframes and finally to a cloud-native solution on Alibaba Cloud, detailing the challenges, design decisions, and best‑practice migration patterns for storage, services, OLTP, and OLAP workloads.
This article examines four major API architectural styles—RPC, SOAP, REST, and GraphQL—detailing their mechanisms, advantages, disadvantages, and typical use cases, and provides guidance on selecting the most suitable style based on project requirements and constraints.
The article outlines the evolution of microservice architecture, its advantages, four concrete design principles—including AKF splitting, front‑end/back‑end separation, stateless services, and RESTful communication—while also discussing common challenges and practical mitigation strategies.
This article outlines Zhenkun's mobile engineering journey from 2020 to 2021, detailing the shift to componentized architecture, the adoption of Flutter hybrid development, CI automation, and real‑time monitoring to boost development efficiency and product quality.
It presents a curated selection of over twenty technical articles covering CSS performance, React Server Components, visualization algorithms, frontend monitoring, serverless migration, and more, each with brief insights and links for deeper reading.
This article chronicles Taobao’s rapid growth from a simple LAMP stack in 2003 to a sophisticated, cloud‑native architecture, detailing each major redesign, the challenges faced, and the best‑practice migration strategies that enabled high availability, scalability, and performance on Alibaba Cloud.
This article provides a comprehensive overview of database system design, covering its historical evolution, classification of relational and NoSQL databases, key architectural patterns, consistency models, indexing techniques, storage formats, compression methods, and practical considerations for selecting the right database solution.
This article compares RabbitMQ and Apache Kafka by examining their internal designs, messaging models, ordering guarantees, routing, timing, retention, fault‑tolerance, scalability, and consumer complexity, then provides concrete guidance on when to choose each technology for real‑world systems.
This article provides a comprehensive overview of microservice architecture, covering its definition, history, differences from monolithic development, core characteristics, comparison with SOA, practical implementation steps, communication methods, design patterns, advantages, challenges, and recommended reading resources.
The article details WeChat’s three‑in‑one strategy of precise product, agile projects, and robust technical support, explaining how the team achieves massive scalability, high availability, extensible protocols, resilient disaster recovery, and embedded monitoring through practices like small‑system‑big‑scale, gray‑release, and foundational components.
This article recounts the JD.com 11.11 tech salon presentation where architect Shi Weihang explains how the NeuHub gateway was redesigned to handle over two billion TTS service calls, detailing the challenges, scaling techniques, and architectural decisions that enabled such massive traffic.
This article walks through the transformation of a simple online supermarket from a monolithic application to a fully fledged microservice architecture, covering design principles, common pitfalls, monitoring, tracing, logging, service discovery, circuit breaking, testing strategies, and the role of service meshes.
This article outlines a systematic approach to high‑performance, high‑concurrency backend development by examining CPU speed, cache and multithreading, memory hierarchy and paging, I/O optimization techniques, and the architectural patterns that tie these components together.
This article chronicles the evolution of software architecture from monolithic applications to microservices, detailing each stage's advantages and drawbacks, and enumerates the essential technology stack—including service communication, API gateways, authentication, fault handling, tracing, logging, configuration, containers, orchestration, and CI/CD—that enables building scalable, resilient backend systems.
This article provides a comprehensive overview of microservice architecture, covering its definition, historical development, differences from monolithic systems, design patterns, implementation challenges, advantages, disadvantages, and the mindset shift required for successful adoption.
This article examines whether a Service layer in a Spring‑based application truly requires an interface, analyzes common arguments for and against using interfaces, explores project structuring options, and offers practical recommendations based on real‑world development experience.
In this presentation, JD Intelligent Cloud architect Ge Jibin walks through the technical architecture, deployment strategies, performance tuning, and real‑world use cases of the TiDB cloud database, providing a comprehensive slide deck for developers and engineers.
This article explains the fundamentals of distributed architecture, describing its definition, key characteristics such as cohesion and transparency, common applications like distributed file systems, caches, and databases, and outlines the evolutionary stages from single‑server setups to clusters, load balancing, caching, CDN, NoSQL, and service‑oriented designs.
This article explains the evolution from monolithic to microservice architectures, defines microservices, presents popular solutions, and provides a detailed overview of Spring Cloud and its key components for building Java-based distributed systems.
This article walks through the evolution of an online supermarket from a simple monolithic website to a fully split microservice architecture, highlighting the pitfalls of ad‑hoc growth, the need for service abstraction, monitoring, tracing, fault tolerance, testing, and the trade‑offs of frameworks versus service mesh.
This article details the evolution of 58.com’s commercial data warehouse across three phases—1.0, 2.0, and 3.0—covering its scale, four‑layer architecture, migration from legacy Hadoop‑MapReduce pipelines to Flume/Kafka and Flink streaming, code optimizations, monitoring, and productization for real‑time business insights.
This article compares microservices and monolithic architectures across eight operational dimensions—network latency, complexity, reliability, resource usage, scaling precision, throughput, deployment time, and communication—showing where each approach excels and concluding which wins overall.
This article walks through building a simple JavaScript calculator, adds a minimal plugin architecture, discusses its limitations, and then presents a more robust plugin system that separates core functionality from extensions while preserving safety and testability.
This article explains how DiDi built a unified solution platform that standardizes customer‑service responses across multiple channels by integrating business information, service capabilities, dynamic workflows, static knowledge bases, and a matching layer, while detailing the underlying workflow and resource engines and their performance impact.
This article analyzes the evolution of high‑availability deployment—from cold backup to cross‑region multi‑active—explaining the trade‑offs of each solution, the challenges of stateful services, and real‑world architectures used by companies like Alibaba and Eleme.
UiPath’s server platform is organized into three logical layers—Presentation, Web Service, and Persistence—each providing specific components such as REST APIs, web applications, Elasticsearch, and SQL Server, and follows a VCS‑managed deployment workflow that moves projects from development through QA to production.
This article explains how layered thinking guides architecture design, covering cloud three‑tier (IaaS‑PaaS‑SaaS) and SOA three‑tier models, the role of decomposition and integration, and practical layering patterns for technical, application, and functional architectures across various domains.
iQIYI Knowledge implemented a three‑layer componentization architecture—base, functional, and business components—combined with protocol‑based service registration, URL routing, and an automated build pipeline, enabling cross‑platform code reuse, independent testing, and faster integration while reducing coupling and maintenance overhead.
The DeWu Android team transformed a rapidly expanding, tightly‑coupled codebase into a modular, stable, and efficient architecture by introducing componentization, CI/CD pipelines, DevOps practices, and reusable services across three evolutionary stages, ultimately delivering business value through open‑source libraries, streamlined processes, and improved developer productivity.
This article provides a comprehensive overview of federated learning engineering, covering deployment via Docker containers, the design of training and inference frameworks, key services such as communication, training, model management, and registration, and practical considerations for scaling and reliability in production environments.
This article explains Android's Binder inter‑process communication mechanism, compares it with other Linux IPC methods, describes its architecture in both Java and native layers, outlines the security advantages, and details the underlying kernel protocol and command set.
This article introduces the basic concepts of servers, explains their core hardware components and technologies, and surveys the essential software and applications that run on server platforms, providing a comprehensive overview for anyone interested in server fundamentals.
This article recounts the author's three‑year journey building a Python‑based HR SaaS backend, detailing the architectural evolution from an initial Django MVC prototype through service splitting and microservices with Kong and custom RPC, to a domain‑driven design approach, and shares lessons learned and optimizations.
This article examines the defining traits of large‑scale web systems and walks through the step‑by‑step evolution of their architecture—from single‑server LAMP setups to multi‑layer, distributed, and automated designs—highlighting performance, availability, scalability, and security considerations.
This article explains seven common software architecture patterns—layered, multi‑layer, pipe‑filter, client‑server, MVC, event‑driven, and microservices—detailing their context, problems they solve, typical solutions, drawbacks, and ideal usage scenarios for developers.
This article explains how the Tongtian Tower platform adopted Domain‑Driven Design to separate business and technical complexity, improve scalability, and enable rapid response to changing requirements through strategic and tactical design, bounded contexts, hexagonal and clean architectures, and related patterns such as CQRS and microservices.
This article uses Taobao's backend as a case study to illustrate how a system evolves from a single‑machine deployment to a multi‑layer, highly available, cloud‑native architecture capable of handling millions of concurrent users, covering concepts such as distribution, load balancing, caching, database sharding, micro‑services, containerization, and cloud platforms.
This article explains how software architects can perform effective software design by modeling domain problems and system architecture, outlines the essential UML diagram types, and shows how to use them across requirement analysis, conceptual design, and detailed design to communicate and control development costs.
After three years of evolving a Python‑based HR SaaS backend from a simple MVC prototype to a microservices architecture with domain‑driven design, the author shares the architectural stages, challenges faced, and practical optimizations such as uWSGI‑gevent, Redis pooling, Kong API gateway, and custom RPC framework.
This article introduces seven open‑source projects that demonstrate frontend‑backend separation using technologies such as Vue, Angular, React, SpringBoot, and SpringCloud, providing practical examples and resources for developers to deepen their full‑stack development skills.
The article details Beike's intelligent recommendation platform, describing its C‑end and B‑end user scenarios, the challenges of handling numerous recommendation scenes and material types, and how a strategy‑driven, multi‑stage architecture—from rapid V1.0 construction to V4.0 deep‑model integration—has been evolved, optimized for stability, real‑time processing, and future search‑recommendation convergence.
This article provides an in‑depth analysis of Tomcat’s architecture, covering its core components such as connectors, containers, lifecycle management, class‑loader hierarchy, and design patterns like composite, observer, and template method, while offering practical guidance for reading source code and applying these concepts in real projects.
This article examines the fundamentals of monolithic and microservice architectures, outlines the advantages and drawbacks of each, provides criteria for deciding when to adopt microservices, and offers practical guidance on technical, talent, and organizational considerations for a successful migration.
This page lists past Ctrip Tech Salon sessions covering backend architecture, API gateway design, serverless services, front‑end engineering, hot‑fix techniques, Electron usage, and data‑collection SDKs, providing links to detailed technical reviews of each practice.
This article outlines the evolution of project architecture from single‑server MVC to RPC, SOA, and micro‑services, and provides clear explanations of core distributed‑system terms such as clusters, load balancing, caching, and flow control for developers.
By incrementally routing module‑specific requests through Nginx to a new static front‑end while keeping backward‑compatible APIs, the Vivo Mall team transformed a monolithic 2015 platform into a fully separated architecture, achieving over tenfold front‑end release speed, doubled development efficiency, and a solid foundation for multi‑channel expansion.
This guide surveys over a hundred modern frameworks and tools across fourteen critical backend domains—message queues, caching, sharding, data sync, communication, micro‑services, distributed utilities, monitoring, scheduling, entry proxies, storage, CI/CD, debugging, and local utilities—offering concise recommendations and practical insights for architects and engineers.
This article provides a comprehensive guide to building private cloud infrastructures, covering core principles of stability, scalability and redundancy, storage options, network design, compute resource planning, operating‑system choices, security mechanisms, cloud‑ification techniques, and practical OpenStack deployment examples.
This article outlines the step‑by‑step evolution of a high‑traffic e‑commerce backend—from a single‑machine setup through caching, load balancing, database sharding, microservices, containerization, and finally cloud deployment—while summarizing the key technologies and design principles at each stage.
This article explains the origins, principles, advantages, disadvantages, adoption criteria, architectural stages, required infrastructure, design patterns, service splitting methods, and popular frameworks for building cloud‑native microservices, helping engineers decide when and how to transition from monoliths to microservice‑based systems.
Meituan Waimai’s mobile architecture progressed from early componentization through platformization and a custom React‑Native hybrid to a containerized system that unifies Android and iOS via SDKs, MRN and Titans containers, enabling dynamic updates, modular development, and massive traffic handling while demanding enhanced monitoring and release governance.
Qualitis is a big‑data‑platform‑based data‑quality‑management service that defines, detects, and reports data‑set quality issues, featuring idempotent backend services, load‑balanced high‑availability, Zookeeper‑coordinated process synchronization, thread‑pool throttling, and clearly separated internal and external APIs.
