This article explains the evolution of software architecture—from monolithic to distributed, microservice, and serverless designs—highlighting each model's advantages, drawbacks, and suitable scenarios to help developers make informed technology and career decisions.
This article introduces the open‑source system‑design‑101 repository, explaining why learning system design matters, and walks through essential topics such as API performance, the CAP theorem, caching strategies, microservice best practices, and secure password storage, with links to video courses and the project’s GitHub address.
This article outlines nine practical microservices best practices—from applying the Single Responsibility Principle and forming cross‑functional teams to using proper DevSecOps tools, asynchronous communication, independent data stores, and robust monitoring—to help developers design scalable, maintainable, and secure backend architectures.
This article explores how to build a robust engineering architecture by prioritizing product value, defining clear layered and DDD structures, selecting appropriate technologies, and establishing standards for exception, logging, monitoring, and team collaboration to achieve scalability, maintainability, reliability, security, and high performance.
The article explains the evolution of software architecture by describing monolithic, distributed, microservice, and serverless models, outlining their structures, advantages, disadvantages, and practical considerations for developers and teams.
The article examines recent large‑scale service outages to illustrate how system complexity can be analyzed through four dimensions—component, structural, functional, and descriptive complexity—highlighting the need for comprehensive assessment to improve resilience and sustainable development.
This article explains the Bridge design pattern, a structural pattern that separates abstraction from implementation to avoid class explosion, provides detailed Java code examples, UML diagrams, advantages, disadvantages, and typical scenarios for applying the pattern in software development.
This article provides a comprehensive overview of the five creational design patterns—Singleton, Abstract Factory, Factory Method, Builder, and Prototype—explaining their concepts, UML structures, implementation details, typical use cases, advantages, disadvantages, and includes Java code examples and diagrams.
This article explains the concept of system architecture, outlines the TOGAF layers, describes various types of architecture diagrams such as the 4+1 view and C4 model, and provides practical guidance on creating clear, audience‑focused diagrams for effective communication.
This article explains the Factory Method design pattern, covering its definition, UML diagram, key participants, the problems it solves compared to the Simple Factory, step‑by‑step Java implementation with code examples, advantages, disadvantages, application scenarios, and differences from the Simple Factory pattern.
This article provides an extensive overview of software architecture, covering its definition, history, core concepts, design principles, complexity sources, design process, performance, high availability, scalability, and practical implementation techniques for large‑scale web systems.
This article extends the ideas from "13 Years of Coding at Tencent" by presenting a comprehensive set of engineering self‑cultivation principles—including bias, entropy control, test‑driven design, early and automated testing, unified terminology, domain‑driven design, framework decoupling, and disciplined code encapsulation—to help developers write higher‑quality, maintainable code.
This article shares a developer’s three‑year journey on Alibaba Cloud’s platform, exploring the nature of technical debt, categorizing its causes, and illustrating how micro‑refactorings and configuration‑driven upgrades can steadily improve code quality, accelerate feature delivery, and align engineering with business goals.
This article provides a comprehensive overview of design patterns by first explaining the seven core design principles—Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion, and others—detailing their definitions, benefits, UML diagrams, practical examples, and offering a downloadable PDF for deeper study.
This article explains why hard‑coded if‑else logic hinders extensibility, introduces the Strategy pattern, shows its structure and Java implementation for data synchronization, then enhances the design with a Factory to decouple object creation, concluding with best‑practice recommendations.
This article explains the fundamental concepts of software architecture, the purpose and classification of architecture diagrams, criteria for good diagrams, and introduces the C4 modeling approach with practical examples to help engineers create clear, self‑describing visualizations for various audiences.
This article explains the Proxy design pattern, illustrates its core participants with clear Chinese idiom analogies, and provides a complete static‑proxy implementation in Java—including interface, real subject, proxy class, and client code—while also noting the distinction between static and dynamic proxies.
The Chain of Responsibility pattern links a series of handler objects so that a request can be passed along until one processes it, decoupling sender and receiver, supporting dynamic composition, runtime flexibility, and the Open/Closed principle, as illustrated by a Java leave‑approval workflow.
This article lists and briefly explains fifteen common Python design patterns, including Singleton, Factory, Abstract Factory, Builder, Prototype, Adapter, Decorator, Proxy, Observer, Strategy, Template Method, Iterator, Chain of Responsibility, Command, and State, helping developers understand their purposes and usage.
This article examines the challenges of customizing B2B software, critiques branch‑based development, and proposes a plugin architecture with extensible interfaces, hot‑plug support, tenant isolation, and Spring integration, providing Java code examples and implementation guidelines.
This article explains why software architecture matters, defines the essence of Clean Architecture, compares it with Hexagonal and DDD layered models, and walks through a practical, step‑by‑step process—from business analysis and domain modeling to layer implementation and code examples—showing how to reduce complexity and maintenance cost.
Bilibili’s ONE SDK/API unifies 22 fragmented game SDK variants across brands, regions, and devices into a single, adapter‑based package with centralized parameter management and automated multi‑channel builds, slashing global integration time from 60 to 15 days, cutting parameter awareness by 90 % and duplicate development effort by at least 75 %.
This article explains the Command design pattern, describes its key participants and advantages, and provides five Python examples demonstrating command encapsulation, undo/redo functionality, file operations, shopping‑cart management, and menu handling to illustrate how the pattern decouples request senders from receivers.
This article analyzes the MyBatis source code, illustrating how it applies a variety of design patterns—including Factory, Singleton, Builder, Adapter, Proxy, Composite, Decorator, Template, Strategy, and Iterator—to solve complex architectural challenges and improve modularity, extensibility, and maintainability.
This article introduces ten classic software design patterns—Singleton, Factory, Observer, Strategy, Adapter, Builder, Prototype, Decorator, Template Method, and Facade—explaining their purpose, structure, and providing complete Python code examples that demonstrate how to implement and apply each pattern in real projects.
This article provides direct links to a comprehensive DDD lecture series covering domain primitives, architectural fundamentals, the repository pattern, and best practices for designing a robust domain‑driven design in their projects, offering developers practical examples and essential guidance for implementing effective domain‑driven design.
This article explains the purpose and definition of system architecture, outlines the differences between business, application, technical, and data architectures, and introduces the 4+1 and C4 diagram models with practical guidance on creating clear, audience‑focused architectural drawings.
This article explains the purpose and classification of system architecture diagrams, introduces the 4+1 and C4 view models, and provides practical guidance on drawing effective, audience‑focused diagrams that are self‑descriptive, consistent, and aligned with code.
This article presents a comprehensive set of software engineering principles—including obsessive code detail, entropy control, test‑driven design, domain‑driven modeling, and disciplined coding habits—to improve code quality, maintainability, and team collaboration across development projects.
The article expands on prior reflections by urging engineers to adopt a paranoid, entropy‑controlling mindset, design for testability, apply domain‑driven design, keep frameworks peripheral, enforce purposeful encapsulation and explicitness, and treat code as a craft, inviting community discussion.
This article analyzes how carefully crafted prompts influence the architecture of complex AIGC applications, comparing tools like GitHub Copilot, JetBrains AI Assistant, and Bloop, and presents practical strategies and design patterns for building robust, context‑aware AI‑driven development environments.
This article comprehensively discusses the essential aspects of constructing a system engineering architecture, emphasizing value‑first decision making, layered and DDD architectural patterns, technology selection criteria, exception handling, logging, monitoring, and the importance of establishing shared consensus among teams.
Rich (or active) models embed behavior and aggregation relationships directly within DDD entities, contrasting with anemic models; this approach clarifies business logic, reduces glue code, and improves readability, though it can cause entity bloat, prompting strategies like external service classes, utility helpers, and careful injection handling.
This article explains the Strategy design pattern, demonstrates its implementation in JavaScript through three code versions, discusses the drawbacks of naïve if‑else approaches, and outlines the pattern's advantages and disadvantages for creating flexible, maintainable code.
This article explains the Observer behavioral design pattern, describes its participants, illustrates a real‑world e‑commerce scenario, and provides complete Java code for the observer interface, subject interface, concrete subject, concrete observers, and a test client, concluding with the pattern’s benefits.
The article broadens software architecture beyond structural design to encompass people, processes, and business value, urging architects to balance realistic, flexible goals, limited resources, commercial‑focused behaviors, and industry trends so they can deliver cost‑effective, scalable solutions that align technology with organizational objectives.
This article explains the Chain of Responsibility design pattern, its roles, and how to implement it in Java using a leave‑approval scenario to achieve decoupled, flexible, and easily extensible request handling across multiple handlers.
The author reflects on how studying several programming languages—Java, Go, and Python—mirrors learning foreign tongues, revealing that cross‑language comparison sharpens understanding of data structures, HTTP fundamentals, and framework implementations, ultimately deepening overall software development expertise.
This article explains the traditional strict and loose layered architectures, highlights their coupling issues, introduces the Dependency Inversion Principle as a solution, and shows how applying it leads to hexagonal and clean architecture designs with illustrative diagrams and code examples.
This article details ZEEK Automotive's transition to a cloud‑native architecture, describing how the company adopted Kubernetes, containerization, micro‑service unification, and full‑link gray release to improve system stability, scalability, and development efficiency across its APP ecosystem.
This article explains the importance of architecture visualization for clear communication, compares wireframe, UML, and sketch approaches, and details how the C4 model’s layered abstractions—system, container, component, and code—provide a low‑cognitive‑load, consistent way to document software systems.
This article explains the seven SOLID principles of Java software design—Single Responsibility, Open‑Closed, Liskov Substitution, Interface Segregation, Dependency Inversion, Law of Demeter, and Composite Reuse—illustrating each with clear Java code examples that demonstrate how to write more maintainable, extensible, and flexible object‑oriented code.
This article explains the Strategy design pattern, its definition, structure, and how to refactor a typical e‑commerce discount calculation in Java using interfaces, concrete strategy classes, and a context, highlighting benefits, drawbacks, and best‑practice considerations.
This article explains how a massive Python project with nearly 30,000 files uses a layered architecture and Import Linter to enforce dependency rules, reduce complexity, track technical debt, and improve maintainability, while also discussing the trade‑offs and practical implementation details.
This article explains the purpose and definition of software architecture, categorizes different architecture diagrams, introduces the 4+1 and C4 view models, and provides practical guidance on drawing clear, audience‑focused architecture diagrams that align with code and system design.
This article explains the Chain of Responsibility design pattern, shows its typical use cases, demonstrates how naïve implementations can lead to tangled, hard‑to‑maintain code, and provides step‑by‑step refactorings—including abstract handlers, linked chains, and a factory‑based configuration—to produce clean, extensible Java solutions.
This comprehensive guide explains software methods—including business modeling, requirement analysis, domain modeling, UML relationships, and design principles—illustrating how systematic modeling improves product quality, reduces costs, and enhances engineers' professional growth.
The author revisits two concise yet powerful books—‘Microservice Design’ and ‘Systems Thinking’—explaining how the former guides architects through microservice boundaries, deployment, and scaling, while the latter offers a systematic mindset for designing and governing complex software systems, making both indispensable for modern architects.
This article explains why code architecture matters, compares Clean, Hexagonal, Onion and COLA patterns, describes their layered structures and separation‑of‑concerns principles, and provides a practical Go project layout with concrete code examples to illustrate how each layer interacts.
The article likens blind adoption of Domain‑Driven Design to Forrest Gump’s run, explains how tangled business logic and over‑abstracted layers increase maintenance, shows DDD’s role in clarifying domains and mapping SOLID principles, offers practical tips for splitting responsibilities and building reusable capabilities, and concludes DDD is a valuable—not magical—lens for sustainable, extensible software.
Systems Theory, originating in the 1940s, provides a holistic framework for understanding and designing complex software architectures, emphasizing component interaction, feedback, and adaptability, with practical examples ranging from microservices and Kubernetes to chaos engineering, illustrating its impact on scalability, resilience, and modular design.
This article walks through the historical evolution of backend architecture—from early N‑layered designs, through DDD, Hexagonal, Onion, and finally Clean Architecture—explaining why each style emerged, how they differ, and what practical rules developers can follow to manage complexity and dependencies.
The article systematically defines software architecture, distinguishes systems, subsystems, modules, and components, compares frameworks with architectures, explores TOGAF and RUP classifications, traces the evolution from monoliths to micro‑services, and presents concrete design principles and common pitfalls for building scalable, maintainable systems.
A Tencent architect explains that effective software architecture requires clear distinctions between systems, subsystems, modules and components, understanding frameworks versus structural design, applying TOGAF classifications, evolving from monoliths to microservices, and following fifteen practical principles while avoiding common misconceptions such as over‑design and technology‑driven choices.
This article explores engineering architecture design, emphasizing value‑first decision making, layered and DDD architectures, technology selection criteria, and best practices for consensus, exception, logging, and monitoring to build scalable, maintainable, and secure software systems.
This article explains the three major categories of design patterns—creational, structural, and behavioral—provides concise definitions, typical use‑cases, and clear Java code samples for each pattern so developers can write more maintainable and efficient software.
This article explains how integrating large language models into industrial configuration tools creates AI‑driven features such as knowledge Q&A, automatic application generation, smart drawing, script and material generation, and outlines the three‑layer architecture, prompt engineering, and implementation lessons for developers.
This article explains how Gaode's Information Business team tackled fragmented portal implementations across multiple industries by adopting the Gaode Business Framework (GBF) and domain‑driven design, achieving unified architecture, reduced duplication, improved reusability, and enhanced system stability and maintainability.
This article details how a rapidly expanding B2B fresh‑food company restructured its R&D organization, adopted a matrix management model, and built a comprehensive distributed infrastructure—including task scheduling, service discovery, messaging, logging, file storage, CDN, configuration, sharding, search, caching, and monitoring—to support nationwide warehouse operations and future growth.
This article provides a systematic, example‑driven guide to all 23 classic design patterns—covering creational, structural, and behavioral types—explaining their intent, real‑world analogies, benefits, and offering clear diagrams and runnable code snippets to illustrate each pattern in practice.
The article shares the author’s years of architecture experience at Alipay, arguing that growth into a true architect is a cognitive upgrade, explains what architectural ability really means, illustrates it with a multithreading interview example, and presents systematic thinking methods and practical steps for building architectural competence.
The article examines how applying the open‑closed principle and domain‑driven design in software architecture can lower programmers' cognitive load, streamline development, and enable cost‑effective, scalable evolution of complex systems, especially in fast‑iteration internet services.
This article outlines the definition, motivations, impact levels, planning, communication, layered design, gray‑release techniques, quality improvement measures, and observability considerations for large‑scale backend refactoring in microservice architectures, drawing on practical experience from Ctrip's end‑to‑end refactoring project.
This article explains the Object Factory design pattern, its benefits such as decoupling, extensibility, and centralized instance management, and demonstrates five practical Python examples covering basic product creation, configuration‑driven factories, logger factories, singleton factories, and object caching factories.
This article explains how to apply Domain‑Driven Design (DDD) to a new project, covering key terminology, architectural evolution, bounded contexts, the four DDD boundaries, and various layered architectures such as clean, hexagonal, and onion models.
This article explains the concepts, advantages, disadvantages, and real-world use cases of four essential design patterns—Chain of Responsibility, Template Method, Publish‑Subscribe, and Strategy—providing detailed Java and Spring code examples to help developers apply them effectively.
This article explains how to apply Domain-Driven Design (DDD) from project inception, covering key terminology, architectural evolution, bounded contexts, the four DDD boundaries, and various layered architectures such as clean, hexagonal, and onion models to achieve modular, maintainable systems.
This comprehensive guide clarifies the concept of software architecture, explores related notions such as systems, subsystems, modules, components, frameworks, and various architectural classifications, and outlines design goals, evolution paths, common pitfalls, and recommended reading for building effective, scalable, and maintainable systems.
The article examines the rapid rise of GPT models, their technical capabilities and limitations, and how their integration is reshaping software interaction from command‑line to GUI‑plus‑Language UI, offering frontend engineers new opportunities, practical examples, and guidance on leveraging large‑model AI in product design.
This article explains what architect‑to‑PM transformation means, outlines its characteristic signs and harmful impacts on projects, organizations, and individuals, and offers practical organizational, personal, and cultural measures—including automation pipelines—to keep architects focused on real technical work.
This article analyses the relationship between design patterns, architectural patterns and programming paradigms, explains core concepts and principles, provides extensive examples in Java and Python, presents common pattern catalogs, and offers practical implementation guidelines and case studies for software developers.
The article explains what constitutes a complex system, defines software architecture, outlines its essential elements, categorizes various architecture types, discusses key factors such as functional and non‑functional requirements, and presents design principles and typical solutions for building robust, scalable systems.
This article explains what complex systems and software architecture are, outlines various architectural categories, discusses essential functional and non‑functional requirements, and presents design principles and typical solutions such as domain‑driven design, microservices, cloud‑native, DevOps, and big‑data architectures for building stable, scalable, and maintainable systems.
The article explores how an architect’s cognitive upgrade—through systematic thinking, model-driven analysis, and practical design methods—drives effective system architecture, business modeling, and trade‑off decisions, illustrated by a multithreading interview example and a suite of methodological tools.
This article outlines four foundational design principles—user‑intent‑driven design, context awareness, atomic capability mapping, and language‑API integration—for building LLM‑centric software architectures, illustrating each with DSL examples, Kotlin implementations, and practical insights on prompt engineering, dynamic context layering, and API evolution.
This article explains what complex systems are, defines software architecture, explores its essence and classifications, outlines key architectural factors, and presents design principles and typical solutions such as domain‑driven design, microservices, cloud‑native, and big‑data architectures.
The article explains what a software architect does, outlines four developmental stages—from entry to team collaboration—emphasizes continuous learning, and promotes the 2023 GIAC Global Internet Architecture Conference covering topics like AIGC, cloud native, and digital transformation.
The article explains why clear application layering—covering controller, service, manager, and DAO levels—is essential for maintainable backend code, reviews Alibaba's recommended layer structure, proposes an optimized layering model, and discusses domain model conversions to avoid excessive object transformations.
The article reviews Scott's presentation on Lexical, the next‑generation Elixir language server, explaining the Language Server Protocol, Lexical's dual‑node architecture, modular design for easy contribution, and upcoming development plans, while inviting the community to explore the video replay and contribute.
This article describes how Qunar's technology center defined, measured, and managed system complexity through a custom modeling framework, implemented a dashboard for continuous monitoring, and established an anti‑corruption governance process that limits complexity growth to maintain low maintenance costs across hundreds of applications and systems.
This article explains why design documents need readability, outlines the three essential writing elements—clarity, conciseness, elegance—presents four key design principles such as trade‑offs, the importance of “why” over “how”, time considerations, and avoiding over‑design, and concludes with a brief promotion for a continuous deployment course.
The article explains Java’s Chain of Responsibility pattern, describing how abstract and concrete handler classes form a linked chain that passes a request until one processes it, outlines the steps to implement and assemble the chain, and discusses its benefits, drawbacks, and typical applications such as approval workflows and filter pipelines.
This article describes the challenges of migrating a long‑running monolithic database to a sharded architecture, presents a two‑stage smooth migration strategy using double‑write, diff verification, and mapping‑key techniques, and details the componentized design, core implementation, and configuration of a reusable sharding framework built on MyBatis and Spring.
This article explains the Chain of Responsibility design pattern, shows why naïve nested if‑statements are problematic, demonstrates a step‑by‑step refactor using linked handlers, introduces an abstract handler hierarchy, and finally presents a factory‑based dynamic configuration for scalable request processing in Java.
This article chronicles Nubank’s architectural evolution—detailing how strategic technology choices, cloud‑native platforms, micro‑service design, and data‑engineering practices were leveraged across startup, growth, consolidation, and expansion phases to achieve massive scalability and business agility.
The article defines software architecture as a business‑driven abstraction of system structure, explains core design principles such as SOLID, Ockham’s Razor, DRY, YAGNI, KISS and POLA, illustrates LSP violations, surveys layered, hexagonal, onion and DDD styles, and shows how applying Dependency Inversion in a large C++ codebase yields a simple, maintainable, business‑aligned architecture.
This article describes JD Supply Chain's self‑developed low‑code rule engine platform, outlining its motivation, high‑concurrency performance challenges, value‑centric design, visual rule‑authoring workflow, SDK integration, and the resulting efficiency gains for both development and business teams.
This article explains the concept of software architecture, distinguishes it from frameworks, outlines its components, design objectives, classification methods such as RUP 4+1 and TOGAF, evolution from monoliths to micro‑services, evaluation criteria, typical misconceptions, and recommends essential reading for architects.
This article explains why architecture design, especially Domain‑Driven Design, is essential for controlling the complexity, cost, and scalability of microservice systems, detailing common misconceptions, sources of complexity, and concrete steps to define clear domain and service boundaries.
This article explains what a complex system is, defines software architecture, explores its essence and classifications, and outlines the key factors, analysis methods, design principles, and typical solution patterns such as DDD, micro‑services, cloud‑native, DevOps, and big‑data architectures.
This article explains why design patterns, while useful for improving code quality and reusability, can lead to over‑design, describes common forms of over‑design, and offers practical guidelines to avoid excessive abstraction in software projects.
The article examines Google’s single‑repository (monorepo) strategy, detailing its technical benefits such as unified version control, code sharing, and atomic changes, while also analyzing the substantial tooling, infrastructure, and maintenance costs, and discussing why alternatives like Git are not adopted.
The article explains that building evolvable software systems—using strategies like microservices and event‑driven architecture—allows teams to adapt to changing workloads and business growth, illustrated with real‑world examples from Amazon, Prime Video, and S3, while emphasizing that no single architectural pattern fits all scenarios.
This article revisits Inversion of Control and SOLID design principles within the JavaScript ecosystem, explains their practical application using InversifyJS, demonstrates a full‑stack example in the Theia IDE framework, and discusses the benefits, challenges, and best‑practice considerations of adopting IOC in modern web projects.
This article explains the concept of enterprise architecture by likening an organization to a massive software system, discusses its importance in digital transformation, outlines its meta‑model and view layers, and highlights why a structured architectural approach is essential for modern enterprises.
This article explores the relationship between design patterns and programming languages, explains various programming paradigms, compares design patterns with architectural patterns, outlines key design principles, and provides extensive Java code examples illustrating factory, strategy, template method, builder, proxy, chain of responsibility, and command patterns in practice.
The article defines pipeline domain design concepts, compares major multimedia frameworks such as FFmpeg, GStreamer, MediaPipe and AVPipeline, and demonstrates a configurable, extensible node‑based architecture that enables fast plugin integration and adaptable audio‑video pipelines across diverse business scenarios and platforms.
The article explains the emerging concept of sustainable or continuous software architecture, outlines six guiding principles, compares it with traditional methods, and describes how it integrates with agile, DevOps, and product‑centric thinking to deliver resilient, adaptable systems over the long term.
The article presents a component‑based integration framework that abstracts partner‑specific data mapping, signature creation, call execution, and response parsing into reusable modules, enabling companies to standardize interfaces, eliminate custom development for most partners, cut integration costs by 86 % and pave the way for a hot‑swappable orchestration platform.
The article explains why layered architectures such as Clean, Onion, and Hexagonal are essential for reducing coupling and improving maintainability, introduces the COLA (Clean Object‑oriented and Layered Architecture) derived from them, and presents a concrete Go project scaffold with clearly defined Domain, Application, Infrastructure, and Adapter layers and recommended directory layout.
