What is enterprise architecture?
Enterprise architecture (EA) is a structured way to describe how an organization works: its goals, processes, systems, data, and technology. Rather than a one-time diagram, EA is a living map that helps leaders align investments, reduce duplication, and make tradeoffs visible before they become expensive rework.
The four architecture domains
Most EA frameworks organize work into four domains. Business architecture captures capabilities, value streams, and organizational structure. Application architecture describes software and how it supports the business. Data architecture defines what information exists, where it flows, and how it is governed. Technology architecture covers infrastructure, platforms, and integration patterns. Together they answer: what we do, what runs it, what we know, and what it runs on.
Where data architecture fits
Data architecture sits between business intent and technical execution. It translates business concepts (customers, products, transactions) into consistent definitions, models, and flows that applications and analytics can rely on. When data architecture is weak, every team defines 'customer' differently; when it is strong, the organization shares a common language from strategy through implementation.
Connection to data governance
Governance gives data architecture teeth: Policy sets the rules, Standard defines how to apply them, and operating models assign accountability. Architecture shows what should exist; governance ensures it is maintained, measured, and improved. Neither works well alone: architecture without governance drifts, and governance without architecture becomes paperwork.
What good looks like
Mature organizations treat EA and data architecture as decision-support tools, not shelfware. Domain models stay current, Data lineage is traceable, and changes go through lightweight review. Teams can answer where critical data lives, who owns it, and how Data quality is measured without a six-week investigation.
