The article examines why costly data middle platforms often become "data swamps," cites real‑world failures, and shows how Palantir's ontology‑driven three‑layer architecture (semantic, dynamics, decision) can transform read‑only data warehouses into automated decision engines delivering triple‑digit ROI.
The article outlines the evolution from isolated push modules to a unified framework and finally a dedicated push service, detailing functional and non‑functional requirements, component responsibilities, priority handling, and a scalable micro‑service architecture for enterprise notifications.
After mastering MCP for tool calling, Java back‑ends should shift focus to Agent‑to‑Agent (A2A) collaboration, where each service becomes an AI‑enabled business agent that describes its capabilities, coordinates tasks, and maintains auditability across complex enterprise workflows.
This article uses a single family‑tree diagram to explain the three generations of software architecture—enterprise, application, and domain‑specific architectures—detailing their layers, typical concerns, common tools, and the 4+1 view model for describing systems from multiple perspectives.
The article presents a production‑grade, six‑layer architecture for an AI assistant that unifies LangGraph state orchestration, industrial‑strength RAG pipelines, multi‑level memory management, and the Model Context Protocol (MCP), addressing integration fragmentation, fault tolerance, observability, and security to enable scalable enterprise deployments.
This article compiles over thirty detailed architecture diagrams covering Java class loaders, JVM, Spring, Hibernate, Android, Linux kernel, cloud computing, and various enterprise technologies, offering developers a visual reference library for understanding and designing Java backend systems.
The article explains how traditional data governance, which merely cleans and organizes files, fails to meet AI’s need for semantic understanding, and argues that adopting ontology‑based governance—building a “cognitive dictionary” of entities, relationships, and rules—enables machines to truly comprehend and reason over enterprise data.
The article analyzes how the shift to marketing digitalization forces traditional IT departments to move from peripheral support roles to strategic growth engines, detailing the three core challenges they face, the value‑redefinition framework, and three concrete pathways—including infrastructure, low‑code enablement, and data‑driven decision making—illustrated with real‑world case studies such as Dongpeng Energy Drink and Luzhou Laojiao.
The article explains how the hard‑coded, role‑bound permission model of traditional code‑issuing platforms collapses when an organization’s structure changes, and shows how a three‑layer decoupled architecture can provide fine‑grained, configurable access that turns the platform into true enterprise infrastructure.
The article analyzes costly data‑platform failures in large enterprises, contrasts traditional data middle‑platforms with Palantir’s ontology‑based approach, and explains a three‑layer architecture that turns raw data into automated business decisions, illustrated with real‑world case outcomes.
This article presents a practical framework for CTOs to evaluate three leading AI agents—Claude Code, Microsoft Copilot, and OpenClaw—across data sovereignty, ecosystem integration, cost structure, and team capability, and demonstrates the approach with a realistic fintech case study.
The talk outlines the AI+ era's digital ecosystem, traces the evolution from traditional AI to Agentic AI, examines emerging AI Agent technologies, and shares concrete enterprise‑level development practices, frameworks, and governance strategies for financial industry deployments.
This article shares a step‑by‑step framework for creating architecture planning PPTs that emphasize a clear logical backbone, slide‑level objectives, quantified business and technical value, unified terminology, strategic alignment, technical standards, gap analysis, and an implementation plan, helping leaders without domain expertise quickly grasp and trust the proposal.
This article demystifies the concept of architecture by tracing its origins, explaining the 4+1 and C4 modeling approaches, introducing TOGAF‑4A, and clarifying the role of enterprise architecture in aligning people, processes, technology, and data to manage complexity across large organizations.
This article explains the core differences between Enterprise Architecture and Solution Architecture, outlines how they complement each other, and provides practical governance methods to ensure effective collaboration and reduce technical debt.
In a landscape crowded with OLTP, OLAP, HTAP, NewSQL and cloud‑native options, this article explains why enterprises must look beyond performance and assess a database’s five‑dimensional long‑term service capability to ensure sustainable growth and low migration risk.
This article explains how enterprise architects can integrate ONNX‑based machine‑learning inference directly into Java applications, covering tokenizer integration, GPU acceleration, deployment patterns, and lifecycle management to achieve secure, scalable, and observable AI services without relying on Python runtimes.
This article provides a deep dive into the five major enterprise architecture methodologies—TOGAF, Zachman, OEA, ITSA, and DODAF—explaining their core principles, step‑by‑step implementation processes, a detailed omni‑channel order and marketing platform case study, and a comparative analysis to help architects choose the right framework for their projects.
This guide outlines a systematic enterprise architecture planning framework—from business capability mapping and digital maturity assessment to asset inventory, debt identification, technology selection, phased implementation, risk mitigation, and continuous governance—helping organizations align technology with business goals and accelerate successful digital transformation.
This article explains the definition of technical architecture, outlines its core components such as technical services, components, infrastructure and selection, and illustrates how it supports business, application, and data architectures through layered system diagrams and practical examples.
This article explains the definition of application architecture, distinguishes enterprise‑level and system‑level designs, outlines its core components—application services, structure, and interaction—and illustrates layered architectures and service interactions with diagrams, helping readers understand how to translate business architecture into concrete IT solutions.
This article explains the background, concept, suitable enterprises, involved departments, policies, processes, technical architecture, and common challenges of Financial Shared Service Centers (FSSC), offering a step‑by‑step roadmap for organizations seeking cost reduction, efficiency, and stronger financial control.
Over ten years, the author chronicles the evolution of data governance across finance, government, and manufacturing, highlighting early chaos, tool migrations from Excel to Apache Atlas, AI‑powered quality monitoring, strict compliance across jurisdictions, cross‑department collaboration challenges, and the shift toward autonomous, value‑driven data ecosystems.
This article explains data architecture, its purpose, historical development, major enterprise frameworks, various data management system types, and the key advantages it brings to organizations, helping readers understand how to design and implement effective data solutions in modern environments.
This article reflects on ten years of the Chinese tech industry's "mid‑platform" concept, explaining its origins, various definitions, practical benefits and pitfalls, criteria for adoption, and why it has become both a strategic asset and a buzzword in digital transformation.
The article shares a corporate‑bank architect’s experience of creating a bottom‑up, cross‑functional organization to overcome siloed responsibilities, detailing the challenges, the three‑step implementation framework, and practical templates for task management and agile enterprise architecture.
This article presents a comprehensive overview of NIO's company‑wide knowledge platform, detailing its background, layered architecture, retrieval‑augmented generation workflow, challenges such as accuracy, permission control and high concurrency, and future plans for AI‑assisted understanding, creation, multimodal capabilities, and expanded knowledge types.
This article presents a comprehensive visual guide to enterprise digital transformation, covering overall digital planning, application system architecture, data architecture, information security architecture, and digital organization and governance, illustrating each layer with detailed diagrams to aid strategic implementation.
This guide outlines a practical six‑step methodology—covering overall planning, data integration, model construction, data development, asset management, and data services—to help enterprises build a robust data middle platform that unlocks business value and supports agile digital transformation.
This article explains the concept of Single Sign‑On (SSO), outlines its implementation process—including user redirection, token generation, and cross‑system authentication—discusses challenges such as single point of failure, complexity, and cross‑domain issues, and highlights typical use cases in enterprise and e‑commerce environments.
This article outlines the background, overall framework, and platform construction of enterprise digital transformation, illustrating each component with detailed diagrams that guide organizations in planning and implementing comprehensive digital strategies to achieve competitive advantage.
Drawing from the book “Huawei Data Way”, this article explains why Huawei must digitize, describes the resulting data‑island problem, and outlines the four‑part framework of data governance—including data asset catalogs, standards, models, and distribution—while showing how business‑object‑centric information architecture is built and implemented.
This article details how Industrial and Commercial Bank of China (ICBC) created a cross‑channel, enterprise‑grade frontend component library and management platform to standardize UI design, boost development efficiency, and enhance user experience across mobile, PC, and smart‑terminal banking applications.
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 examines how cloud computing has become central to enterprise IT architecture, explores its cost governance challenges, outlines industry trends, standards like ITIL and COBIT, and presents practical strategies—including FinOps, multi‑cloud platforms, and sustainable practices—to effectively manage and reduce IT costs.
This article explores how cloud computing has become the core of enterprise IT, examines the debate over its cost‑saving potential, outlines the latest cloud trends, details IT cost‑governance frameworks such as ITIL, COBIT and FinOps, and provides practical technical and managerial strategies—including multi‑cloud scheduling, resource over‑commit, workload mixing, bin‑packing, and green data‑center practices—to achieve continuous cost control and value‑driven digital transformation.
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.
Enterprises facing fragmented systems like OA, HR, CRM, and ERP must adopt a unified master data management framework that defines standards, governance, organizational structures, and integrated platforms to ensure data consistency, accuracy, and real‑time availability, thereby reducing maintenance costs and supporting digital transformation.
The article explains what reference models are, outlines business, technical, and information reference model types, and provides guidance on how to represent these models consistently using the ArchiMate modeling language within enterprise architecture practice.
This article explains the origins and concepts of IT architecture and governance, compares traditional and internet‑era enterprise structures, reviews major standards such as COBIT, ITIL and IT4IT, outlines practical governance methods, and showcases JD.com’s concrete implementation across infrastructure, applications, and organizational processes.
The article presents a comprehensive Digital Transformation Framework (DTF) for asset‑management firms, detailing how financial, economic, risk, and technical dimensions intertwine, illustrating the composable‑enterprise model, middle‑office evolution, API‑centric automation, and the essential cultural shift required for successful digital change.
Data middle platforms transform raw enterprise data into reusable assets by integrating collection, storage, processing, governance, and service layers, enabling faster deployment, consistent metrics, improved data quality, and business value across digital transformation, while addressing challenges like siloed data, low efficiency, and inconsistent standards.
The article traces the rise and recent re‑configuration of the enterprise “middle platform” strategy—originally adopted to reduce redundancy, speed R&D, and improve stability—while highlighting its boundary, flexibility, and governance challenges, and advises firms to adopt or decentralize such platforms according to their growth stage and business complexity.
This article explains the role of application architecture within enterprise architecture, describes its focus on application behavior and data exchange, outlines strategic alignment and common architectural patterns, and details the responsibilities and knowledge areas of an application architect.
The article outlines the complete solution‑architecture lifecycle, describing each phase—from problem identification and context definition through requirements capture, backlog creation, detailed design, implementation choices, and production delivery—while emphasizing the architect’s role in aligning technical and business goals.
The article explains the distinct roles of software architects, enterprise architects, solution architects, and technical architects, outlining their responsibilities, focus areas, and how they differ in scope, technical depth, and alignment with business goals within an organization.
This article outlines a real‑world enterprise master data project, detailing the definition of master data, the four critical data‑quality challenges faced, the comprehensive solution framework with executive backing, and the six measurable outcomes that improved data governance, efficiency, and decision‑making across the organization.
In this presentation, Guo Wei, CEO of Baijiang Open Source and seasoned big‑data expert, explores how large‑model AI reshapes DataOps and DataFabric, detailing efficiency gains, intelligent deployment, and future enterprise architectures for big‑data and AI integration.
The article explains how enterprise architecture (EA) principles and design architecture principles (DAPs) should be defined, prioritized, and linked to business goals to guide technical standards, overcome resistance, and drive effective governance and behavioral change within organizations.
The article explains information governance as a business‑driven program that ensures data accuracy, completeness, consistency, accessibility, and security, outlines three essential roles, describes the data administrator’s duties, and details the key procedures and their relationship to corporate and IT governance.
This article explains business architecture as the bridge between business models and strategy, defines Enterprise Business Architecture (EBA), outlines its four key dimensions—people, finance, process, and organization—and discusses the various factors that influence its design and implementation.
The article presents a comprehensive, step‑by‑step methodology for designing, evaluating, and governing enterprise modernization and digital transformation initiatives, covering vision, strategy, current and future state analysis, requirements, feasibility, trade‑offs, decisions, models, design, specifications, and agile governance.
The article explains how strategy development and execution are interdependent, outlines why executives often prioritize execution, and demonstrates how Archimate 3.1's motivation layer can model strategic intent, capabilities, and feedback loops to bridge strategy with actionable enterprise architecture practices.
This article explains the three main types of roadmaps—technology, product, and capability—how they are created, their interdependencies, and why enterprise architecture should be involved to keep business and technology aligned with strategic goals.
This article outlines twelve essential lessons for successfully defining and implementing business capabilities, covering understanding use cases, stakeholder identification, process differences, continuous communication, strict guidance, reuse of inputs, recognizing concept drawbacks, long‑term expectations, pilot opportunities, expectation management, tool selection, and capability type awareness.
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 outlines the seven essential steps for establishing an effective data governance framework, covering the creation of a governance organization, identification of strategic master data, ownership assignment, rule definition, maintenance procedures, tooling, and archiving policies.
In a round‑table interview, former Alibaba executive Jia Yangqing, Yunqi CTO Guan Tao, and OtterTune co‑founder Zhang Bohan explore how databases, big data, and AI converge, the distinctions between “AI for Data” and “Data for AI,” and what enterprises need in an integrated AI‑enabled data platform.
The article explains the concept of software design patterns, their role in managing coupling and interfaces, and provides best‑practice guidelines for enterprise‑level service design, illustrating how MITRE system engineers should select and apply patterns to achieve loosely‑coupled, extensible systems.
This comprehensive guide clarifies the concept of software architecture, explores related notions such as systems, subsystems, modules, components, frameworks, and various architectural classifications, and outlines design goals, evolution paths, common pitfalls, and recommended reading for building effective, scalable, and maintainable systems.
The article explains business capability modeling as a universal language for aligning IT with strategy, detailing its definition, benefits for mergers, risk and innovation management, and a four‑step method to create a capability model that drives cost savings, risk reduction, and growth.
This article presents a comprehensive methodology for building an Onedata data warehouse, covering the conceptual framework, data modeling processes, the Inmon and Kimball approaches, practical case studies from Baidu, Huawei, and banking, and key takeaways for enterprise data architecture.
This article explores enterprise architecture as a practice of modeling and managing an organization’s structures, processes, systems, data, and product portfolios, emphasizing the importance of process models, model convergence, governance, and how APQC’s PCF and MosaiQ tools can streamline EA efforts.
The article forecasts rising enterprise application integration spending, outlines challenges of integrating cloud, mobile, social, and data services, and provides strategic steps—including budgeting, organizational agility, technology selection, and deployment models—to guide successful integration initiatives across on‑premise, cloud, and B2B environments.
This article explains the three main use cases of API gateways—Open API platforms, microservice gateways, and API service management platforms—describes their position in enterprise architecture, outlines practical deployment scenarios, compares competing solutions, and provides criteria for choosing the right gateway for performance, scalability, extensibility, and cloud deployment.
The 2022 Xinchuang whitepaper outlines a comprehensive enterprise‑architecture‑driven roadmap—including framework, development method, technical reference models, implementation and operation practices—to guide central state‑owned enterprises through digital transformation challenges and opportunities.
This article explains the concept of enterprise architecture by likening an organization to a massive software system, discusses its importance in digital transformation, outlines its meta‑model and view layers, and highlights why a structured architectural approach is essential for modern enterprises.
This article presents Dipu Technology's comprehensive data governance methodology, covering construction paths, a typical enterprise digital platform framework, core governance components, practical case studies, and a Q&A session that together illustrate how businesses can design, implement, and sustain effective data governance across the organization.
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.
The article explains the purpose, stakeholders, concerns, scope, and key elements of the Organization View and Business Process Collaboration View in ArchiMate, illustrating how these viewpoints model enterprise structures and business process dependencies for better design and decision‑making.
This guide introduces ArchiMate views, explains their role in modeling enterprise architecture, outlines the 23 official example viewpoints grouped into basic, motivation, strategy, and implementation & migration categories, and provides detailed descriptions of basic viewpoints such as composition, support, collaboration, and implementation.
The article examines the relationship between enterprise architecture and systems engineering, discussing overlapping frameworks such as TOGAF, DoDAF, UPDM, and model‑based approaches, and argues that while they share terminology and goals, EA focuses on business transformation and IT alignment, whereas SE emphasizes technical system development.
The article explains how enterprise applications have evolved to web‑based distributed environments, describes the three‑tier architecture, and shows how UML/EAP and Archimate can be used to model and visualize the deployment of hardware and application components in a networked infrastructure.
The article explains how environment and location diagrams map applications to physical sites, defines key UML/BPMN EAP elements such as headquarters, site locations, servers, workstations, applications, interactive components, and class relationships, and illustrates these concepts with an Archimate diagram while also providing community links.
The article explains how to create data‑security diagrams that map which participants can access specific enterprise data, recommends breaking large diagrams into role‑based views, and illustrates the approach with UML/BPMN and ArchiMate models while addressing compliance and trust considerations.
The article explains the purpose and benefits of data publication diagrams for visualizing relationships among data entities, services, and application components, introduces UML/BPMN EAP profile components with illustrative images, and outlines Archimate modeling elements, highlighting how data is localized within repositories or entity application components.
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 how organization decomposition diagrams illustrate the links between participants, roles, and locations, define responsibilities, show information flows, and map goals to stakeholders using UML/BPMN and Archimate models, providing a comprehensive view of enterprise structure and governance.
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.
The article explains how business capabilities—derived from strategic plans and modeled as cross‑cutting EA concepts—provide a foundation for building enterprise‑architecture roadmaps, describing capability models, capability increments, dependencies, and their alignment with strategic, business, and IT change initiatives.
The article explains how the Scaled Agile Framework (SAFe) supports lean enterprises by integrating agile, lean, and DevOps principles, detailing its business benefits, core competencies, configurable options, and implementation guidance for organizations seeking rapid, sustainable delivery of high‑quality solutions.
This article examines how enterprise architecture has shifted from a technical oversight function to a strategic, cross‑disciplinary role that supports decision‑making, ensures reusability, accelerates development, and requires new skills and organizational changes to drive successful digital transformation.
The article humorously deconstructs an overly complex Java enterprise setup, illustrating how excessive use of interfaces, abstract classes, factories, dependency injection, XML configuration, and heavyweight IDE tooling leads to bloated, hard‑to‑maintain code that ultimately fails in production.
This article explains how Agile Architecture within the SAFe framework combines Lean‑Agile principles, intentional and emergent design, and continuous delivery practices to evolve system architecture over time, align it with business value, and support collaborative roles across enterprise, solution, and system architects.
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 provides a comprehensive overview of Enterprise Architecture (EA), covering its definitions, scope, key concepts, benefits, real‑world examples, relationships with other disciplines, major tooling options, and common criticisms, offering readers a solid foundation for understanding EA in modern organizations.
This article explains how enterprises can build a unified data storage and compute foundation, covering strategic goals, functional and architectural requirements, and the layered design of business support, storage‑compute, and resource management to enable scalable, secure, and high‑performance data platforms.
The article explains how ArchiSurance visualizes new digital‑customer‑intimacy capabilities, distinguishes business capabilities from functions, and shows how resources and architectural models can be aligned to support data‑driven insurance initiatives within an enterprise‑architecture framework.
This article outlines the essential requirements, architectural design, and five key capabilities of an enterprise‑level unified data platform, explaining how data integration, cloud‑native features, and layered design enable digital transformation and business innovation.
This document outlines a comprehensive big‑data platform construction plan for a financial enterprise, describing the current data challenges, objectives, three‑layer architecture, recommended commercial Hadoop solution (TDH), detailed model‑design steps, implementation schedule, hardware/software specifications, and key success factors.
This article systematically explores the challenges of microservice service splitting—from technical choices and architectural reliability to business model validation and team collaboration—offering static and dynamic solutions, design principles, and practical guidelines for effective service decomposition.
The article analyzes why software development teams often see productivity drop as headcount grows, explains communication‑cost theory, introduces a 5S model covering design, development, testing, management and support stages, and recommends enterprise architecture and domain‑driven design to curb complexity and boost delivery speed.
This article explores the evolution of enterprise technical architecture—from single‑instance monoliths through distributed and microservice designs to modern cloud‑native platforms—detailing definitions, classifications, a real‑world case study, and the stability, efficiency, and process challenges faced along the way.
This article explains what data architecture is, why it is essential for linking business and technology, outlines its main components such as data models, data flows, value streams and standards, and discusses emerging trends toward service‑oriented, consumption‑focused data architectures.
This article explains the TOGAF enterprise architecture framework, its evolution to version 10 with a modular agile‑focused structure, the core and extended guidance it provides, the business benefits and certification paths, salary impact, and a list of certified tools for implementation.
Enterprise Information Security Architecture (EISA) provides a structured framework that links business drivers with technical guidance through three perspectives—business, information, and technology—detailing its documentation layers, strategic approaches, and the integration of security into overall enterprise architecture to enable effective, iterative security programs.
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.
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.
The article presents a comprehensive overview of Dongfang Securities' enterprise business middle platform, detailing its background, definition, construction principles, user journey, overall architecture, domain‑driven design, technical stack, service governance, PaaS, multi‑active deployment, R&D management, data governance, and the practical outcomes achieved through this cloud‑native transformation.
The article explains how enterprise architects drive digital transformation, outlines the dynamic responsibilities and required hard and soft skills for senior roles, and describes the path and strategic functions needed to advance to a chief enterprise architect position.
