The Thorny Road of a Digital Design Tool
summary
A practitioner describes building a digital design tool for architecture and integration in a large organization, explaining why C4 models and simple API/contract descriptions were insufficient. The talk covers identifying missing descriptions of inter-system interactions and argues for more architectural layers and richer interaction modeling to document complex system behavior.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 4:27Enterprise architecture problems
- 6:34Core system modules
- 7:57Architecture layers concept
- 10:07Detailed architecture components
- 12:14Deployment architecture
- 15:28API repository role
- 17:13Alerts and notifications
- 18:15Universal search and learning
- 18:57API Gateway implementation
- 21:13Caching and performance
- 22:17Diagrams and visualization
- 24:02Digitalizing architectural standards
- 25:52Open Policy Agent validation
- 27:59Team and tech stack
- 29:02Clients and system scale
- 30:47Q&A
- 31:51Formats and scalability questions
- 34:43Versioning and trends questions
- 38:39Corporate data model questions
- 40:56Architecture process and review questions
- 43:46Notation and adoption questions
- 44:28System effectiveness metrics
- 45:33Time to Market and architecture
- 47:44Summary and answers
related talks
01h 00mVisualise, document and explore your software architecture
54mC4 models as code
57mVisualise, document and explore your software architecture
44mThe C4 Model – Misconceptions, Misuses & Mistakes
52mC4 Models as Code
30mBlending Product Thinking with Architecture
45mSW Design, Architecture & Clarity at Scale
34mPractical Tools and Strategies for Tackling Legacy Practices