This article explains how Airwallex uses Domain-Driven Design (DDD) to model a complex payment system, covering problem and solution spaces, bounded contexts, domain models, services, events, infrastructure, and the transition from domain concepts to microservices.
This article presents a light‑hearted yet comprehensive overview of 23 classic software design patterns—such as Factory Method, Builder, Abstract Factory, Prototype, Singleton, Adapter, Bridge, Composite, Decorator, Facade, Flyweight, Proxy, Chain of Responsibility, Command, Interpreter, Iterator, Mediator, Memento, Observer, State, Strategy, Template Method, and Visitor—explaining each pattern’s intent, structure, advantages, and drawbacks through everyday analogies.
This article explains why clear architecture diagrams are essential for communication, defines system architecture, compares the 4+1 and C4 view models, and offers practical guidance on choosing audiences, diagram elements, and drawing techniques to create self‑describing, accurate architectural visuals.
Domain-Driven Design (DDD) is a model‑driven approach that places the business domain at the core, using ubiquitous language, bounded contexts, and building blocks such as entities, value objects, and services to create a cohesive domain model that aligns code with complex business requirements.
This article presents thirty practical architecture principles—from keeping designs simple and avoiding unnecessary features to embracing distributed, stateless systems and thoughtful configuration—offering a comprehensive guide for architects to lead, mentor, and build resilient, user‑focused software.
This article explores why software systems inevitably become more entropic and complex, draws parallels with physical entropy and the Constructal Law, identifies sources of uncertainty, scale, and cognitive cost, and presents practical approaches such as isolating core kernels, adopting Domain‑Driven Design, and applying Clean Code principles to keep systems maintainable.
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 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, and the pros and cons of adopting microservices in modern software systems.
This comprehensive guide explains the definition of software architecture, its essential concepts, layered classifications, various architecture levels, evolution from monolith to microservices, common pitfalls, and metrics for evaluating architectural soundness, providing practical insights for architects and developers alike.
This article provides an extensive introduction to software architecture, covering its definition, essential concepts such as systems, subsystems, modules, components, and frameworks, various architectural layers and classifications, architectural levels, strategic versus tactical design, evolution from monoliths to micro‑services, common pitfalls, measurement criteria, and recommended learning resources.
This article explains why code quality often degrades despite clear requirements, introduces Domain‑Driven Design (DDD) and Algebraic Data Types (ADT) as a unified modeling approach, shows how Curry‑Howard isomorphism connects domain knowledge to type systems, and demonstrates practical TypeScript examples that reduce illegal states, defensive code and improve maintainability.
This article explains the Strategy design pattern, its definition, structure, Java implementation with code examples, advantages, disadvantages, and typical scenarios where interchangeable algorithms improve flexibility and maintainability.
This article introduces the 4+1 view model of software architecture, explaining its four main views—Logical, Process, Physical, Development—and the additional Scenario view, illustrating each with examples and diagrams to guide architects in comprehensive system design.
This article introduces Domain-Driven Design (DDD), explains key terminology, describes the evolution of architecture from SaaS to IaaS, details bounded context concepts and division rules, and reviews major architectural styles such as clean layered, hexagonal, and onion architectures for building robust software systems.
This guide walks through applying Domain‑Driven Design to a brand‑new project, covering essential terminology, the evolution from SaaS to IaaS, defining bounded contexts, the four DDD boundaries, and various architectural styles such as clean layered, hexagonal, and onion architectures, with practical insights for implementation.
The article presents thirty practical architectural principles—ranging from simplicity, YAGNI, iterative development, automated testing, and ROI to server concurrency, distributed system design, user experience, and configuration management—aimed at guiding engineers and teams toward robust, scalable, and maintainable software solutions.
The article presents clean‑architecture best practices for Go microservices built with trpc‑Go, recommending a four‑layer pyramid (gateway, logic, repo, entity), strict dependency inversion, interface‑based injection, gomock testing, centralized JSON configuration, and a three‑phase rollout to replace tangled packages and global imports while avoiding DDD complexity.
The article explains the origins and four quadrants of technical debt, outlines its detrimental effects on software quality and maintainability, and offers practical approaches—including daily debt management, clear technical standards, continuous technology monitoring, visualization, and sustained investment—to identify, prioritize, and reduce technical debt in development teams.
The article explains how microservices differ from monolithic applications by emphasizing team‑based, autonomous service design, data‑sharing challenges, dependency management, API communication patterns, and the use of shared caches to improve performance and reliability.
This article presents thirty practical software architecture principles—ranging from simplicity and YAGNI to distributed system design, user experience, and configuration management—offered by architect Srinath to guide teams in making better technical decisions and fostering collaborative, high‑quality product development.
This article presents thirty practical software architecture principles—from simplicity and YAGNI to distributed system design and user experience—offering actionable guidance for engineers to shape robust, maintainable, and user‑centric systems.
The article presents thirty concise architectural principles—ranging from simplicity, YAGNI, iterative development, automated testing, ROI, user‑centric design, modularity, to distributed system concerns like statelessness, idempotency, CAP theory, and configuration best practices—offered as a practical guide for architects and development teams.
This article explains Java's Simple Factory design pattern, covering its definition, class structure, implementation steps with code examples, advantages and disadvantages, and suitable application scenarios, helping developers understand when and how to use this creational pattern effectively.
This article explains the fundamental definition of software architecture, distinguishes systems, subsystems, modules, components, frameworks, and various architecture layers, and examines how architectures evolve from monoliths to distributed services and micro‑services while highlighting common pitfalls and evaluation criteria.
This article provides a detailed English summary of 23 Java design patterns—including their purposes, core principles, classification into creational, structural, and behavioral groups, definitions, typical use‑cases, and visual diagrams—helping developers understand how to write reusable, readable, extensible, and reliable code.
This article explains Clean Architecture, shows how Domain‑Driven Design fits into its concentric‑layer model, and demonstrates how adding Command‑Query Responsibility Segregation (CQRS) enhances scalability, testability, and maintainability while outlining practical implementation steps, benefits, and trade‑offs.
Idempotency ensures that repeated API calls produce the same result, preventing duplicate processing in high‑traffic systems; this article explains why it matters, typical duplicate request scenarios, and a practical implementation using client‑generated identifiers to cache and filter repeated submissions.
This article explains the essence of software architecture, covering definitions, system vs. subsystem, module vs. component, framework vs. architecture, various architectural layers, classifications, evolution from monolith to microservices, and how to evaluate a design’s suitability for business and non‑functional requirements.
This article explains the importance of clear architecture diagrams, defines architecture and its visual representations, outlines common diagram types and pitfalls, and introduces the C4 modeling approach with practical guidance for creating self‑describing, audience‑focused system diagrams.
This article explains what microservices are, how they differ from traditional monolithic applications, provides an Amazon product‑listing example, discusses containers, compares the two, outlines when to adopt microservices, lists their pros and cons, and describes how Kubernetes supports cloud‑native microservice architectures.
This article summarizes Evans' concise DDD booklet, explains why domain‑driven design is needed, outlines the problems it addresses, describes strategic and tactical design practices—including bounded contexts, ubiquitous language, aggregates, and event storming—and highlights common pitfalls and supporting tools.
This article explains Domain-Driven Design (DDD), outlining why it is needed, how it solves common software development problems, and detailing strategic and tactical design steps, event‑storming techniques, and common misconceptions to help teams align business and technical perspectives.
Learn how to create clear, audience‑focused software architecture diagrams using the C4 model, covering essential concepts, diagram types, common pitfalls, and practical tips to ensure your diagrams communicate effectively without unnecessary complexity.
This article explains the proxy design pattern through an engaging cartoon story, analyzes the roles of client, target, and proxy, discusses its benefits and variations, and shows practical usage examples such as ES6 Proxy, virtual image lazy‑loading, and a Golang implementation.
The article shares the author’s four‑year journey as a software architect at Dangdang, detailing practical experiences in platform reconstruction, order system planning, technology‑stack selection, open‑source framework development, and the four essential growth elements—learning, adapting, collaborating, and driving—offering actionable insights for technical leaders.
This article explains what microservices are, how they differ from traditional monolithic apps, illustrates their use with an Amazon product page example, and explores the relationship with containers and Kubernetes, while outlining benefits, drawbacks, and design considerations for adopting a microservice architecture.
The article explains why a well‑designed API return‑code system—modeled after HTTP status codes, with clear numeric ranges, descriptive messages, and personalized user messages—reduces communication overhead, simplifies maintenance, and enables effective monitoring and alerting for backend services.
This article explains how to design robust backend technical architectures by addressing strategic principles such as suitability, simplicity, and evolution, and tactical guidelines covering high concurrency, high availability, and business design, while illustrating logical and physical architecture diagrams and practical implementation tips.
This article explains the essence of software architecture, its core principles, the distinction between development and architecture design, and presents a methodology based on TOGAF and the ADM cycle, covering business, data, application, and technology architecture domains.
This article explains the fundamentals of software architecture, why it is needed, the responsibilities of architects, various architectural classifications, and introduces classic and modern application architectures such as layered, CQRS, hexagonal, onion, and the open‑source COLA framework with its design and extension principles.
The article presents a detailed 19‑section knowledge map for software architects, covering everything from core responsibilities and fundamentals to distributed caching, messaging, load balancing, performance testing, OS, algorithms, networking, databases, JVM, micro‑services, DDD, security, high availability, big data, and blockchain, with visual mind‑maps for each topic.
This article surveys the programming languages and technology stacks behind a wide range of operating systems, user interfaces, desktop search tools, office suites, databases, browsers, servers, and other software, highlighting the prevalence of C, C++, Java, and other languages across the industry.
The article explains how the misconception of treating distribution as the whole of microservices leads to a distributed‑monolith trap, and shows how mixing command‑driven and event‑driven communication can decouple services, improve reliability, and guide a smooth migration from monolith to microservices.
This article explains why and when to break a monolithic application into microservices, outlines the business and technical signals that trigger splitting, presents guiding principles, functional and non‑functional strategies, and risk‑mitigation practices to ensure a smooth, sustainable migration.
This article explains how to transform product requirements into robust technical architectures by addressing uncertainty through strategic principles—suitability, simplicity, evolution—and tactical guidelines covering high concurrency, high availability, and business design, illustrated with logical and physical diagrams.
This article explores how to transform product requirements into robust technical architectures by addressing uncertainty, outlining strategic principles—appropriateness, simplicity, evolution—and tactical guidelines for high concurrency, high availability, and business design, while illustrating logical and physical architecture diagrams.
This article clarifies the essence of software architecture by defining key concepts such as system, subsystem, module, component, framework versus architecture, and then details the multiple architectural layers—including business, application, data, code, technical, and deployment—while highlighting their purposes, relationships, and design considerations.
This article explains the philosophical basis of object‑oriented thinking, distinguishes attributes and operations, compares data‑model and object‑model designs with Java and SQL examples, discusses composition versus aggregation through a digestion model, and illustrates application‑service patterns in account credit scenarios.
The article explains various context‑mapping techniques from Domain‑Driven Design—such as Partnership, Shared Kernel, Customer/Supplier, Conformist, Anti‑Corruption Layer, Open Host Service, and Published Language—and advises when to apply each based on code, team, and business considerations.
This article clarifies the fundamental concept of software architecture, distinguishes related terms such as system, subsystem, module, component, framework, and architecture, and outlines the five major architectural layers—business, application, data, code, technical, and deployment—providing a comprehensive guide for architects and developers.
The article explains why a solid code structure is essential, outlines the principles of single responsibility, reusability and clear definitions, and details the roles of Model, Util, Service, DAO and Controller, while discussing their relevance to Web, Android and iOS development.
This article explains what a rule engine is, why it is useful, common products, core concepts such as rule files, LHS/RHS, facts, and various modeling patterns, as well as management, execution modes, real‑world use cases and best‑practice recommendations for building scalable backend rule‑processing systems.
This article explains how mismatched vocabularies between domain experts and developers hinder project progress, and how establishing a shared, model‑driven language can reduce misunderstandings, streamline communication, and improve the reliability of software built with Domain‑Driven Design.
This article presents a comprehensive, layer‑by‑layer framework for unifying business architecture design, detailing product contracts, business models, services, flows, components, infrastructure, and model adapters, and shows how low‑code and hard‑coded approaches can be combined to accelerate development while maintaining consistency.
The article explains how mismatched vocabularies between domain experts and developers hinder project progress, and argues that establishing a shared, model‑driven language—central to Domain‑Driven Design—can improve communication, reduce misunderstandings, and create more reliable software.
This article explains workflow fundamentals using a train‑transport analogy, describes key design elements such as forms, task nodes, and routing, compares open‑source engines, and details a low‑code platform architecture that separates business logic, process control, and event handling for flexible, distributed execution.
The talk demonstrates how to apply Domain‑Driven Design and microservice architecture to an e‑commerce voucher platform by defining problem spaces and bounded contexts, prioritizing boundaries over aggregates, using layered‑on‑demand infrastructure, and following SOLID principles to achieve clear, maintainable services.
This article introduces seven widely used software architecture patterns—layered, multi‑layer, pipe‑filter, client‑server, MVC, event‑driven, and microservices—explaining their contexts, problems they solve, typical structures, advantages, drawbacks, and suitable application scenarios.
This article explains the fundamentals of software architecture, why architecture is needed, the responsibilities of architects, various architecture categories, common styles such as layered, CQRS, hexagonal and onion architectures, and introduces the open‑source COLA framework with its layered design, extension points and standards.
This article shares eight months of hands‑on experience with Domain‑Driven Design, explaining why traditional waterfall approaches hinder true business understanding and presenting practical notes, mind‑map visualizations, and step‑by‑step guidance on effective modeling, knowledge digestion, continuous learning, and deep model design.
The article outlines twenty‑four essential capabilities—including version control, automated deployment, continuous integration, trunk‑based development, test automation, lean management, and cultural practices—that together drive high‑performance software delivery and organizational effectiveness.
This article explains how Vivo Game Center adopted a modular architecture—combining componentization, configuration, and experiment-driven deployment—to enable rapid, flexible UI layout adjustments, unified backend processes, and data-driven A/B testing, thereby improving development efficiency and user‑targeted operations.
This article traces the evolution of programming paradigms—from low‑level machine code through procedural and object‑oriented approaches—explains the pitfalls of poor abstraction, introduces domain‑driven design, and reviews key software design principles such as SOLID, OCP, DIP, PLOA and KISS.
This article explains the concept of software architecture, its necessity, the role of architects, various architectural categories, typical patterns such as layered, CQRS, hexagonal and onion architectures, and introduces the COLA open‑source application architecture with its layered design, extension mechanisms, and specification guidelines.
This comprehensive guide explains the essence of software architecture, its layers and classifications, architectural levels, strategic versus tactical design, evolution from monoliths to micro‑services, common pitfalls, and key metrics for evaluating a sound architecture.
This article provides a comprehensive overview of software architecture, covering its definition, essential concepts such as systems, subsystems, modules, and frameworks, various architectural layers and classifications, evolution from monolithic to microservices, design principles, evaluation criteria, and typical misconceptions to avoid.
Anemic domain models separate data and behavior, leading to procedural code and maintenance challenges, while rich (or “充血”) models embed logic within objects, offering clearer OOP design, better encapsulation, and scalability, though they require careful design to avoid complexity.
The article explains the differences between the anemic (transaction‑script) and rich (domain‑model) approaches in DDD, discusses their historical origins, advantages, drawbacks, and provides guidance on when and how to apply each model in software design.
The article explains the rise of Domain-Driven Design, its strategic and tactical design aspects, and how it helps define business boundaries to solve microservice decomposition challenges, providing a step‑by‑step approach for architects transitioning from monolithic to microservice systems.
This article explains the fundamentals of Domain-Driven Design, covering its core concepts, step‑by‑step design methodology, domain modeling techniques, and how to apply DDD in microservice architectures with considerations for technical elements such as distributed transactions and scalability.
This article explores six classic design patterns—Strategy, Chain of Responsibility, Template Method, Observer, Factory, and Singleton—detailing their real‑world business scenarios, core principles, Java implementations with Spring integration, and how they improve code maintainability, extensibility, and adherence to SOLID principles.
This article explains how to design robust technical architectures by applying strategic principles of suitability, simplicity, and evolution, and tactical principles covering high concurrency, high availability, and business design, while illustrating logical and physical architecture diagrams and offering practical implementation advice.
This article explains the differences and similarities between the Factory and Strategy design patterns in Java, provides concrete code examples for each, and discusses how the Strategy pattern can offer more flexible behavior composition compared to the traditional Factory approach.
The article explains how Domain-Driven Design (DDD) rose to prominence by addressing business‑boundary challenges in microservice architectures, outlines the evolution of software architectures, and details DDD’s strategic and tactical design practices for creating clear, maintainable service boundaries.
This article explains how good software architecture enables easy evolution, fault tolerance, and low maintenance, while bad architecture leads to complexity and brittleness, and it outlines key principles, design styles, and practical techniques such as domain‑centric, microservices, event‑driven, and CQRS to build robust, adaptable systems.
This article provides a concise overview of Domain-Driven Design, explaining why it matters, defining key concepts such as domain, model, bounded context, and ubiquitous language, and illustrating how DDD helps teams tackle core software complexity through collaborative modeling and shared terminology.
This guide walks developers through DrawIO secondary development, explaining why integration is needed, how to set up Java/Ant, clone and build the source, configure dev mode, deploy via various platforms, and use core APIs like getCurrentFile and loadFile, with a starter scaffold on GitHub.
This article presents a practical, seven‑step methodology for efficiently reading Redis source code, covering project mapping, prerequisite knowledge, starting from basic modules, identifying the core execution path, balancing overall structure with detailed logic, handling auxiliary features, and performing targeted gap‑filling to master the codebase.
Microservice architecture introduces complexity, but using scaffolding tools such as Spring Boot and Spring Data lets developers focus on business logic by providing reusable components, reducing duplication, and simplifying data access, while avoiding the pitfalls of building custom persistence layers from scratch.
This article introduces ten fundamental software architecture patterns—including layered, client‑server, master‑slave, pipe‑filter, proxy, P2P, event‑bus, MVC, blackboard, and interpreter—explaining their structures, typical use cases, advantages, and drawbacks to help developers choose the right design for large‑scale systems.
This article explores the evolution of software development from machine code to high‑level languages, explains the two software crises, and defines key architectural concepts such as systems, subsystems, modules, components, frameworks, and the role of software architecture in managing complexity.
This article explains the essence of software architecture, defining systems, subsystems, modules, components, frameworks, and various architectural layers such as business, application, data, code, technical, and deployment, and discusses architectural evolution from monolithic to distributed and microservice designs, including common pitfalls and recommended reading.
The article explains the core characteristics of entities—identity and continuity—using DDD concepts, demonstrates why a Message in a messaging scenario qualifies as an entity, and argues that senders and recipients (contacts) should also be modeled as entities rather than value objects.
The article compares the work attitude, technical depth, product awareness, and leadership responsibilities of senior developers and software architects, offering practical advice and concrete steps for engineers who want to upgrade their skills and transition into an architectural role.
This article explores how to transform product requirements into robust technical architectures by addressing uncertainty, outlining strategic principles—appropriateness, simplicity, evolution—and tactical guidelines for high concurrency, high availability, and business design, while illustrating logical and physical architecture diagrams and offering practical design recommendations.
This article explains the common misconceptions about software architects, outlines the essential technical and soft‑skill requirements for senior developers to become architects, describes practical upgrade paths, and details the typical responsibilities and daily activities of an architect.
This article explains the purpose of software architecture diagrams, defines key concepts, outlines common diagram types such as the 4+1 view and C4 model, discusses criteria for good diagrams, addresses typical pitfalls, and provides practical guidance and tool recommendations for producing clear, audience‑focused architecture visuals.
This article outlines the progression of software architecture from traditional monolithic systems through distributed applications and microservices to modern serverless designs, highlighting each model's structure, benefits, drawbacks, and typical use cases for developers and architects.
The article argues that over the past decade China's rapid, short‑term development model has created a serious talent gap in software architecture for B2B and industrial internet sectors, limiting the country's core competitiveness despite flourishing consumer‑facing tech companies.
This article explains the Builder design pattern in Java with complete code examples—including Product, abstract Builder, ConcreteBuilder, Director, and client code—demonstrates the output, compares it to the simple factory pattern, and briefly shows how ASM bytecode manipulation can generate similar constructs.
This article presents 30 widely‑accepted software architecture principles—grouped into basics, feature selection, server design, distributed systems, user experience, and challenges—to help architects act as gardeners who shape, refine, and sustain robust, maintainable systems.
This article shares a senior CTO’s journey through Alibaba and Ant Group, detailing how commercial goals and technology co‑evolve, the pivotal architectural decisions, risk‑management practices, organizational design, and leadership principles that shape effective technology leadership.
The article recounts a senior technology leader’s journey from early PHP/MySQL work to senior CTO roles at Ant Group and Alibaba, arguing that a CTO must be an executor who aligns business goals with evolving distributed, cloud‑native architectures, outlines three leadership stages, key responsibilities, and offers a Z‑shaped career roadmap for future CTOs.
This article introduces the essential principles of Domain‑Driven Design, explaining its two‑stage approach, key building blocks such as entities, value objects, aggregates, factories, repositories, services, and domain events, and shows how DDD fits into layered architecture and common anti‑patterns.
The article explains the concept of software scaffolding, why it is needed for microservice development, outlines key design principles, shares a real‑world case of replacing a custom persistence layer with Spring Data, and reviews popular scaffolding tools such as Vue CLI, Maven, Netty, Java EE, Dropwizard and Spring Boot.
This article explains how to design a stable and high‑performing software architecture by addressing strategic principles—suitability, simplicity, evolution—and tactical guidelines for high concurrency, high availability, and business‑oriented design, while illustrating logical and physical architecture diagrams.
This article explains how Domain‑Driven Design (DDD) gained popularity alongside microservices, outlines the evolution of software architectures, highlights the boundary‑defining problems of microservices, and shows how DDD’s strategic and tactical design methods help create clear, high‑cohesion, low‑coupling systems.
The article explores how Conway’s Law and the entropy increase principle explain the dynamic nature of organizational structures in tech companies, highlighting the impact of communication patterns on system design, resource allocation, and team efficiency.
The article surveys the evolution of front‑end development, explains the surge of low‑code platforms and micro‑frontend architectures, and proposes a next‑generation, JSON‑driven framework that separates component creation from page configuration to combine rapid low‑code productivity with the flexibility of traditional code.
This article analyzes the root causes of low‑quality code—such as poor naming, tangled structure, and weak scalability—then presents practical ways to improve code quality through domain modeling, SOLID design principles, and design patterns, illustrated with real‑world case studies.
