The article examines how design patterns serve as intermediate code conventions, discusses their performance impact, class‑explosion risk, team skill gaps, project environment, and agile constraints, and offers practical advice for balancing code quality with business realities.
This article walks through the progressive evolution of a software system—from a traditional monolithic architecture to a task‑oriented monolith, then to Command‑Query Separation (CQS) and finally to a full CQRS solution—explaining the motivations, trade‑offs, and techniques such as eventual consistency, event sourcing, and read‑model generation.
This article traces the evolution of software architecture from monolithic applications through vertical splitting and distributed services to modern microservices, outlines the key stages of microservice development, and presents a comprehensive technology stack—including communication protocols, API gateways, authentication, fault‑tolerance, logging, configuration, containerization, orchestration, and CI/CD tools—required to build robust backend systems.
The article predicts smartphones will dominate traffic for the next three years, argues that cross‑device frameworks like ReactNative, Weex and Flutter are essential, and proposes a streamlined R&D model at Xianyu with full‑stack mobile engineers and infrastructure engineers supported by a unified container, programming plane, workflow, and the high‑performance, W3C‑compliant KUN rendering engine to boost iteration speed, consistency, and talent efficiency.
This article translates Mahesh Balakrishnan’s 42 practical lessons on building a production database, covering customer focus, project management, design principles, code review, strategy, observability, and research, offering actionable guidance for infrastructure engineers and architects.
This article objectively explains Domain‑Driven Design, compares it with traditional data‑driven approaches, and details how DDD was applied in the architecture, strategic and tactical design, context integration, and business‑logic implementation of ZuanZuan's complex pricing system, including code examples.
This article explains the concept of software‑architecture tradeoffs, why they are inevitable, the key system attributes involved, and how architects can consciously balance scalability, simplicity, interoperability and other “‑ilities” to make informed design decisions.
By exploring popular open-source codebases such as Chromium, Electron, Flutter, React, and Go, developers can deepen their understanding of software architecture, DevOps practices, cross-platform development, and essential programming principles, turning code reading into a powerful self-learning strategy.
The article outlines twenty‑four essential capabilities—spanning continuous delivery, architecture, product and process, lean management, and culture—that research shows drive high performance in software delivery and organizational outcomes.
This article explains how Onion Architecture, built on Domain‑Driven Design principles, organizes software into concentric layers that isolate core business logic, improve maintainability, testability, and flexibility, and outlines its layers, dependencies, services, testing strategies, and applicability to microservices.
This article reviews the rapid growth of software scale and complexity, traces the evolution from monolithic to microservice architectures, and outlines the essential backend technologies—including service communication, API gateways, authentication, fault handling, logging, configuration, containers, orchestration, and CI/CD—that enable modern cloud‑native microservice systems.
This article explains the Chain of Responsibility design pattern in Java, illustrating its use for multi‑level approval workflows during high‑traffic events, provides step‑by‑step code implementations, refactors naive IF logic into modular link classes, and demonstrates testing, highlighting benefits for clean, extensible backend architecture.
The article explains how many microservice migrations end up as “distributed monoliths,” detailing why splitting a monolith without proper domain design and protective mechanisms can worsen stability, increase latency, and fail to deliver the promised efficiency gains.
This article introduces eight typical software architecture design patterns—including single-database single-application, content distribution, query separation, microservices, multi-level caching, sharding, elastic scaling, and multi-datacenter deployment—explaining their structures, typical use cases, advantages, and disadvantages for building scalable, high-performance systems.
Shopee’s Merchant Services team created a visual, configurable onboarding platform that abstracts purchase flows into reusable templates and six modular configuration sections, moving product‑launch responsibilities from developers to operators, cutting code changes, boosting launch efficiency by about 75 % and adding import/export and validation tools.
The article examines the typical traits of massive legacy codebases, outlines the technical debt they generate, and proposes practical strategies—from design‑pattern mastery and daily code reviews for small teams to metrics‑driven debt tracking, agile practices, and clean‑architecture principles for million‑line and ten‑million‑line systems—aimed at safely evolving such systems while maintaining team stability.
This article explains why clear architecture diagrams are essential for communication, outlines common pitfalls, defines architecture and its diagram types, introduces the 4+1 view classification and the C4 modeling approach, and provides practical guidance and examples for producing self‑describing, audience‑focused diagrams.
The article explains the importance of measuring software architecture, outlines the granularity of metrics from code to infrastructure, and provides concrete measurement indicators for code implementation, component design, architecture design, and runtime infrastructure to guide effective architecture governance.
This article chronicles the step‑by‑step evolution of a workflow engine, detailing how simple sequential approvers were expanded into hierarchical trees supporting parallel, multi‑sign, conditional, proxy, and scripted nodes, while introducing state management, rejection handling, and progress metrics.
This article explains the Chain of Responsibility design pattern, its use cases, and demonstrates step‑by‑step refactoring in Java—from a verbose conditional example to a clean, extensible handler chain, including abstract handlers, concrete handlers, and a factory‑based configuration.
This article explains how to keep software architecture simple and appropriate by applying KISS principles, balancing completeness, flexibility, and lightness, outlines when pre‑design is sufficient or excessive, presents core design principles such as SOLID, N+1, statelessness, and details a six‑step C4‑based design and review process.
This article explains the Observer design pattern, outlines its advantages and drawbacks, and demonstrates practical implementations through three real‑world scenarios—weather forecasting, payment processing, and data subscription—providing complete Java and PHP code samples that illustrate subjects, observers, and notification mechanisms.
This article explains the basic concepts of software modeling, the role of UML diagrams, and how to organize those models into a coherent software design document that guides architects, developers, testers, and stakeholders throughout the development lifecycle.
This article uses humorous everyday scenarios to illustrate 21 classic software design patterns, explaining each pattern's intent, structure, advantages, and drawbacks, helping readers grasp abstract concepts through relatable analogies.
This article explores the practical challenges of using MVC and related architectural patterns, compares implementations from Microsoft, Apple, and industry experts, discusses controller bloat and view‑model relationships, and proposes solutions such as view‑to‑model factories, multi‑controller designs, and MVVM adoption to improve testability and maintainability.
This article explains how to design robust technical architectures by applying strategic principles of suitability, simplicity, and evolution, alongside tactical guidelines for high concurrency, high availability, and business design, and illustrates the concepts with logical and physical architecture diagrams.
This article explains the purpose and benefits of software architecture diagrams, introduces basic concepts and the 4+1 view classification, describes what makes a good diagram, outlines common pitfalls, and presents the C4 modeling approach with practical examples for clear communication among stakeholders.
This article explains the purpose and definition of software architecture diagrams, introduces the 4+1 view classification and the C4 model (system context, container, component, and code diagrams), discusses common pitfalls, and provides practical guidance and tool recommendations for producing self‑describing, audience‑focused architecture visuals.
In a Stack Overflow Podcast interview, former GitHub CTO Jason Warner recounts his unconventional path from a Connecticut farm to leading massive platform scaling, shares insights on engineering leadership, product strategy, venture investing, and the future of cloud, data, and blockchain technologies.
This article introduces the concept of software architectural patterns, explains why they are essential, and details five popular patterns—layered, microkernel, event‑driven, microservices, and space‑based—along with guidance on when and where to apply each.
The article details how NetEase Yanxuan applied Domain‑Driven Design to reconstruct its Product Center middle‑platform, using strategic and tactical design, COLA layered architecture, and an event‑driven mechanism to eliminate duplicated logic and heavy coupling, cutting code volume by roughly two‑thirds while addressing entity scope, model richness, and microservice granularity challenges.
This article explains the Chain of Responsibility design pattern, illustrates common misuse with a multi‑if game‑level example, and then shows step‑by‑step refactorings—including linked handlers, an abstract base class, a factory and enum‑based configuration—to produce clean, extensible Java code.
This article introduces ten common software architecture patterns—layered, client‑server, master‑slave, pipe‑filter, proxy, P2P, event‑bus, MVC, blackboard, and interpreter—explaining their structures, typical use cases, and advantages to help developers choose suitable designs for large‑scale systems.
This article explains the evolution of programming—from machine code, assembly, and high‑level languages—to the software crises that led to structured programming, object‑oriented design, and ultimately the emergence of software architecture as a solution for managing system complexity.
This article traces the evolution of software development—from machine language and assembly to high‑level languages—explores the two software crises, explains why software architecture emerged, and clarifies core concepts such as systems, subsystems, modules, components, frameworks, and architecture itself.
This article explores the evolution of software development from machine code to high‑level languages, explains the two software crises and their solutions, defines system, subsystem, module, component, framework and architecture, and concludes that software architecture is a strategic response to system complexity requiring careful judgment and trade‑offs.
This article introduces eight typical software architecture design patterns—including single-database single-application, content distribution, query separation, microservices, multi-level caching, sharding, elastic scaling, and multi-datacenter deployment—explaining their structures, typical use cases, advantages, disadvantages, and practical considerations for building scalable, reliable systems.
This article explains eight widely used software architecture design patterns—including single‑database single‑application, content distribution, query separation, microservices, multi‑level caching, database sharding, elastic scaling, and multi‑data‑center—detailing their typical scenarios, advantages, and disadvantages for backend developers.
The article introduces eight widely used software architecture design patterns—including single‑database, content distribution, query separation, microservices, multi‑level caching, sharding, elastic scaling, and multi‑datacenter deployment—explaining their typical structures, suitable scenarios, and the key pros and cons of each.
This article explains how to design clear, consistent API return codes and messages by referencing HTTP status codes, defining code‑message pairs, supporting personalized messages for different clients, and using unified handling for monitoring and alerting, ultimately improving communication and maintenance costs.
This article explains the Decorator design pattern, contrasting it with inheritance, and shows how to dynamically extend Java classes—especially I/O streams—using composition, complete with code examples, class diagrams, advantages, drawbacks, and practical usage scenarios.
In this interview, Meituan Selection architect Xu Po shares his 14‑year journey, explains how logistics architecture balances process and result quality, outlines the four pillars for successful architecture implementation, discusses the core value of architects, team organization models, essential skills, and the role of domain‑driven design.
This article shares the author’s experience and reflections on software architecture, covering its definition, iterative evolution, closed‑loop feedback design, microservice adoption, the impact of organizational culture, and the mindset and soft skills required of modern architects.
The article analyses low‑code platforms by defining low‑code as visual programming, contrasting declarative and imperative approaches, examining front‑end and back‑end implementation schemes, interaction models, storage options, workflow engines, and future trends, ultimately showing that declarative foundations drive both strengths and limitations.
The Singleton design pattern guarantees a single, globally accessible instance, reducing memory overhead and global variables, with eager (init) and lazy (sync.Once) thread‑safe implementations in Go, and practical uses such as configuration management in Python, shared DB connections in PHP, and UI components like toasts in JavaScript.
This article explains the differences and similarities between the Factory and Strategy design patterns in Java, provides complete code examples, compares their execution results, and discusses how Strategy can resemble micro‑service composition while reducing code redundancy.
This article details a year‑and‑a‑half of boundary‑governance work on a supplier platform, explaining why fragmented responsibilities hurt efficiency, how the team expressed, identified, and solved boundary issues through clear domain definitions, unified language, and staged migration, and the measurable improvements achieved.
The article explains that becoming a software architect requires more than years of experience—it demands a blend of deep technical expertise, strong business insight, and effective management skills to build a personal moat and avoid being left behind as the industry evolves.
This article compares Java's Factory and Strategy design patterns, explaining their concepts, showing UML diagrams, providing complete code examples, and demonstrating how each pattern affects code structure, flexibility, and maintainability, while drawing parallels to micro‑service architecture.
This article explains how to design robust 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 for real‑world systems.
The article reflects on a dozen years of software development experience to propose three evolving definitions of a software architect, classify various architect roles, and compare centralized versus collaborative work styles, highlighting why the term is often misused in the industry.
This article humorously illustrates 23 classic software design patterns—such as Factory Method, Builder, Abstract Factory, Prototype, Singleton, Adapter, Bridge, Composite, Decorator, Facade, Flyweight, Proxy, Chain of Responsibility, Command, Interpreter, Iterator, Mediator, Memento, Observer, State, Strategy, Template Method, and Visitor—using everyday relationship scenarios to make each pattern’s intent and structure easy to grasp.
This article examines the evolution of cross‑platform frontend technologies, outlines key criteria for selecting a solution, compares major approaches such as WebView, native rendering, and self‑rendering, and presents a practical low‑code, Flutter‑based implementation that delivers fast, consistent multi‑device applications.
This article presents thirty practical software‑architecture principles—from keeping designs simple and avoiding unnecessary features to mastering concurrency, distributed systems, and user experience—providing a comprehensive guide that helps architects make informed, ROI‑driven decisions while fostering scalable, maintainable solutions.
The article reflects on a dozen years of software development experience to propose three evolving definitions of a software architect, examines why the term is often misused, categorises different architect types, and compares centralized versus connective work styles for effective R&D management.
This article explains common misconceptions about application layering, outlines essential principles for maintainable layers, details Alibaba's multi‑layer architecture, proposes optimized layering with service and manager responsibilities, discusses domain model conversions, and concludes with practical guidance for clear, reusable backend design.
This article examines the concept of business architecture, its origins in TOGAF, and presents a detailed case study of Qunar’s activity capability layer design, highlighting pain points, architectural solutions, and a step-by-step methodology for building robust, reusable activity systems.
During the Chinese New Year, the author reflects on the declining state of Chinese football and draws parallels to large‑scale digital transformation projects, exploring how component‑based, cloud‑native architecture and domain‑driven design can address the complexities of enterprise business systems, improve modularity, and enable rapid, resilient evolution.
This article explains what microservices are, how they differ from traditional monolithic apps, illustrates their benefits and drawbacks with an Amazon product‑page example, describes containers and Docker, and shows why Kubernetes is a natural platform for managing microservice‑based systems.
This article presents thirty concise architectural principles covering simplicity, YAGNI, iterative development, testing, ROI, user focus, modular design, configuration, server concurrency, distributed system challenges, and user experience, offering practical guidance for engineers to build scalable, maintainable software systems.
This article reviews key concepts from the book "Software Architecture with Patterns" and discusses how architectural patterns such as layered architecture, microkernel, and GoF design patterns can guide the decomposition of monolithic applications and improve the extensibility of complex systems.
The article critiques traditional software architects as bottlenecks, shares personal experiences at eBay and Alibaba, argues that dedicated architecture departments often cause more harm than good, and advocates that every engineer develop architectural thinking, offering guidance for engineers, team leads, and CTOs.
This article explains how Airwallex uses Domain-Driven Design (DDD) to model a complex payment system, detailing strategic and tactical patterns, bounded contexts, domain events, and the translation of domain models into microservice architectures, while highlighting the benefits of clear communication and modular design.
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.
