Mastering the 4A Enterprise Architecture: From TOGAF to DDD Integration
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.
What Is the 4A Architecture?
The 4A architecture is a comprehensive enterprise‑architecture model that consists of four core elements—Business Architecture, Information (Data) Architecture, Application Architecture, and Technology Architecture. It helps organizations understand and manage the complexity of their business, data, applications, and technology to improve operational efficiency and competitiveness.
Core Components of the 4A Model
Business Architecture (BA) : Structured representation of business goals, value streams, capabilities, and processes. Key artifacts include strategic vision, AS‑IS and TO‑BE process maps, service blueprints, and product‑function panoramas.
Information Architecture (IA) / Data Architecture : Defines the structured set of information needed for business operations, focusing on core business objects (e.g., product, customer, contract) and their relationships. Important aspects are data‑model design, data governance, data services, data platforms, and data lakes.
Application Architecture (AA) : Identifies the IT systems that support business objectives, their positioning, and integration points. Emphasizes the choice of integration platforms, user‑experience layers, and the IT systems that enable digital transformation.
Technology Architecture (TA) : Describes the technology components, platforms, and infrastructure resources required to realize the application architecture. Includes technology selection, code‑layer design, PaaS platforms, cloud‑native technologies, DevOps practices, micro‑service design, and deployment topology.
TOGAF Overview
TOGAF (The Open Group Architecture Framework) is the most widely adopted enterprise‑architecture framework. Its metamodel aligns directly with the 4A model’s four domains—Business, Data, Application, and Technology.
Huawei’s “One Body Four Faces” Architecture
Huawei describes its enterprise architecture as “One Body Four Faces,” where the “one body” represents a unified framework driven by business goals, and the “four faces” correspond to Business, Information (Data), Application, and Technology architectures.
In Huawei’s terminology the “information architecture” is essentially what most frameworks call “data architecture.” In TOGAF, data and application architecture are merged into a single “information architecture.”
Key Points for Each Layer
Business Architecture: Project vision, value‑stream analysis, capability mapping, and identification of digital‑technology opportunities. Information Architecture: Data‑model design, governance, data services, data platforms, and data‑lake considerations. Application Architecture: Mapping business functions to applications, defining modules, components, and external IT system integrations. Technology Architecture: Selecting platforms, cloud‑native stacks, DevOps pipelines, micro‑service patterns, and deployment architectures based on the application layer.
Integrating Domain‑Driven Design (DDD) with the 4A Model
Business Architecture : DDD’s collaboration between domain experts and developers defines business requirements; business processes and capabilities map to bounded contexts and domain models.
Application Architecture : DDD’s bounded contexts and aggregates align with modular application design; services and interfaces are organized around these contexts.
Data Architecture : Domain entities become the basis for data models and relational schemas, ensuring data structures reflect core business concepts.
Technology Architecture : DDD’s layered architecture (application, domain, infrastructure) corresponds to technology‑stack decisions such as frameworks, communication protocols, and infrastructure services.
Practical Diagram Examples
The article provides typical diagram templates to help practitioners visualize each layer. Sample diagrams include a business panorama, an application‑architecture map, a data‑architecture diagram, and a technology‑architecture diagram.
Eric Tech Circle
Backend team lead & architect with 10+ years experience, full‑stack engineer, sharing insights and solo development practice.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
