0 views collected around this technical thread.
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 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 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 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.
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 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 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.
The article explains layered architecture thinking, covering cloud three‑tier models, SOA layering, classic three‑layer application design, domain‑driven refinements, and practical guidance on constructing clear, maintainable system diagrams without mixing incompatible modeling approaches.
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.