Fundamentals of Enterprise Architecture
Authors: Tanu McCabe
Publisher: O'Reilly Media
Length: 2024
A contemporary view of enterprise architecture: why it exists, which roles and operating models work, and how architectural decisions connect strategy to corporate delivery.
OriginalBrief
The essential idea
Tanu McCabe's Fundamentals of Enterprise Architecture presents enterprise architecture as a practical way to connect business goals, technology strategy, and delivery. Its purpose is to reduce organizational silos, manage complexity as a company grows, and keep technical debt from blocking new business initiatives.
The EA function combines strategy, enablement, and oversight. Enterprise, solution, and software architects work at different scopes and draw on specialists in security, networking, cloud, SRE, data, compliance, privacy, and observability. Organizations can centralize this function, federate it across domains, or use a hybrid model with a small standards-setting core and distributed architects.
Useful outputs include decision records, reusable architecture patterns, capability target architectures, and application target architectures. The recurring failure mode is architecture that produces documents and approvals but does not affect ownership, roadmaps, lead time, reliability, or portfolio control.
Decision lens
Key takeaways
Enterprise architecture should translate business goals and constraints into technology choices and delivery mechanisms.
Strategy, enablement, and oversight are complementary functions, not interchangeable job titles.
Enterprise, solution, and software architects operate at different scopes and need explicit interfaces.
Centralized, federated, and hybrid operating models should be chosen for organizational context rather than copied as doctrine.
ADRs and architecture patterns preserve decision context and make recurring choices easier to scale.
Security, data, SRE, privacy, and other specialist perspectives must participate in consequential decisions.
EA is valuable only when it improves delivery, reliability, debt management, or portfolio decisions.
Workplace experiment
Apply it at work
- 1
Write down the business outcome and non-negotiable constraints before debating technology for the next major initiative.
- 2
Clarify the decision rights and interfaces of enterprise, solution, and software architecture roles.
- 3
Adopt a small set of deliverables: ADRs, reusable patterns, and target-state plans with named owners.
- 4
Measure the EA function against delivery and reliability outcomes rather than document volume or approval count.
Choose one action, define the observable effect, and keep the first test small enough to reverse.
Evidence
Sources and further reading
Additional sources
Channel, aggregator, and commentary links confirm the work; they are not the primary source.