Decoding Complexity:[...]
summary
Argues that the difference between a tangled “hairball” of APIs and a sustainable enterprise architecture is concrete: unmanaged API sprawl creates technical debt that blows maintenance from a $1M project to 5–6× the cost, while a TOGAF-based program using TOGAF v10, ArchiMate models and a canonical digital repository lets teams map business strategy to apps and tech, enforce architecture contracts, pay down debt incrementally, and reduce impact-analysis time from months to minutes.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 4:17Enterprise architecture debt perspectives
- 12:27Non-standardized IT frameworks
- 15:39Enterprise architecture definition
- 22:14TOGAF preliminary phase
- 26:29ArchiMate modeling
- 30:20Architecture contracts governance
- 31:45Prudent EA approach
related talks
37mThe Dark Gods of Enterprise Architecture. To Warp and Back
50mThe Unbearable Weight of Architecture
41mArchitecture decision making
38mAgile Architecture
46mManaging architectural debt in a hypergrowth context
26mMastering API Strategies for Digital Transformation
49mGetting a handle on software architecture
25mAPIs and Complexity