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 explains the concept of layered architecture thinking, covering decomposition and integration, cloud three‑tier models, SOA layering, application‑level three‑tier patterns, and how to combine cloud and SOA approaches into a coherent, multi‑view architectural blueprint.
The article explains seven widely used software architecture patterns—layered, multi‑layer, pipe‑filter, client‑server, MVC, event‑driven, and microservices—detailing their contexts, problems they solve, typical structures, strengths, weaknesses, and suitable application scenarios.
Many companies attempt microservice transformations only to end up with a “distributed monolith” that looks like microservices but retains monolithic flaws, leading to increased complexity, reduced stability, and minimal performance gains, as this article explains the root causes and how to avoid them.
This article distills essential software design knowledge—covering the five SOLID principles, three common architecture styles, effective diagramming, naming conventions, and techniques for simplifying nested if‑else logic—providing concrete Python examples and visual aids to help developers write more maintainable and robust code.
This article explains why clear application layering matters, outlines Alibaba's recommended layers, proposes an optimized layering approach, details domain model mappings for each layer, and offers practical tips to improve maintainability and team collaboration in backend development.
This article explains the purpose and types of software architecture diagrams, introduces the C4 modeling approach, highlights common pitfalls, and offers a step‑by‑step methodology to create clear, self‑describing diagrams that effectively communicate system structure to the right audience.
This article explains the cloud native paradigm—originating from Matt Stine in 2013—and its core components such as DevOps, continuous delivery, microservices, agile infrastructure, and the Twelve‑Factor App, showing how they enable resilient, scalable applications built directly on cloud services.
Effective API design is crucial for microservice architectures, reducing communication overhead, preventing API decay, and ensuring scalability; this article outlines common pitfalls, core design principles such as simplicity, focus, extensibility, compatibility, thorough testing, and documentation to help developers build robust, maintainable services.
The author reflects on their path from a senior Java developer to a software architect, describing early misconceptions, the pitfalls of over‑focusing on code, the importance of mastering existing components, and how design patterns and maintainability become essential when assembling high‑concurrency, distributed architectures.
The article traces the evolution of software architecture—from monolithic applications through vertical splitting, distributed services, and finally microservices—detailing their advantages, drawbacks, and the essential technology stack such as service discovery, API gateways, authentication, logging, containerization, orchestration, and CI/CD, while providing practical examples and references.
The article shares a senior Alibaba engineer’s reflections on what architecture means, the architect’s role, essential skills, and the challenges faced, offering practical insights for developers aspiring to become effective software architects.
The iQIYI Knowledge Web front‑end team built a developer‑oriented component library that splits UI and business logic into reusable basic and business Vue components, enforces clear input/output contracts, uses on‑demand loading and Storybook documentation, achieving high code reuse, maintainability, and consistent UI across independent projects while tackling bundle size and CI/CD challenges.
This article explains the twenty‑one key non‑functional characteristics of software architecture—such as performance, reliability, scalability, security and maintainability—detailing their definitions, typical metrics, and practical techniques for improvement, while linking each trait to ISO‑25010 and real‑world engineering practices.
This article presents a detailed Java learning roadmap covering fundamentals, core language features, the Spring framework, microservices, databases, DevOps tools, project experiences, and soft skills, guiding beginners to become proficient backend developers.
This article explains the definitions of domain and data models, illustrates why they are often confused, shows real‑world examples of misusing each, and provides practical guidance on separating them to improve system design, scalability, and maintainability.
In this detailed case study, a team describes how they successfully refactored a 30,000‑line advertising engine within a month, covering the system's legacy challenges, preparation steps, execution tactics, testing strategies, and the seven critical takeaways that ensured a smooth, low‑risk rollout.
The article examines the tangled code and maintenance pain points of multi‑store (chain) product management, then proposes separating generic and chain‑specific logic into distinct services—mei‑goods for single‑store functions and mei‑chain for cross‑store rules—using OCP, SRP, and domain‑driven design to achieve decoupling, isolated deployment, clearer responsibilities, and improved system stability and developer productivity.
The article analyzes Alibaba's recent decision to dismantle and thin its mid‑platform, tracing its origins, evaluating its impact on business agility and innovation, and discussing why a leaner architecture suits combination‑style innovation while disruptive breakthroughs require a different approach.
The article explains how the YuanShi platform was created to address front‑end talent shortage by standardising tools, redefining team structures, introducing component‑based cooperation, and outlining the evolution, benefits, challenges, and future directions of this approach within a large B‑end organization.
This article explains the abstract nature of software architecture, why it is essential for any system, the responsibilities of architects, various architecture classifications, typical patterns such as layered, CQRS, hexagonal and onion, and introduces the open‑source COLA architecture with its layered design, extension and specification concepts.
This article compares ancient warfare logistics with modern software delivery, defines DevOps and microservices, presents survey data on DevOps adoption, explains microservice characteristics, outlines suitable scenarios, and discusses the benefits and challenges of adopting a microservice‑based DevOps approach.
This article introduces seven common software architecture patterns—layered, multilayer, pipe‑filter, client‑server, MVC, event‑driven, and microservices—explaining their context, typical problems they address, core solutions, inherent drawbacks, and suitable application scenarios for developers and system designers.
The article explains how monolithic drawbacks—complexity, technical debt, and scaling issues—drive the shift to microservices, then details applying Domain‑Driven Design principles such as bounded contexts, aggregates, and layered architecture to design cohesive, loosely‑coupled services, illustrated with e‑commerce examples and code snippets.
This article explains seven fundamental software architecture patterns—layered, multi‑layer, pipe‑filter, client‑server, MVC, event‑driven, and microservices—detailing their contexts, problems they solve, typical solutions, drawbacks, and ideal use cases for developers seeking robust system designs.
This article introduces the Chain of Responsibility design pattern using a whimsical Qing dynasty south‑tour scenario, walks through class design, UML diagrams, and Java code examples—including abstract officials, a singleton emperor, and a prime minister orchestrating the travel—demonstrating flexible, extensible workflow construction.
The article analyzes how the relentless pursuit of high performance drives both single‑machine and cluster‑level architectural complexity, explaining the evolution from batch processing to multi‑core CPUs, the trade‑offs of processes, threads, SMP/NUMA/MPP, and the challenges of task allocation and decomposition in large‑scale systems.
This article explains common software architecture patterns—including traditional three‑tier, cluster (horizontal scaling), distributed (vertical splitting), and microservice (vertical division) architectures—detailing their components, advantages, drawbacks, and configuration examples such as Tomcat clustering with Nginx load balancing.
This article outlines a comprehensive knowledge framework for software architects, covering nineteen essential areas such as responsibilities, foundational concepts, internet system challenges, distributed caching, messaging, load balancing, performance testing, operating systems, algorithms, networking, database design, JVM internals, flash-sale systems, microservices, domain‑driven design, security, high‑availability, big data, and blockchain.
This article examines common misconceptions about software architecture, explains that its core purpose is to manage system complexity, offers practical guidance for identifying complexity hotspots, and presents a concrete university student‑management system case study to illustrate effective architectural decision‑making.
This article introduces ten widely used software architecture patterns—including layered, client‑server, master‑slave, pipe‑filter, broker, P2P, blackboard, interpreter, and MVC—explaining their structures, typical use cases, advantages, and disadvantages, and provides a comparative table to help developers select the most suitable pattern for enterprise‑level system design.
The article traces the evolution of software development—from early machine code and assembly, through high‑level languages, the first and second software crises, structured and object‑oriented programming, to the rise of software architecture in the 1990s—explaining the historical forces that shaped modern architectural design.
This article demystifies software architecture by defining systems, subsystems, modules, components, and frameworks, illustrating their relationships with real‑world examples and diagrams, and proposing a concise definition of architecture as the top‑level structure of a software system.
This article explains core object‑oriented design principles—including DRY, YAGNI, Rule of Three, GRASP, SOLID and other fundamental guidelines—illustrated with real‑world examples and diagrams to help developers write cleaner, more maintainable code.
This guide shows how to build a lightweight Inversion of Control container in TypeScript and use Reflect‑Metadata decorators to register providers and inject dependencies, demonstrating how constructor‑based injection decouples classes, simplifies testing, and mirrors patterns used in frameworks such as NestJS, Midway, and Angular.
This article explains how classification thinking—organizing software into modules, components, and packages—forms the foundation of application architecture, illustrates the COLA framework’s evolution, and shows how proper layering and domain‑oriented packaging improve maintainability and scalability.
This article explains how to tackle intricate business logic by applying a top‑down structured decomposition, combining it with bottom‑up domain modeling, and using simple composition patterns, illustrated with a product‑on‑sale use case and concrete Java code examples.
This article introduces the Chain of Responsibility design pattern, explains its motivation through a Qing‑dynasty travel scenario, outlines class design and UML, provides complete Java code examples, demonstrates extensibility, and discusses broader applications in modern software systems.
This article explains the concept of software architecture, why it is essential, the responsibilities of architects, various architecture classifications, and introduces practical application architectures such as layered, CQRS, hexagonal, onion, and the open‑source COLA framework, highlighting how separating business logic from technical details improves maintainability and scalability.
This article explains the Strategy (Policy) pattern, detailing its definition, class diagram, typical use cases, advantages and drawbacks, compares it with Factory and State patterns, and provides a practical Java implementation with sample code and analysis of related JDK components.
This article presents a structured approach to mastering microservices, covering the learning pyramid concept, a detailed learning path with resource collection, and an overview of the six essential components—service description, registry, framework, monitoring, tracing, and governance—along with practical tips and visual diagrams.
This article chronicles Ele.me’s evolution from a monolithic All‑in‑One system to a cloud‑ready, service‑oriented architecture, highlighting the cultural, operational, and technical lessons learned across four major phases of rapid growth and scaling.
This article explains seven common software architecture patterns—layered, multi‑layer, pipe‑filter, client‑server, MVC, event‑driven, and microservices—detailing their contexts, problems they solve, typical structures, strengths, weaknesses, and suitable application scenarios to help developers choose the right architecture for their projects.
The article follows architect Da Liu’s frustration over being passed over for promotion, revealing seven practical strategies—from reading diverse code and accurately judging project direction to mastering meeting management and version control—that can help engineers transform technical expertise into career advancement.
This article explains what software architecture is, why it is essential, the responsibilities of architects, various classification types, common patterns such as layered, CQRS, hexagonal and onion architectures, and introduces the open‑source COLA framework with its layered design, extension mechanisms, and specification rules.
This article explains the Decorator design pattern, compares a naïve inheritance approach with a proper decorator implementation in Java, provides complete code examples, class diagram, usage scenarios, advantages, and disadvantages, demonstrating how to dynamically extend object behavior without modifying existing code.
This article explains the essence of software architecture, outlines its various classifications—including business, application, technical, code, and deployment architectures—describes when architecture design is needed, and presents metrics and common pitfalls for evaluating a sound, scalable system.
This comprehensive guide outlines the philosophical mindset, core competencies, technical knowledge, architectural principles, and essential tools that aspiring software architects should master to build robust, scalable, and secure systems in modern IT environments.
This article explains the concept of software architecture, why it is needed, the responsibilities of architects, various architectural classifications and patterns such as layered, CQRS, hexagonal and onion architectures, and introduces the COLA framework with its layered design, extension mechanisms, and specification guidelines.
This article outlines a step‑by‑step career roadmap for developers who aspire to become software architects, covering role definitions, required technical and managerial skills, learning pathways such as OOP, design patterns and refactoring, and practical advice for continuous self‑improvement.
The article outlines the essential competencies—technical mastery, business understanding, design foresight, depth and breadth of knowledge, communication, and systematic thinking—that a software architect must develop to effectively lead and deliver complex projects within an organization.
In this article, Alibaba senior tech expert Zhang Jianfei shares a practical methodology for handling intricate business scenarios—like product listing in the Retail platform—by combining top‑down process decomposition with bottom‑up object‑oriented modeling, avoiding heavyweight workflow tools, and applying ability sinking to keep domain code clean, reusable, and maintainable.
This article presents a practical methodology for writing clean, maintainable code for complex business scenarios, using structured top‑down process decomposition combined with bottom‑up object modeling, illustrated with a retail product‑on‑sale case, code samples, and guidance on tool usage, domain modeling, and capability sinking.
The article explains what a software architect is, outlines their evolving responsibilities across development phases, describes various architect specializations, highlights essential skills and team collaboration practices, and offers career guidance for aspiring architects.
This article explains what software architecture is, why it is essential, the responsibilities of architects, various classification types, typical architectural patterns such as layered, CQRS, hexagonal and onion architectures, and introduces Alibaba's open‑source COLA framework with its layered design, extension and specification concepts.
The article presents a comprehensive set of fifteen universal software architecture principles—ranging from redundancy and rollback to automation and non‑intrusive design—along with essential design guidelines such as separation of concerns, single responsibility, and low coupling to help architects build scalable, reliable, and maintainable systems.
This article explains how to craft an architecture vision by answering core philosophical questions, applying a waterfall design process, distinguishing vision from concrete goals, exploring three hierarchical levels of vision, and linking requirements, quality attributes, and design principles to create a coherent, future‑proof software architecture.
This article explains how to conduct thorough requirement analysis, classify and prioritize needs, and translate them into solid software architecture decisions, highlighting demand capture, functional, quality, and constraint considerations, as well as practical steps for prioritization and implementation.
This article introduces ten widely used software architecture patterns, explains their purposes, advantages, disadvantages, and typical application scenarios, and provides a comparative table to help developers choose the most suitable architecture for large‑scale enterprise systems.
This article explains the 4+1 view model for software architecture, detailing its logical, process, development, and physical views, how scenarios tie them together, and why using multiple concurrent views improves design, documentation, and risk management in large‑scale systems.
This comprehensive article explains the concept of the mid‑platform (Zhongtai), its origins, classification into business, data, algorithm, technical, R&D, and organizational platforms, examines the challenges it solves, and reviews real‑world implementations by Alibaba, Huawei, NetEase, Baidu, and Tencent, concluding with practical guidance for adopting a suitable platform strategy.
This comprehensive guide explains the essence of software architecture, clarifies related concepts such as systems, modules, and frameworks, and details various architectural layers, classifications, evolution paths, and best‑practice considerations for building robust, scalable systems.
This article explains the Dependency Inversion Principle, shows why traditional layered architectures suffer from maintenance and reuse problems, provides concrete Java and web examples, and demonstrates how refactoring to abstract interfaces resolves these issues for more flexible, decoupled software design.
This article explains the Chain of Responsibility design pattern, its definition, roles, Java code examples, real‑world applications such as servlet filters and Spring MVC, advantages, drawbacks, and typical usage scenarios, providing a comprehensive overview for developers.
This comprehensive guide explains what software architecture is, distinguishes systems, subsystems, modules, components, and frameworks, outlines architecture layers and classifications, describes strategic versus tactical design, tracks the evolution from monoliths to micro‑services, and highlights how to evaluate and avoid common architectural pitfalls.
This article explains the fundamental concepts of software architecture, distinguishes systems, subsystems, modules and components, describes various architectural layers such as business, application, data, code, technical and deployment, outlines evolution from monoliths to micro‑services, and highlights common misconceptions and measurement criteria for a sound architecture.
This comprehensive guide walks you through the fundamentals of system design, covering core concepts, analytical thinking, modeling techniques, architecture classification, design tools, and best‑practice principles to help you build robust, scalable software systems.
Microservices aren’t a universal solution; this article outlines five common situations—insufficient complexity, small teams, indivisible applications, legacy system integration, and tight real‑time integration—where adopting a microservice architecture can add unnecessary overhead and risk, advising developers to choose the right architecture for their needs.
This article explains why entities are essential in domain‑driven design, how to define unique identifiers, ensure their stability, model entities in various states, and implement robust constructors with Java code examples and practical guidelines.
This article introduces common frontend design patterns—creational, structural, and behavioral—explains the SOLID principles behind them, and provides clear JavaScript examples for each pattern, helping developers understand when and how to apply them for more maintainable code.
The article outlines twenty‑four key capabilities across continuous delivery, architecture, product and process, lean management, and culture that research shows drive superior software delivery performance and organizational outcomes.
The article introduces eight widely used software architecture design patterns—including single‑database single‑application, content distribution, query separation, microservice, multi‑level cache, sharding, elastic scaling, and multi‑datacenter—explaining their typical structures, suitable scenarios, and the main pros and cons of each.
The article explains what cloud‑native applications are, contrasts them with traditional software, outlines four core cloud‑native development principles, and details a six‑step process—including DevOps culture, lightweight servers, PaaS, framework selection, automation, and modular architecture—to accelerate building and deploying cloud‑native solutions.
This article compares five common software architecture patterns—layered, event‑driven, microkernel‑plugin, microservices, and cache—detailing their structures, advantages, drawbacks, and ideal use cases, helping architects choose the most suitable design for new or existing applications.
This article explains the principles, advantages, and step-by-step process of component-based development, covering business modeling, software requirements, system and technical design, implementation, and integration within modern microservice and SOA architectures.
This article explains six essential software design patterns—Factory, Singleton, Decorator, Strategy, Proxy, and Observer—covering their concepts, structure, advantages, drawbacks, typical use cases, and provides concise Java code examples for each.
This article shares the author's insights on why engineers and leaders must conduct code reviews, identifies common causes of poor code such as duplication and premature decisions, and presents a set of design principles, model‑driven thinking, and concrete Go code examples to help improve software quality and maintainability.
This guide explains why architecture diagrams matter, introduces the C4 modeling method, shows how to use C4PlantUML with PlantUML to create context, container, component, and code‑level diagrams, and provides step‑by‑step instructions and example code for practical implementation.
In this candid talk, a former Alibaba multimedia front‑end engineer shares his career journey—from early patents and B2B animation work to leading live‑streaming projects, detailing the challenges, technical breakthroughs, and personal reflections that helped him overcome professional uncertainty.
This article explains the fundamental concepts of software architecture, including definitions of systems, modules, frameworks, various architectural layers such as business, application, data, code, technical and deployment, and discusses the evolution from monolithic to distributed and microservice architectures along with evaluation criteria and common pitfalls.
This article explains the fundamental concepts of software architecture, distinguishes system, subsystem, module, component, and framework, outlines architectural layers and classifications, describes the evolution from monolithic to distributed and micro‑service architectures, and discusses how to evaluate and avoid common design pitfalls.
This article explains the concept of a business middle platform, distinguishes it from front‑end, back‑end and generic platforms, outlines its classifications, and details Biz‑UI's three‑stage journey of building, designing, and deploying a reusable micro‑service‑based middle platform for rapid business innovation.
This article explains the fundamentals of data modeling for front‑end development, covering its three core elements, integrity constraints, domain‑driven design, layered architecture, and practical guidelines for building clean, maintainable front‑end data models.
The article explains why large distributed applications quickly become complex, identifies cognitive‑load and collaboration‑cost as the two key dimensions of software complexity, analyses concrete causes such as poor logic, mismatched models, bad API design, naming and testing gaps, and offers practical principles for keeping complexity under control.
This article explains the concept of loose coupling in banking IT systems, outlines its definitions, measurement criteria, and practical design guidelines across components, interfaces, data, and processes, while also discussing the trade‑offs and costs associated with adopting a loosely coupled architecture.
This article explores why massive distributed applications quickly become complex, identifies cognitive load and collaboration cost as the two main dimensions of software complexity, and offers practical design, naming, testing, and documentation strategies to keep systems maintainable over time.
This article explains the Strategy pattern with Java, showing how to refactor a naïve pricing module into a flexible, open‑closed design, and then extends the concept to payment processing and thread‑pool rejection handling, complete with code samples and UML diagrams.
This article explains the factory pattern—a creational design pattern in Java—by describing its three main variants (simple factory, factory method, abstract factory), their advantages, typical scenarios, detailed UML diagrams, and complete Java code examples illustrating each implementation.
The article uses a thought experiment of a computer left idle for a year to illustrate how software architecture must evolve from static diagrams to operationalized, continuously delivered microservices, emphasizing the importance of DevOps, feature toggles, and real‑world resilience.
Application security principles are language‑agnostic design and implementation guidelines that help reduce the likelihood and impact of threats, providing a systematic way to make secure decisions, derive requirements, and identify potential defects in software systems.
This article introduces a methodology for creating clear architecture diagrams, explains what architecture and architecture diagrams are, outlines their purposes, presents the 4+1 view classification, discusses common pitfalls, recommends the C4 model, and shares a real‑world case study to help readers communicate system designs without ambiguity.
To refactor a versioned API plagued by nested guards, the article proposes the Responsibility Tree pattern—a hybrid of Chain of Responsibility and Strategy—that routes requests through hierarchical handlers based on parameters, yielding cleaner code, easier debugging, and scalable extension for future versions.
This article explains how to apply the Observer design pattern in a simple Java game to handle button clicks and hero movement, showing UML diagrams, code examples for subjects, observers, and a client that registers and triggers events.
This guide explains monolithic and microservice architectures, compares their advantages and drawbacks, outlines suitable scenarios, and reviews popular Java backend frameworks and versioning strategies to help developers choose the right approach for scalable applications.
This article explains the basic concepts, advantages and disadvantages of four common software architecture patterns—monolithic, distributed, microservices, and serverless—helping developers understand their evolution, trade‑offs, and suitable scenarios for modern application design.
This article explains the four main software architecture styles—monolithic, distributed, microservices, and serverless—detailing their structures, advantages, disadvantages, and typical use cases to help developers select the most suitable architecture for their projects.
This article describes Agricultural Bank's "1+1" development model that combines a comprehensive microservice development platform with an end‑to‑end DevOps workflow, enabling rapid, automated delivery of cloud‑native financial applications and achieving industry‑leading continuous delivery maturity.
The article details how China People's Insurance (PICC) leveraged a distributed micro‑service architecture, AI integration, and a DevOps maturity model to attain a level‑3 continuous delivery rating, illustrating the practical benefits, metrics, challenges, and future plans of their transformation.
This article explains what an architecture diagram is, why it matters, and provides a step‑by‑step methodology—including business and system modeling, abstraction techniques, diagram classification, drawing guidelines, and quality evaluation—to help engineers produce clear, purposeful diagrams that improve communication and collaboration.
This article explains what an architecture diagram is, why it matters, and provides a step‑by‑step methodology—including business and system modeling, abstraction techniques, and quality criteria—to create clear, purposeful diagrams for software projects.
