Tell me why - About the purpose of architectural work
summary
Architectural work aims to minimize cumulative costs over a system’s lifetime while guaranteeing runtime correctness (examples: 99 requests <300ms, 99.9% availability), not just optimize immediate development effort. It separates quality attributes into development (changeability, maintainability) and runtime (performance, availability), and uses standards like ISO 25010/9126 as vocab. Choosing Kafka over a relational queue illustrates the tradeoff: saving ~3.5 days of dev can add ~$500k/year in ops and staffing. Good architecture must reduce cognitive load for builders and improve people’s lives.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 1:58Why ask why in architecture
- 5:52Optimization problem over time
- 14:47Minimize cumulative costs
- 19:19Reduce cognitive load
- 24:12Architecture for humanity
- 27:43Three perspectives summary
- 28:04Q&A session
related talks
56mEssential Architectural Thinking – Why, What, How, When and How Much?
25mThinking Architecturally
58mThe past, present and future of Architecture
44mDeliberate Architecture
46mPractical (a.k.a. Actually Useful) Architecture
07mWhat is Architecture, and Why It Matters
58mEffective Architecture Practices Debate
41mArchitectural Thinking