Deliberate Architecture
summary
Argues architecture should follow constraints and quality trade‑offs rather than fashion, citing microservices at peak and REST from Fielding as examples of styles with known behaviors. Notes biases (availability cascade, recency, hyperbolic discounting) and a developer half‑life 3.5 years that hides long‑term consequences. Highlights concrete trade‑offs: performance vs maintainability, security vs usability; finds "definition of done" and tickets fail for cross‑cutting qualities, so teams must monitor production, run architecture reviews, and look after quality attributes so features remain deliverable.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 3:02Fashion
- 4:41Layers
- 6:23Gartner Hype Cycle
- 8:23Software Architecture Styles
- 12:27Biases
- 17:40Incident Forces
- 18:43Resolving to Zero
- 19:27Qualities of the System
- 21:33Nonfunctional Requirements
- 22:21Features
- 26:23Emergence
- 27:59Nonlinear dynamical systems
- 28:34Be wary of emergent
- 28:59Accidental
- 29:40Agile
- 30:18Emergent
- 31:04Defects
- 32:36Deliberate
- 32:46Complexity
- 34:13Functionality
- 37:36Silver Bullet Solutions
- 37:58Building Architecture
- 38:49Building Qualities
- 39:34Monitoring
- 40:49Review
- 41:39Advice
related talks
59mDeliberate Architecture
58mThe past, present and future of Architecture
01h 14mDeliberate Architecture
37mArchitecting for Tomorrow: A Pragmatic Perspective
45mThe Unbearable Weight of Architecture
46mPractical (a.k.a. Actually Useful) Architecture
59mChoosing the Right Architecture Style Debate
25mThinking Architecturally