This article explains what Kubernetes (K8s) is, its core characteristics of portability, extensibility, and automation, and how it enables cloud‑native, container‑based deployments, resource optimization, seamless service migration, and operational automation across enterprises of all sizes.
This article explores the motivations, challenges, and design principles behind adopting a multi‑cloud active‑active architecture, emphasizing how it enhances stability, reduces costs, and improves efficiency, while detailing practical solutions for networking, compute, containers, service discovery, traffic routing, and data storage in a cloud‑native environment.
This article explains how organizations can evolve from monolithic applications to microservices using service mesh patterns, Kubernetes sidecar proxies, event‑driven designs, and practical migration strategies such as incremental extraction, Lego‑style integration, and full rebuilds, while addressing latency, security, and observability concerns.
This article uses Taobao as a case study to trace the evolution of a high‑performance backend architecture from a single‑machine setup to a cloud‑native, micro‑service ecosystem, highlighting the technical challenges and design principles at each scaling stage.
This article examines the most common Chinese distributed database architectures, comparing integrated SHARDING designs like OceanBase with separated compute‑storage models such as TiDB and SQL‑proxy based systems, highlighting their inherent trade‑offs, performance challenges, and practical considerations for choosing the right solution.
This article explains how to design a well‑structured Java web application by defining clear three‑layer architecture (Controller, Service, DAO), outlining each layer's responsibilities, describing data type conventions such as PO, BO, VO, DTO, Model, and showing how these types map to the layers for maintainable, scalable development.
This article systematically outlines the design, components, data flow, and evolution of Vivo’s server‑side monitoring system, covering data collection, transmission, storage with OpenTSDB, visualization, alerting mechanisms, and comparisons with other monitoring solutions.
This article walks through the step‑by‑step evolution of Taobao’s backend architecture—from a single‑machine deployment to distributed caching, load‑balancing, database sharding, micro‑services, and finally cloud‑native solutions—explaining the technologies introduced at each stage, the performance bottlenecks encountered, and the design principles that guide large‑scale system construction.
VideoX is a versatile front‑end video player built for Taobao’s massive e‑commerce platform, offering multi‑terminal playback, customizable controls, and analytics through a layered architecture that separates core decoding, framework integration, and experience assurance, while supporting modern web technologies and native fallbacks across diverse business scenarios.
Yelp migrated its massive Kafka deployment from EC2 to a Kubernetes‑based PaaSTA platform, introducing a custom Kafka operator and Cruise Control to cut provisioning time, simplify upgrades, improve lifecycle management, and reduce reliance on Puppet, while maintaining high‑throughput data pipelines.
VideoX, a front‑end player built for Alibaba’s massive e‑commerce ecosystem, addresses diverse playback scenarios—from product detail videos to live streams—by offering multi‑format support, customizable controls, multi‑video management, and a layered architecture that separates playback core, business integration, and experience assurance.
This article presents a comprehensive overview of Home's intelligent recommendation system, detailing its business value, challenges of the previous siloed approach, the platform‑based architecture with standardized capabilities, micro‑service components, and the observability stack that together enable scalable, personalized content delivery for millions of users.
This article examines banking regulatory requirements and typical disaster‑recovery architectures, explains system tiering and recovery‑time objectives, and shares the Industrial and Commercial Bank of China's evolution from a two‑site, two‑center model to a cloud‑native, multi‑center disaster‑recovery framework, offering practical design insights.
The article outlines FPGA's strong performance and versatility, presents recent market growth figures and drivers, explains the basic architecture and firmware development process, and highlights key applications in automotive, communications, and computer‑vision systems, emphasizing its expanding role in AI and deep‑learning solutions.
This article explains why microservice architecture is preferred over monolithic applications, outlines a detailed learning roadmap covering core concerns such as Docker, container orchestration, API gateways, load balancing, service discovery, event buses, logging, monitoring, tracing, persistence, caching, and cloud providers, and recommends suitable tools for each component.
This article outlines a comprehensive roadmap for adopting microservice architecture, describing its benefits, core concepts, and essential tools such as Docker, container orchestration, API gateways, load balancing, service discovery, event buses, logging, monitoring, tracing, persistence, caching, and cloud providers.
This article outlines the design and implementation of a minute‑level order‑fulfillment timeliness simulation platform, detailing its background, objectives, challenges, architecture built on Alibaba Cloud DataWorks, core workflow nodes, domain model, ER diagram, JSON task templates, and future extensions for supply‑chain routing.
This article explains the core goals of microservice architecture, outlines essential design principles, and presents a comprehensive catalog of decomposition and design patterns—including Strangler, Bulkhead, Sidecar, API Gateway, Aggregator, Proxy, Chained, Branch, UI composition, database strategies, CQRS, Event‑driven, Saga, observability, logging, metrics, tracing, health checks, external configuration, service discovery, circuit breaker, and blue‑green deployment—providing practical guidance for building resilient, scalable systems.
Architects should treat system capacity like a pre‑flight checklist, using this comprehensive guide to monitor resource usage across services, databases, and queues, and to define business metrics and state‑machine indicators that reveal bottlenecks and guide scaling decisions.
This article provides an in‑depth overview of modern backend architecture, covering microservice fundamentals, design principles, gateway patterns, service registration, configuration management, observability pillars, service mesh options, and a detailed comparison of popular message‑queue technologies.
This article explores the core goals of microservice architecture, outlines key design principles such as scalability and resilience, and presents a comprehensive catalog of decomposition, integration, cross‑cutting concern, and observability patterns—including API gateway, Strangler, Bulkhead, Saga, and CQRS—to guide developers in building robust, maintainable backend systems.
The article analyzes why modern software systems repeatedly collapse—due to growing business complexity, unpredictable changes, and architectural decay—and proposes principles such as decentralization, integration, and diversity, along with practical strategies like service mesh and eBPF, to design more sustainable, observable, and self‑evolving architectures.
This article provides a comprehensive overview of microservice architecture, covering its core goals, design principles, various decomposition and integration patterns, database strategies, observability, resilience, deployment, and operational concerns, offering practical guidance for building scalable, maintainable services.
This article provides a comprehensive overview of common microservice patterns and design principles, covering goals such as cost reduction, faster releases, resilience, visibility, and detailing decomposition, integration, database, CQRS, observability, health‑check, and deployment strategies for building robust backend systems.
This article explains the origins of Domain‑Driven Design, describes strategic concepts such as domain, bounded context and context mapping, explores tactical building blocks like entities, value objects, services, aggregates and factories, and demonstrates practical architecture choices and Java code examples for a payment system.
This comprehensive guide explains how to transform a small e‑commerce monolith into a highly scalable, low‑latency, fault‑tolerant event‑driven microservice system by applying layered architecture, SOA, design patterns, API‑gateway strategies, CQRS, event sourcing, and appropriate cloud‑native technologies.
This article provides a comprehensive overview of microservice architecture, detailing its core objectives, design principles, various decomposition and integration patterns, database strategies, consistency mechanisms, observability techniques, and deployment practices for building resilient, scalable backend systems.
This article explains how to describe current system load, choose appropriate load parameters, analyze Twitter's scaling challenges, compare relational and push‑based timeline designs, clarify latency versus response time, emphasize percentile monitoring, and evaluate vertical versus horizontal scaling and hybrid approaches for handling increasing traffic.
The article explains how to address single‑point failures and capacity limits by clustering servers using replication patterns and introduces the AKF microservice splitting principle, detailing X‑axis horizontal replication, Y‑axis business‑oriented division, and Z‑axis data‑driven partitioning with diagrams.
This article provides a comprehensive overview of microservice architecture, covering its definition, history, differences from monolithic development, key characteristics, comparison with SOA, practical implementation steps, common design patterns, advantages and disadvantages, and essential considerations for successful adoption.
Wolai’s shift to a Serverless architecture using Alibaba Cloud Function Compute cut operational costs by over 50%, accelerated development cycles, and enabled reliable real‑time collaborative editing through a snapshot system, illustrating how small teams can leverage cloud functions for scalable, cost‑effective services.
This article explains Google's shift from MVVM to MVI for Android, detailing how the MVI pattern centralizes UI state in a sealed class, manages user intents with a single data flow, optionally uses a domain layer, and provides Kotlin code examples for implementation.
This article provides a comprehensive overview of Kubernetes, covering its revolutionary role in cloud computing, master‑worker architecture, core concepts such as Pods and Controllers, storage and networking models, workload types, and extensibility through CRI, CNI, and CSI standards.
This article explains why microservice architecture improves flexibility and scalability, outlines a clear learning roadmap, and details essential components such as Docker, orchestration, API gateways, load balancing, service discovery, event buses, logging, monitoring, tracing, data persistence, caching, and cloud providers, helping readers start or migrate to microservices.
To enable Xianyu sellers to create rich product descriptions, the team built a high‑performance, extensible Flutter rich‑text editor using Slate’s protocol, layering protocol, capability extensions, rendering, and business extensions to support custom emojis, themes, ordered paragraphs, and native‑level interactions.
This comprehensive guide explores essential backend development concepts—from system design principles like high cohesion and low coupling, through architecture patterns such as high availability and load balancing, to network communication, fault handling, monitoring, and deployment strategies, providing clear explanations for developers.
This article explains the core concepts of low‑code platforms, why visual editing requires declarative programming, compares declarative and imperative approaches, and details practical front‑end (using JSON‑to‑React via the open‑source AMIS framework) and back‑end storage and logic implementations with code examples.
The article explains the AKF principle for microservice design, detailing how X‑axis horizontal replication, Y‑axis functional splitting, and Z‑axis data‑centric partitioning address single‑point failures, capacity limits, and performance bottlenecks by employing master‑master, master‑slave, and master‑backup replication patterns.
An in‑depth guide compares the four major message‑queue middleware—Kafka, RabbitMQ, RocketMQ and ActiveMQ—detailing their architectures, modes, evaluation criteria, strengths, weaknesses, and selection considerations to help engineers and interviewees answer critical MQ interview questions and make informed technology choices.
This article provides a comprehensive guide for startup founders on selecting languages, components, processes, and tools to design and implement a complete backend technology stack, covering everything from project management and DNS to databases, monitoring, and deployment.
Developer Xiao Wang evaluates three deployment options—traditional SLB + ECS, Kubernetes, and Alibaba Function Compute—to build a highly elastic, low‑cost, low‑maintenance architecture for two online apps, then adopts FC’s reserved‑instance mode and idle‑billing feature to eliminate cold‑starts and reduce expenses.
This article explains how microservice architecture differs from traditional service‑oriented designs, outlines its key characteristics, and shows how Domain‑Driven Design, bounded contexts, aggregates, context mapping, and event‑storming can be used to define clear service boundaries and build resilient, loosely‑coupled systems.
This article compiles core architectural concepts—including ROI, SOLID principles, system splitting, isolation, ACID, CAP/BASE, distributed transactions, and capacity estimation—explaining their definitions, practical examples, trade‑offs, and how they guide architects in making informed technical decisions.
Moyu, Xianyu’s dedicated front‑end R&D framework launched in 2022, unifies template and configuration management, introduces a hybrid XTPL/JS/CSS/Schema development model, and adds a lightweight data gateway that streamlines releases, boosts first‑screen performance, and supports scalable scenarios such as product recommendations, with plans for mini‑programs and broader platform integration.
This article explains the fundamental concepts, design requirements, and modeling approaches for payment account systems in e‑commerce, covering the distinction between payment and login accounts, transaction needs, accounting structures, entity and account models, and the detailed transaction model.
This article provides a detailed technical analysis of the leaked specifications for NVIDIA's Ada Lovelace GPU series, covering chip dimensions, L2 cache innovations, performance expectations, manufacturing node implications, and cost considerations while comparing them to AMD's offerings.
This article examines various approaches to implementing delayed (scheduled) messages in distributed message queue systems, comparing external storage, RocksDB, Redis, and open‑source MQ solutions, and discusses their advantages, drawbacks, and practical considerations.
This article traces Taobao’s architectural evolution—from a single‑machine setup to distributed clusters, caching layers, load‑balancing proxies, database sharding, microservices, ESB, containerization, and finally cloud‑native deployment—highlighting the technologies and design principles that enable scaling from hundreds to tens of millions of concurrent users.
This article outlines the step‑by‑step evolution of a high‑traffic e‑commerce backend—from a single‑machine setup to cloud‑native microservices—illustrating the technologies and design principles needed to scale from hundreds to tens of millions of concurrent users.
This article explores the nature of software complexity, contrasting tactical programming shortcuts with strategic architectural design, explains McCabe cyclomatic complexity and Ousterhout's perception, and offers practical insights and code examples to help engineers manage and reduce complexity in their systems.
Using Taobao as a case study, this article traces the step‑by‑step evolution of a high‑traffic backend—from a single‑machine setup through database sharding, caching, load balancing, microservices, containerization, and finally cloud deployment—highlighting the technologies and design principles that enable scaling to millions of concurrent users.
This article narrates the step‑by‑step evolution of a workflow engine, starting with a basic sequential approver list and progressively adding countersign, parallel, conditional, delegation, timeout, scripting, and nesting capabilities, illustrating a tree‑based architecture and node‑state management for robust backend process automation.
This article explains the concept of architecture, outlines five ways business architecture influences product design, and details modular and progressive approaches for SaaS product architecture, including practical examples, MVP evolution, and strategies for scalable, flexible product development.
This article provides a comprehensive guide on selecting and structuring a backend technology stack for startups, covering language choices, core components, processes, system integration, and practical recommendations for cloud services, databases, RPC frameworks, monitoring, and deployment pipelines.
This article provides a comprehensive overview of servers, covering their definition, logical and hardware architecture, firmware and operating systems, various classification schemes, and a detailed comparison of X86 and ARM server platforms in the context of modern cloud computing.
The article analyzes Alibaba's business middle platform strategy, exposing its inefficiencies caused by deep coupling, high collaboration, cognitive, and stability costs, and proposes practical solutions such as thinning business capabilities, strengthening platform services, decoupling via service-oriented architecture, and adopting Platform-as-Code with componentization.
This article uses Taobao as a case study to trace the step‑by‑step evolution of a high‑traffic backend system—from a single‑machine setup through caching, load balancing, database sharding, microservices, ESB, containerization, and finally cloud‑native deployment—while highlighting the key technologies and design principles at each stage.
This article explains how to design data architecture for microservice systems, covering the advantages of microservices, decoupling principles, lightweight APIs, DevOps integration, database per service versus shared databases, polyglot persistence, and why MongoDB is a suitable choice for scalable, dynamic, and sharded data storage.
The article details Meituan's five‑year journey building a high‑concurrency, AI‑enhanced instant logistics platform, describing its distributed architecture, scalability and reliability practices, fault‑tolerance mechanisms, and future challenges in microservice and unit‑based operations.
This article systematically presents thirty architectural patterns—covering management, monitoring, performance, scalability, data handling, design, messaging, resilience, and security—to help engineers design, implement, and operate robust, high‑performance distributed systems.
This article guides readers through the evolution from a monolithic e‑commerce application to a highly available, scalable, low‑latency event‑driven microservices architecture, covering design patterns, principles, API gateway, BFF, service aggregation, CQRS, event sourcing, and technology stack choices such as Kafka and Cassandra.
This comprehensive guide teaches how to design scalable, highly available microservice architectures by applying design patterns, principles, and best practices, covering the evolution from monolithic to event‑driven systems, communication strategies, data management techniques, and technology choices such as API gateways, BFF, CQRS, and Kafka.
The article presents a modular, extensible content‑delivery pipeline for e‑commerce—comprising datasource, transfer, filter, sorter, completer, validator, factory and iterator nodes—implemented in Java, with JSON‑driven filter schemas, to simplify complex, low‑latency content handling, improve flexibility, and ease operations across evolving business requirements.
This article curates recent front‑end developments, covering emerging frameworks like Pinia, evolving Node.js web standards, low‑code engine open‑source releases, architectural insights, Puppeteer PDF performance tricks, and sandbox security, while also inviting developers to join the Cloud Academy front‑end team.
This article walks through the step‑by‑step evolution of a basic single‑server e‑commerce system into a large‑scale, distributed architecture, explaining core concepts, each architectural upgrade, the technologies involved, and key design principles for building scalable, high‑availability services.
From early monolithic MVC setups to growth‑stage distributed systems and finally fully cloud‑native microservice architectures, this article outlines each phase’s characteristics, technology choices, scaling strategies, and operational practices such as CDN, load balancing, Redis Cluster, Kubernetes auto‑scaling, and unified configuration management.
The article presents actionable methods to speed web development, including adopting a front‑back end separation architecture, leveraging scaffolding tools for data, documentation and mock interfaces, applying disciplined front‑end coding practices, and using computer‑vision‑based techniques to accelerate automated testing.
This article provides a comprehensive technical overview of large‑scale distributed website architecture, covering characteristics, design goals, architectural patterns, performance, high availability, scalability, extensibility, security, agility, evolution stages, capacity estimation, and practical optimization techniques for e‑commerce platforms.
The Alibaba Low‑Code Engine is an extensible front‑end framework that lets developers quickly create customized low‑code platforms, dramatically reducing development time and cost while offering standardized protocols, powerful plug‑in architecture, and an open‑source ecosystem for rapid digital product delivery.
This curated list highlights twelve insightful articles covering Formily's design, React Hooks quirks, ESModule production strategies, Observable-based anti‑corruption layers, REST API POST debates, TypeScript pitfalls, WebAssembly future, spline vs. Bézier curves, Cocos engine rendering, handling complexity with DDD, and React's automatic import changes.
This article explains architectural thinking as a synthesis of system, structured, and programming mindsets, emphasizing the core principles of decomposition and integration, and describes various layered models such as cloud three‑layer, SOA, and classic three‑tier architectures for both technical and application design.
This article outlines the step‑by‑step evolution of Taobao's backend architecture—from a single‑machine setup to distributed clusters, caching, load balancing, database sharding, microservices, containerization, and finally cloud‑native deployment—highlighting the technologies and design principles involved at each stage.
This article details how QQ Music tackled rapid growth in recommendation traffic by redesigning its recommendation architecture, introducing a cloud‑native machine‑learning platform, optimizing data services, and adopting a DAG‑based recall system to improve scalability, flexibility, and development efficiency.
This article explains microservice architecture fundamentals, its advantages, and key design principles for data management, including database selection, polyglot persistence versus multi‑model databases, scaling strategies, and why MongoDB is a suitable choice for microservice‑based systems.
This article provides a detailed introduction to microservices, covering its definition, core principles such as small independent services, lightweight communication, independent deployment and management, the advantages and disadvantages, suitable organizational contexts, and the essential components like service discovery, API gateways, configuration centers, monitoring, circuit breaking, container orchestration, and service mesh.
This article traces Airbnb's architectural journey from a single‑Ruby‑on‑Rails monolith through a microservices era to its current hybrid micro‑macro service model, highlighting the motivations, challenges, and engineering practices that shaped each transition.
The article examines the practical difficulties of integrating services within a microservice architecture—such as circular dependencies, third‑party system coupling, and non‑idempotent APIs—and proposes concrete design principles like one‑way dependencies, minimal redundant data, façade services, idempotency, and contract testing to preserve system health.
This article describes how the Lofter team applied Domain‑Driven Design to refactor and govern complex, multi‑type RecyclerView lists on Android, progressing from a monolithic adapter through a split‑stage implementation to a full DDD‑based framework with reusable bars and context‑aware layout managers.
This article explores layered thinking in architecture design, detailing decomposition and integration, cloud three‑layer models, SOA component‑service‑process layering, and how to combine these approaches into coherent technical and application architectures for balanced business‑technology solutions.
This article provides a detailed overview of the evolution of software architecture from monolithic to microservices, discusses the advantages and drawbacks of each stage, and outlines essential microservice technologies such as service discovery, API gateways, authentication, logging, containerization, orchestration, and CI/CD pipelines.
This document presents Ant Financial's comprehensive coding standards covering concurrency control, idempotency, state management, object handling, SQL practices, time handling, exception safety, code quality, architecture design, middleware usage, data quality, production change procedures, emergency response, and client‑frontend considerations to ensure robust, secure, and maintainable backend systems.
The article outlines how to define security requirements within business context, presents strategic security architecture principles, distinguishes security governance, management and operations, and describes a formalized approach to documenting and integrating security processes for effective enterprise information security.
Gaode Map transformed its navigation and recommendation services by adopting a Serverless, cloud‑native platform that reduces operational costs, enables millisecond‑level scaling, and eliminates the need for on‑site duty during peak holiday periods, while supporting rapid UI and strategy changes.
This article details Alibaba’s front‑end engineer’s approach to building a web‑based short video editor, covering the motivation, design principles, three‑layer architecture, script protocol, immutable data handling, audio‑video processing with WebCodecs and FFmpeg, rendering pipeline, and challenges of browser implementation.
This article explains why front‑end and back‑end separation is needed, describes the evolution from MVC to SPA, outlines responsibilities, development workflow, and provides a detailed version‑1.0.0 API contract with request/response formats, special field rules, and future front‑end trends.
This article details the design, evolution, and optimization of Kuaishou's data synchronization platform, covering business overview, architecture, key technologies, performance tuning, data source protection, incremental data lake integration, and future roadmap for a unified data fabric.
This article examines the intricate data processing challenges of a mobile message client, outlines seven key complexities, proposes a unified abstraction layer to reduce code by 60%, and details a modular solution—including MergeDispatcher, Calculator, and DataStructure—that separates computation from data fetching for improved consistency and scalability.
This article traces the evolution of software architecture from monolithic to microservice models, explains key concepts such as service mesh, distributed tracing, and container orchestration, and lists the essential tools and frameworks—including Docker, Kubernetes, Ocelot, Consul, and Jenkins—required to build and operate modern cloud‑native microservice systems.
This article examines how to design enterprise‑grade data warehouses by evaluating development convenience, ecosystem, decoupling, performance and security, compares Hive and SparkSQL along with other engines such as Presto, Doris and ClickHouse, and outlines best‑practice component selections for long‑running batch and interactive analytics.
This article explains the concept of layered thinking in architecture design, covering decomposition and integration, cloud three‑layer models, SOA component‑service‑process layering, application‑level layering, and how to combine these approaches into coherent, multi‑view architecture diagrams for both technical and functional perspectives.
The article introduces a real-time code coloring system for Lua-based game development, explaining its purpose, usage scenarios, core functionalities, data collection methods, architectural design, technical challenges, performance optimizations, and network communication using Django Channels.
This article details the evolution of an e‑commerce recommendation system through three architectural versions, highlighting the initial simple design, the challenges that prompted vertical and horizontal splits, the introduction of a configurable pipeline and AB testing, and the final micro‑service‑based, dynamically configurable V3.0 architecture.
The panel discusses how microservices have changed over the past ten years, covering evolving definitions, common anti‑patterns, the challenges of distributed transactions, Kubernetes' influence on architecture, organizational impacts, and future trends such as application‑centric models and GitOps.
This article presents thirty concise architectural principles covering simplicity, iterative development, automation, scalability, concurrency, distributed system design, user experience, and practical trade‑offs, offering a comprehensive guide for architects and engineers to build robust, maintainable software.
The article examines synchronous request‑response microservices, outlining their numerous drawbacks such as tight coupling, scalability limits, failure handling, API versioning challenges, data access coupling, distributed monolith risks, and testing difficulties, while also acknowledging their undeniable advantages and the prevalence of hybrid architectures.
This article explains what microservices are, how they differ from traditional monolithic apps, illustrates a real‑world example with an Amazon product page, discusses the role of containers, outlines the benefits and drawbacks of microservice architectures, and shows how Kubernetes facilitates their deployment and management in cloud‑native environments.
This curated list highlights recent technical articles for front‑end engineers, covering Chromium's rendering pipeline, cross‑cloud mini‑program development, clean JavaScript practices, CSS font metrics, React diff optimization, Commander.js, Google Web Vitals, clean architecture, Remix, state‑management comparisons, and CDN disaster recovery solutions.
This article explores layered thinking in system architecture, covering decomposition and integration, cloud three‑tier models, SOA component‑service‑process layers, their fusion, classic and domain‑driven application layers, and practical guidance for constructing clear, multi‑view architecture diagrams.
This article provides a comprehensive overview of MyBatis, detailing its three‑layer architecture, core modules such as caching, reflection, and transaction management, as well as the complete execution process from configuration files to SQL execution, helping developers master the framework for enterprise‑level Java applications.
The article explains layered architecture thinking, covering cloud three‑tier models, SOA layering, classic three‑layer application design, domain‑driven refinements, and practical guidance on constructing clear, maintainable system diagrams without mixing incompatible modeling approaches.
