This article explains the six key types of architecture—business, product, application, data, technical, and project—detailing their core components, purposes, and examples, and shows how they interrelate to form a complete system design framework for organizations.
This article explains the definitions, core components, purposes, and real‑world examples of six architecture layers—business, product, application, data, technical, and project—and shows how they interrelate to form a complete system design framework.
The article explains business architecture as a simplified enterprise blueprint, defines business and its components, outlines core elements such as value streams, capabilities, processes, objects, and organizational structure, and provides diagram examples to help readers apply these concepts in projects.
This guide presents a systematic, nine‑step architecture framework—covering business, product, and application layers—with concrete examples, step‑by‑step methods, comparison tables, and visual diagrams to help engineers design robust systems and ace architecture interview questions.
This article provides a comprehensive overview of Software‑as‑a‑Service, outlining its key advantages and disadvantages, detailing common pricing strategies such as free trials, per‑user, per‑feature, usage‑based and hybrid models, and describing typical SaaS front‑end, tenant, and admin modules.
The article explains how business architecture links models, capabilities, and processes to create value streams, stresses the need for scenario‑specific designs over generic ones, and offers practical methods—such as capability grading and risk‑driven effort allocation—to avoid blind decisions and improve resource efficiency.
Enterprise Architecture, essential for competitive advantage, is explored through TOGAF’s comprehensive framework and the 4A model, detailing business, application, technology, and data architectures, their purposes, design steps, and visualization techniques, offering practical guidance for building coherent, integrated enterprise blueprints.
This article explains the TOGAF framework and its 4A architecture model—Business, Technology, Application, and Data Architecture—detailing each domain's definition, purpose, value, and step‑by‑step guidance for creating enterprise architecture diagrams to align strategy, processes, and technology.
This article explains the 4A enterprise architecture model, compares it with TOGAF and Huawei’s “One Body Four Faces” framework, outlines the four architectural layers, and shows how Domain‑Driven Design can be mapped onto each layer with concrete examples and diagrams.
Reflecting on his 2023 technical writings, the author—prompted by the TV series 'Reply 1988'—structures his insights into chapters covering Domain‑Driven Design lessons illustrated by a Forrest Gump metaphor, business‑architecture note‑taking, judgment models drawn from everyday driving, and personal projects like the VSEF framework and the “曲径通幽” series, emphasizing curiosity, knowledge sharing, and continual growth.
This comprehensive guide explains the purpose of architecture diagrams, the criteria for good diagrams, the optimal moments to create them, and detailed methods for drawing business, application, technical, code, and data architecture diagrams, complete with design principles, classification, and practical tips.
This article explains enterprise architecture (EA), its main frameworks such as Zachman and TOGAF, the four architectural domains (business, application, data, technology), why organizations adopt EA, and provides an extensive EA glossary of terms and concepts.
This article explores architecture fundamentals, covering business architecture methodology, system architecture evolution from monolith to microservices, and technical strategies for reliability, scalability, performance, maintainability, security, and cost reduction, concluding with expression methods like the 4+1 view.
This article explains the core concepts of enterprise architecture, defines both enterprise and architecture, outlines major frameworks such as Zachman, TOGAF, DoDAF and FEA, distinguishes business and IT architecture, and details the components, models, and practical integration of business architecture with value streams, capabilities, information, organization, products, stakeholders, policies, and metrics.
This article presents a comprehensive business architecture design pattern that combines business and technical perspectives, guiding developers through value‑driven thinking, global vision, role and responsibility analysis, domain and process modeling, and both top‑down and bottom‑up design methods.
This article introduces the DuoliXiong local‑life service platform, analyzes the challenges of permission management across its multi‑layered architecture, and details the design of a flat RBAC model—including business‑line isolation, user, role, and permission tables, tree‑structured permission mapping, and data‑level access controls—to support scalable, secure operations.
This article explains what reference models are, outlines business, technical, and information reference model types, and provides practical guidance on representing them consistently using ArchiMate concepts within enterprise architecture to facilitate reuse, communication, and impact analysis.
This article explains the essential concepts of software architecture, distinguishing systems, subsystems, modules, components, frameworks, and architecture itself, and then details the various architectural layers—including business, application, data, code, technical, and deployment—while highlighting their purposes and design considerations.
This article explains the fundamental concepts of software architecture, distinguishing systems, subsystems, modules, components, and frameworks, and then details the various layers—business, application, data, code, technical, and deployment—while outlining the architect’s responsibilities and the criteria for when architecture design is needed.
This article outlines the iterative Enterprise Architecture (EA) process for building business architecture, detailing seven key steps—from definition and scope to migration planning and optimization—followed by an explanation of operating models and the five essential elements needed to create an effective operating model.
This article explains the concept of architecture, describes how business architecture shapes product architecture, outlines five key impacts on product design, and discusses modular and progressive design approaches for building scalable SaaS product architectures.
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.
This article explains the concepts of business and product architecture, outlines five ways business architecture impacts product design, and discusses modular and progressive design principles for building scalable SaaS product architectures.
This article explains the concept of architecture, outlines five ways business architecture influences product design, and details modular and progressive approaches for SaaS product architecture, including practical examples, MVP evolution, and strategies for scalable, flexible product development.
This article explains how business architecture influences SaaS product design through five major impacts—including system roles, operational processes, core value, surrounding systems, and billing models—while also outlining modular and progressive product architecture strategies for scalable development.
The article explains the rising importance of observability in modern operations, defines its control‑theory roots, breaks it down into metrics, traces and logs, and argues that successful implementation requires three pillars—SRE practices, AIOps algorithms, and deep business‑architecture knowledge—together with well‑designed SLOs and critical‑path mapping.
Observability is more than just combining metrics, traces, and logs; successful implementation requires the disciplined SRE methodology, AI‑driven AIOps capabilities, and a deep understanding of business architecture to define critical paths and layered SLOs for real‑world systems.
This article explains the fundamental concepts of software architecture, distinguishing system, subsystem, module, component, framework and architecture, and details various architectural layers such as business, application, data, code, technical, and deployment architectures, highlighting their purposes and relationships.
This article outlines the iterative seven‑step EA process for developing business architecture, details each phase from definition to migration planning, and explains how to design an effective operating model using five core elements such as leadership, governance, organization, capabilities, and services.
The article explains enterprise business architecture (EBA) as a bridge between business models and strategy, outlines what EBA is not, describes its four dimensions—people, finance, process, and organization—lists key influencing factors, and shows how EBA integrates with the broader enterprise context and business architecture.
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.
The Business Footprint Diagram illustrates the relationships among business goals, organizational units, functions, services, and the technical components that deliver them, providing clear traceability for stakeholders while also offering links to community resources and further architectural references.
This article shares practical hints on designing microservice‑based business architectures, covering problem definition, measurable goals, logical and process views, autonomy standards, real‑world case studies, and DevOps metrics to improve development speed and quality.
This article traces the history of the Chinese "mid‑platform" concept, outlines how major tech firms implement various middle‑platform strategies, distinguishes front‑end, back‑end, and middle layers, categorizes platform types, and highlights common pitfalls and organizational challenges in building such platforms.
This article introduces the growing discipline of business architecture, explains its role within enterprise architecture, outlines core domains and their relationships, and presents nine practical modeling techniques supported by BIZBOK and ArchiMate, while also noting available training resources.
This article presents a comprehensive Digital Transformation Framework (DTF) for asset‑management firms, detailing how to model economic, risk and financial impacts, redesign front‑, middle‑ and back‑office functions, adopt composable enterprise principles, and foster a digital culture to achieve sustainable competitive advantage.
This article explains how to abstract business functions into a middle platform through 0‑level and 1‑level modeling, defines domain capabilities and centers, outlines eight service design principles, and describes essential distributed mechanisms such as service registration, elastic scaling, rate limiting, gray release, messaging, and distributed transactions.
This article explores the challenges of business architecture, explaining how abstract design patterns can be concretized to create tangible value for enterprises, and presents visual diagrams that illustrate the core concepts and practical application of business architecture.
The article introduces the concept of business architecture, explaining how abstract architectural design must be grounded in concrete business needs, and discusses the difficulty of bridging design patterns with real‑world value creation, illustrated through a series of explanatory diagrams.
This article presents a series of visual diagrams that illustrate the concepts and structure of business architecture and capability modeling, offering a comprehensive overview for professionals seeking to align organizational processes with strategic goals.
This article clarifies the relationships among Business Architecture (BA), Data Architecture (DA), Application Architecture (AA) and Technology Architecture (TA), explains their roles within strategic, business, and solution layers, and walks through a concrete stock‑purchase example to illustrate end‑to‑end design and implementation.
This article explains business architecture as the bridge between business models and strategy, defines Enterprise Business Architecture (EBA), outlines its four dimensions—people, finance, process, and organization—examines key influencing factors, and describes how it fits within the broader enterprise architecture context.
The article explains business footprint diagrams, illustrating how business goals, organizational units, functions, and services map to technical components, providing traceability for C‑level stakeholders and highlighting their use in enterprise architecture modeling with UML/BPMN and ArchiMate references.
The article explains how implementing business and data middle platforms can enhance enterprise capabilities, streamline processes, foster innovation, and provide strategic advantages for leaders, managers, IT teams, and developers by centralizing standards, enabling data-driven decision‑making, and reducing operational costs.
This article explains how business architecture controls system complexity through layered structures and domain‑driven design, compares traditional three‑tier and microservice architectures, highlights common pitfalls, and offers a lightweight domain‑centric approach for scalable, maintainable backend systems.
This article examines the banking sector through an IT lens, outlining the industry's unique characteristics, business architecture, historical digital transformation, core system components, and key IT demand analyses to help professionals grasp the technical foundations of modern banks.
This article introduces the growing field of business architecture, its core domains, key modeling techniques, and how standards like BIZBOK® and ArchiMate 3.0 support strategic enterprise design and decision‑making.
This article outlines the iterative EA process for building business architecture, details each of the seven EBA development steps—from definition and scope to migration planning and optimization—and explains the five essential components of an effective operating model, providing practical guidance for enterprise architects.
This article explains enterprise architecture (EA) as a disciplined practice for analyzing, designing, planning, and implementing business and IT alignment, outlines major EA frameworks such as Zachman and TOGAF, describes the four architectural domains, and provides a comprehensive EA glossary.
This article explains the fundamental definition of software architecture, distinguishes related concepts such as system, subsystem, module, component, and framework, and outlines the various architectural layers—including business, application, data, code, technical, and deployment—while highlighting the architect's responsibilities and when architecture design is needed.
The article outlines Youzan's retail finance middle platform design, detailing the business background of complex SaaS retail, a structured analysis using layered business, application, data, and technology architectures, and a step‑by‑step implementation that emphasizes reusable domain capabilities and long‑term, standardized middle‑platform development.
The article explains what business architecture is, its evolution from monolithic to micro‑service and platform models, shares 58.com’s real‑world experience, discusses common difficulties, and offers practical guidance for architects on modeling, technology selection, and aligning with cloud and middle‑platform strategies.
This article explains why and how to isolate business lines and platforms, use product IDs for separation, create visual capability maps, employ mock data for issue reproduction, and implement monitoring to improve communication, efficiency, and rapid problem detection in large-scale systems.
The article explains what business architecture is, outlines its key characteristics, describes a four‑step method (systematic thinking, decomposition, abstraction, pattern), and demonstrates the approach with a detailed coupon‑service case study, illustrating how to model goals, processes, and elements into a clear architecture diagram.
This article outlines the development of enterprise business architecture—from early models like Zachman and TOGAF to modern frameworks such as FEA and DODAF—defines its purpose as a structured capability analysis that bridges business strategy and IT implementation, and explains its role in digital transformation and its interplay with various IT architecture layers.
This article explains Alibaba’s middle‑platform strategy, its evolution from a shared service model to a comprehensive business platform, and how it accelerates cross‑service integration, speeds up new‑business rollout, and supports the company’s broader “Five New” initiatives.
This article examines JD Pay's business architecture transformation, detailing the drivers behind the change, the challenges of large‑scale system migration, the new platform's architectural goals, implementation steps, and the measurable outcomes that improved stability, scalability, and data insight.
This guide explains how operations engineers can systematically map online business architecture, implement comprehensive multi‑dimensional monitoring, and create effective data dashboards to gain full visibility and quickly resolve issues.
This guide explains how operations engineers can systematically map business architecture, set up comprehensive multi‑dimensional monitoring, and consolidate monitoring data into dashboards to gain full visibility and quickly resolve issues in large‑scale online services.
