This chapter summary traces the evolution from monolith to microservices, detailing core components like service discovery, circuit breakers, gateways, and observability, while stressing that adoption must be driven by business complexity and team needs — not service count — and provides a practical checklist for splitting and transformation.
This article walks through selecting and evaluating four architectural styles—layered, SOA, microservices, and event‑driven—by mapping concrete business evidence to style choices, explaining their benefits and costs, and applying ATAM terminology to assess key decisions in a healthcare platform scenario.
This article dissects orchestration-driven SOA, a 1990s enterprise architecture pattern centered on a central ESB and strict service taxonomy, explaining its layered topology, how reuse led to tight coupling and bloated models, the difficulties of distributed transactions, and why its failures directly inspired modern microservices principles.
This article guides readers through a 45‑minute review of the eight architecture categories—information‑system, layered, cloud‑native, SOA, embedded, communication, security, and big‑data—showing how to identify the relevant type from a problem statement, combine multiple architectures in a solution, and articulate the problem, solution, rationale, and cost with concrete examples and tables.
The article explains how enterprise architecture, layered architecture, SOA, microservices and cloud‑native each address different scales of system design, shows how they can coexist in a retail modernization roadmap, and guides architects on selecting and integrating the appropriate approach for each problem domain.
The article explains how a retail company’s fragmented CRM, ERP, warehouse, logistics and store systems cause point‑to‑point integration chaos, and shows how Service‑Oriented Architecture—through stable service contracts, a service registry, ESB mediation, and BPEL orchestration—provides a loosely‑coupled, scalable solution while contrasting SOA with micro‑services.
The article explains what an Enterprise Service Bus (ESB) is, outlines its core positioning, walks through the complete end‑to‑end workflow—from request entry, protocol adaptation, data conversion, routing, orchestration, to exception handling, logging, monitoring—and compares ESB with microservice gateways while providing a concrete order‑processing example.
The article explains that Service‑Oriented Architecture (SOA) focuses on integrating many heterogeneous systems through service contracts and an ESB as a means, contrasts orchestration with choreography, debunks common misconceptions, and shows how SOA’s core ideas survive in modern microservices.
The article clarifies that microservices are defined by business‑capability‑aligned, independently deployable services—not merely smaller services—detailing five core mechanisms, distributed‑system constraints, SOA comparison, and five common misconceptions.
CAP theoremDistributed SystemsIndependent Deployment
This article compares microservices and SOA, covering design philosophy, service granularity, autonomy, communication mechanisms, and deployment/operations, highlighting how microservices favor lightweight protocols, independent deployment, and container orchestration, while SOA relies on centralized middleware and coarse‑grained services.
Microservices and SOA differ in architecture design, communication methods, service granularity, governance, and deployment, with microservices favoring decentralized, fine‑grained, container‑based approaches while SOA relies on larger, centrally orchestrated services via an ESB, making each suited to distinct enterprise scenarios.
Microservices and Service‑Oriented Architecture (SOA) both aim to modularize systems, but they differ in design philosophy, technology heterogeneity, governance, and deployment, with microservices favoring fine‑grained, independent services, decentralized governance, and container‑based continuous delivery, while SOA relies on larger, centrally managed services via an ESB.
This guide walks you through ten practical nslookup commands for retrieving A, NS, SOA, MX, any, server-specific, reverse, PTR, timeout, and debug DNS records, complete with example syntax and screenshots to help you troubleshoot and verify DNS configurations.
This article explores the design and implementation of a disaster‑recovery data‑backup architecture for JD’s LBS C‑end SOA service, covering backup strategies, cost‑reduction techniques, grid‑based indexing with H3, client‑side caching, diff verification, and deployment considerations to balance reliability, performance, and expense.
This article explores a comprehensive disaster‑recovery strategy for LBS‑driven SOA services, detailing challenges of massive POI data backup, cost‑reduction techniques using grid‑based caching, H3 hexagonal indexing, selective data compression, and a hybrid client‑server fallback mechanism to achieve high availability at dramatically lower expense.
This article explains the fundamentals of Remote Procedure Call (RPC) frameworks, their underlying architecture, communication steps, role of providers, consumers, and registries, and compares popular RPC solutions with other service paradigms such as SOA, SOAP, and REST.
The article outlines emerging forces such as cloud, mobile, social, and big data that drive modern application architecture, advocates moving beyond traditional three‑tier designs, and recommends adopting service‑oriented, microservice, event‑driven, and open‑standard approaches while considering paradigms, models, and organizational structures.
This article traces the evolution of software architecture—from early monolithic Java war packages through Service‑Oriented Architecture to modern microservices and cloud‑native designs—highlighting their structural differences, benefits, challenges, and the key principles that guide successful migration to distributed, scalable systems.
This article explains the concepts, design principles, and key differences among RESTful, SOAP, RPC, SOA, and microservices, and outlines why microservices have emerged as an evolution of SOA, illustrated with typical framework examples and architectural evolution diagrams.
This article explains Huolala’s multi‑group microservice architecture, covering its background, core principles, deployment, discovery, routing strategies, extension mechanisms, and practical application scenarios that enable flexible, versioned, and policy‑driven service routing.
This article explains the concept and implementation principles of RPC frameworks, describes the roles of provider, consumer, and registry, outlines the communication, addressing, serialization, and service invocation steps, and compares RPC with SOA, SOAP, and REST in terms of architecture and usage.
The article critiques Alibaba’s recent “1+6+N” reorganization and explains why many digital and business middle‑platform projects fail in enterprises, arguing that true middle‑platform capabilities must stem from existing IT assets and should be treated as a shared service aggregation rather than a standalone product.
This article explains the core concepts, design principles, and key differences among RESTful, SOAP, RPC, SOA, and microservices, illustrating how they relate to each other and why modern architectures increasingly adopt microservices for scalability and business agility.
This article analyzes the concept of extension points, explains why traditional if‑else or naive strategy patterns break the Open‑Closed Principle, and demonstrates how plugin‑based micro‑kernel architectures, adapter patterns, and nature‑based modeling (as in Eclipse) enable flexible, self‑service platform development while reducing code coupling and maintenance overhead.
The article explains the purpose and structure of application communication diagrams, describes SOA‑oriented component layering, introduces the UML/BPMN EAP profile and Archimate concepts, and provides a detailed list of application component types for enterprise architecture modeling.
The article explains TOGAF's concept of business services, compares them with SOA and ITIL services, provides insurance and banking examples, and outlines a top‑down process for identifying and modeling business services within an enterprise architecture framework.
Viaduct, Airbnb’s data‑oriented service mesh built on GraphQL, replaces traditional procedural meshes by centralizing a schema that routes queries across thousands of micro‑services, enabling fine‑grained data access, serverless derived fields, automatic schema propagation, and improved observability, now handling most of Airbnb’s API traffic.
This article explains the concept and logical levels of application architecture within enterprise solution architecture, outlines the roles of enterprise and project‑level solution and application architects, and describes how standardization, reuse, and coordination of current and future states are achieved through defined guidelines and SOA practices.
This article explains the limitations of traditional load balancing, how CDN and DNS mechanisms work, the concept of SOA, and how DNS-based load balancing can distribute traffic across multiple servers, including practical examples and a list of supporting DNS service providers.
The article explains architectural thinking as a blend of system, structured, and programming mindsets, then details cloud three‑layer (IaaS‑PaaS‑SaaS) and SOA component‑service‑process models, their fusion, and how these concepts map to classic three‑tier, domain‑driven, and software technical architectures, ending with a hackathon announcement.
This article explains the limitations of traditional load‑balancing, describes how CDNs and DNS use distributed, hierarchical mechanisms such as SOA to achieve traffic distribution and fault tolerance, and outlines practical DNS‑based load‑balancing implementations and supported service providers.
This article explains why traditional single‑point load balancers are limited, how CDNs distribute traffic, the role of DNS and SOA in request routing, and how DNS‑based load balancing can improve availability and speed for high‑traffic websites.
This article examines the shortcomings of traditional single-point load balancing, explains how CDNs distribute traffic using DNS, details the DNS hierarchy and SOA mechanism, and shows practical steps to implement DNS-based load balancing with examples from GitHub and major DNS providers.
This article details Ctrip's transition from traditional SOA to a cloud‑native Service Mesh using Istio, covering background challenges, technical solutions for control and data planes, SDK compatibility, configuration management, performance optimizations, and future directions such as WebAssembly and sidecar considerations.
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 explains how architecture thinking bridges business and IT by using decomposition and integration, outlines the cloud three‑layer model (resource‑platform‑application), explores SOA layered architecture, and demonstrates how various architectural layering methods can be combined for coherent system design.
This article explores layered thinking in architecture design, detailing decomposition and integration, cloud three‑layer models, SOA component‑service‑process layering, and how to combine these approaches into coherent technical and application architectures for balanced business‑technology solutions.
This article explains the concept of layered thinking in architecture design, covering decomposition and integration, cloud three‑layer models, SOA component‑service‑process layering, application‑level layering, and how to combine these approaches into coherent, multi‑view architecture diagrams for both technical and functional perspectives.
This article explores layered thinking in system architecture, covering decomposition and integration, cloud three‑tier models, SOA component‑service‑process layers, their fusion, classic and domain‑driven application layers, and practical guidance for constructing clear, multi‑view architecture diagrams.
This article explains how layered thinking and layered models—covering decomposition, integration, cloud three‑layer architecture, SOA layering, and application architecture—provide a systematic approach to designing balanced, cohesive, and loosely‑coupled software systems.
This article explains the concept of layered architecture, covering decomposition and integration, cloud three‑layer models, SOA layering, database and service layers, application and domain layers, and provides guidance on constructing clear, multi‑view architecture diagrams for complex systems.
This article explains the concepts of Service Oriented Architecture (SOA), its core problems and solutions, introduces Enterprise Service Bus (ESB), and compares SOA with microservice architecture, highlighting how microservices evolve from SOA to achieve decentralized, componentized services.
The article explains the purpose and structure of application communication diagrams, describes SOA‑oriented application components, outlines the UML/BPMN EAP profile and Archimate modeling elements, and provides guidance on layering interaction, process, and entity components within logical enterprise architectures.
The article explains the concept of business services within the TOGAF framework, clarifies their definition and identification through examples from insurance and banking, and shows how they relate to SOA, ITIL, and enterprise architecture service models.
The article outlines Ctrip's multi‑stage architectural evolution, detailing its three‑tier composition of operations, framework, and applications, and examines concrete case studies such as the release system, configuration management, SOA, and a large‑scale User Profile big‑data project.
The article reviews modern application‑architecture trends, explains why traditional three‑tier designs are insufficient for cloud, mobile, social and big‑data environments, and proposes service‑oriented, micro‑service, event‑driven and open‑computing approaches together with architectural paradigms, models and organizational considerations.
This article explores the concept of layered thinking in architecture design, covering decomposition and integration, cloud three‑tier models, SOA layering, application and technical architecture patterns, and how to combine these approaches for clear, maintainable system diagrams.
This article compares microservices and SOA architectures, examining component sharing philosophies, service orchestration versus choreography, the role of API layers versus message middleware, and how remote service access differs, highlighting the impact on coupling, performance, and maintainability.
This article explains how layered thinking and layered models guide architecture design, covering decomposition and integration, cloud three‑tier (IaaS‑PaaS‑SaaS) and SOA layering, the role of service and data layers, and how to combine cloud and SOA concepts into coherent architectural diagrams.
This article explains the concept of layered architecture thinking, covering decomposition and integration, cloud three‑tier models, SOA layering, application‑level three‑tier patterns, and how to combine cloud and SOA approaches into a coherent, multi‑view architectural blueprint.
This article provides a comprehensive overview of major software architecture approaches—including layered, multi‑tier, service‑oriented, and microservice architectures—explaining their motivations, structures, advantages, disadvantages, and when to apply each pattern in modern software development.
This article explains how to achieve extensibility in business systems by addressing database scalability through horizontal and vertical sharding, middleware layers, flexible schema designs, and by applying SOA principles to application, interface, and rule‑engine layers for adaptable, high‑performance architectures.
This article explores practical approaches to building extensible business systems by addressing database scalability through sharding and partitioning, designing flexible application layers with configurable rules and hooks, and applying SOA principles to achieve modular, service‑oriented architectures that adapt to changing requirements.
This article explains how layered thinking guides architecture design, covering cloud three‑tier (IaaS‑PaaS‑SaaS) and SOA three‑tier models, the role of decomposition and integration, and practical layering patterns for technical, application, and functional architectures across various domains.
This article presents a comprehensive SOA service‑architecture planning methodology—from end‑to‑end business process analysis and data‑architecture design to technical platform assessment, integration mapping, service‑catalog creation, and practical case study—showing how to identify, refine, and organize reusable services in a micro‑services and mid‑platform environment.
This article explains the distinctions between SOA and microservice architectures, describes ESB and API gateway roles, outlines the characteristics of both architectures, and provides practical Dubbo service design guidelines such as packaging, granularity, versioning, and pre‑release environment configuration.
The article explains the purpose and structure of application communication diagrams, describes SOA‑oriented component layering, outlines the UML/BPMN EAP profile and Archimate concepts, and provides a detailed list of component types used in enterprise architecture modeling.
The article explains the concept of business services within the TOGAF 9.1 metamodel, compares it to SOA and ArchiMate definitions, demonstrates how to identify services from business processes using real insurance and banking examples, and discusses how these services relate to IS, SOA, and ITIL service models.
This article explains middleware fundamentals, its evolution in distributed systems, classifies its major types, analyzes global and Chinese market growth, and profiles key domestic vendors such as Dongfangtong, Baoland, Puyuan, Kingdee, Zhongchuang, Alibaba, and Tencent.
This article explains the principles, advantages, and step-by-step process of component-based development, covering business modeling, software requirements, system and technical design, implementation, and integration within modern microservice and SOA architectures.
This article explains the concept of microservices, contrasts it with monolithic architecture, outlines the drawbacks of monoliths, describes the advantages of microservice architectures, and briefly compares microservices with SOA, while also promoting a Java interview question resource.
The article examines modern application architecture trends, emphasizing service‑oriented and microservice approaches, the need to move beyond three‑tier designs, and adopting patterns, models, and structures that accommodate cloud, mobile, social, and big‑data influences.
This article explains the fundamentals of microservice architecture, contrasts it with traditional three‑layer monolithic designs, outlines its characteristics, benefits, drawbacks, and implementation challenges, and compares it to SOA, providing a comprehensive overview for developers and architects.
This article explains the essence, purpose, and value of service‑oriented architecture, compares it with layered, microservice, and distributed architectures, defines services and their components, outlines design principles, granularity decisions, service roles, and provides a practical roadmap for successful service‑centric system design.
The article examines the architectural differences between microservices and Service‑Oriented Architecture, covering component sharing, service orchestration versus choreography, middleware roles, API layers, and remote service access, highlighting how each style impacts coupling, performance, and deployment complexity.
This article explains the conceptual differences between SOA and microservice architectures, compares ESB with API gateways, outlines the characteristics of each approach, and provides practical guidelines for designing and managing Dubbo services in a distributed backend system.
This article traces the evolution of enterprise distributed application architectures—from early SOA through microservices to modern cloud‑native and service‑mesh designs—explaining the underlying complexity challenges, architectural principles, and the trade‑offs that shape today’s agile IT systems.
This article explains the concept of microservices, contrasts them with SOA, outlines their architectural advantages, and describes how Spring Boot and Spring Cloud work together to implement microservice solutions, detailing core components and request flow within a cloud‑native backend system.
This article explains the essential considerations for creating overall and application‑level architecture diagrams, covering layered structures, SOA‑based service layers, distinctions between business and technical views, and practical tips for visualizing enterprise, IoT, and single‑system architectures.
When creating software or solution architecture diagrams, it is essential to consider layered structures, platform and service distinctions, SOA principles, and the separation of application and technical views to effectively communicate enterprise‑wide or single‑system designs.
This article traces the evolution of software architecture—from monolithic applications through vertical and SOA designs to modern microservices—detailing each style’s characteristics, advantages, and drawbacks to help developers understand when and why to adopt each approach.
Over four years, MuleSoft’s website transitioned from a tightly‑coupled monolithic system to a coarse‑grained SOA with an ESB, and finally to fine‑grained microservices deployed on cloud platforms, highlighting the benefits, challenges, and practical considerations of each architectural style.
This article explains how adopting microservices, appropriate architectural patterns, and DevOps practices—ranging from monolithic to cloud‑native designs—can reduce costs, improve scalability, and support rapid development across web, mobile, and IoT platforms, while highlighting key differences between SOA and microservices.
This article explains the concept of microservices, compares it with SOA, outlines common business drivers such as agility, customer experience and cost reduction, shares real‑world implementation examples, and provides a detailed list of mistakes to avoid along with practical recommendations for successful adoption.
This article presents a DNS‑based universal addressing solution that enables traditional SOA applications using interfaces such as Dubbo, HSF, and SOFA to run on a Service Mesh without code changes, by mapping interface names to Kubernetes ClusterIP through CoreDNS and leveraging Istio’s routing mechanisms.
This article examines the shortcomings of decentralized and micro‑service‑only approaches for enterprise integration, argues for version‑less services, explains how a centralized ESB and multi‑center architecture can balance security, efficiency, and scalability, and outlines practical design patterns and component roles.
This article clarifies the core distinctions between Service‑Oriented Architecture (SOA) and microservices, covering their origins, communication models, bounded contexts, scalability, and suitable use‑cases, helping developers decide which architectural style best fits their application’s size, complexity, and deployment needs.
The article traces the evolution from early Service‑Oriented Architecture and monolithic applications to modern microservice architectures, highlighting their limitations, the rise of containers and Docker, and how these technologies enable scalable, language‑agnostic, and cloud‑native deployments for complex systems such as e‑commerce platforms.
This article explains the evolution from a single‑system e‑commerce application to vertically split and SOA‑based distributed architectures, demonstrates how to expose and consume services using Dubbo with complete Java interface and implementation code, and provides configuration, deployment, and testing guidance for both providers and consumers.
This article explains the evolution and core concepts of mainstream distributed architectures—including SOA, microservices, and service mesh—covers fundamental consistency theories such as CAP and BASE, and outlines practical high‑availability and scalability techniques for building resilient cloud‑native systems.
This article explores the evolution from Service‑Oriented Architecture to microservices, explaining why microservices succeed, how they differ from traditional monolithic designs, and the practical considerations for adopting them in large‑scale systems.
This article explores the evolution and core concepts of modern distributed architectures—including SOA, microservices, and service mesh—explains key theories such as CAP and BASE, and provides practical guidelines for achieving high availability, scalability, and efficient content delivery through techniques like load balancing, CDN, and gray‑release strategies.
This article explores software architecture fundamentals, covering object‑oriented design principles, SOLID, DRY, KISS, logical vs. physical layers, service and business logic layers, SOA, data access strategies, stored procedures, and the MVC pattern, providing practical insights for building maintainable systems.
This article walks through a practical transformation of an old payment architecture into a high‑availability microservice ecosystem, covering SOA vs. microservices, DDD‑guided domain boundaries, Dubbo‑based implementation, operational challenges, continuous integration testing, and future plans for multi‑active data centers.
This article walks through the evolution from traditional three‑layer monolithic architecture to microservice architecture, explaining system design concepts, the drawbacks of monoliths, the benefits and challenges of microservices, and compares them with SOA, providing clear diagrams, pros and cons, and practical insights for backend engineers.
This article outlines the historical evolution of application architecture—from early vertical monolithic designs through RPC and SOA approaches to modern microservice architectures—highlighting their characteristics, deployment models, and the motivations behind each transition.
This article explains the concepts of vertical (monolithic) and horizontal (distributed) architectures, compares onion, SOA, and microservice models, describes typical frameworks for data access, MVC, IoC, and service governance, and provides guidance on choosing the appropriate architecture for different project sizes and teams.
This article explores Ctrip’s continuously evolving architecture, detailing its three-layer composition of operations, frameworks, and applications, and examines real-world case studies of its release system, configuration management, SOA, and a massive User Profile big‑data project, highlighting key innovations and lessons learned.
This article defines microservices, SOA, and APIs, examines their differing viewpoints and integration challenges, and proposes a combined architectural perspective that highlights how microservices can evolve from or complement traditional SOA implementations.
This article explains the fundamentals of Service‑Oriented Architecture, defines services and their essential characteristics, discusses common challenges such as consistency and security, and details bus‑based designs including broker and message‑bus patterns with practical examples.
This article explains the layered server‑side architecture model, the role of each layer, the MVC pattern and its communication flows, Maven‑based project modularization, and an overview of Service‑Oriented Architecture, providing a practical guide for designing flexible backend systems.
Enterprise Service Bus (ESB) serves as the core architecture for SOA systems, centralizing service management and facilitating loosely‑coupled, flexible integration across heterogeneous supply‑chain partners, thereby meeting rapid response requirements through standardized data exchange, adaptable adapters, and scalable, maintainable processes.
Enterprise information systems increasingly rely on integrating business processes, and this article proposes a novel approach that combines Service‑Oriented Architecture with Message‑Oriented Middleware, delivering a three‑tier MOM framework that enhances efficiency, reusability, cross‑platform support, and flexible configuration for seamless business workflow integration.
Service‑Oriented Architecture (SOA) is a loosely‑coupled, coarse‑grained architectural model that enables distributed deployment and reuse of services through standardized interfaces, offering benefits such as external accessibility, high availability, scalability, and easier maintenance, while emphasizing service contracts, message patterns, and design management.
This article outlines a comprehensive enterprise SOA strategy, detailing the design of an ESB with core functions, component architecture, and a product development platform that enables modular, reusable business components across systems.
This article explains the appropriate use cases for the Factory pattern, details the responsibilities and characteristics of the application layer in SOA systems, and provides concrete C# code examples for services, DTOs, and data assemblers to illustrate clean separation of concerns and effective data transfer.
This article explores the definitions of SOA and DDD, explains DDD's layered architecture, demonstrates how business relationships become domain models, and provides concrete C# examples of repositories, services, and factories to illustrate the integration of service‑oriented architecture with domain‑driven design.
This article outlines Ctrip’s evolving architecture—covering its operational backbone, framework components, release system, configuration management, SOA evolution, and the massive UserProfile big‑data platform—offering practical insights from a senior developer on how the company achieves high availability and scalability.
This article explains how microservices evolved from SOA as a fine‑grained implementation, compares their concepts, benefits, and drawbacks, and provides practical guidance for choosing architectures, communication protocols, and frameworks—especially in Java‑based systems.