Architectural Thinking
summary
Defines three required skills: analyze trade-offs, map business drivers to quality attributes, and keep technical breadth plus depth. Uses concrete examples: wing‑vs‑tail engine tradeoffs, an auction with ~210 bids and three consumers choosing pub/sub vs point-to-point, shows coupling dropping from total=10 to total=0 by moving to topics/queues, contrasts coarse vs fine service granularity, cites gRPC: ~100ms → ~8ms latency gain at the cost of tight coupling, and recommends 20 minutes/day on InfoQ/ThoughtWorks to build breadth.
AI-written summary · about
chapters (17)
- 0:00Start
- 0:54Architectural Thinking
- 2:27Architecture Trade-Offs
- 4:34Wing Flutter
- 8:51Implement Architecture Extensibility
- 15:37Service Granularity
- 20:26Loose Coupling and Strong Cohesion
- 21:15Notification Service
- 21:37Inventory Service
- 27:31Data Consistency
- 27:41Transaction Management
- 29:18The Cart before the Horse
- 29:43Business Drivers
- 32:59User Satisfaction
- 34:15Budget and Time Constraints
- 35:37Gaining Technical Breadth
- 38:1320 Minute Rule
related talks
59mHow to Think Like an Architect
44mDeliberate Architecture
25mThinking Architecturally
43mThinking Architecturally
56mEssential Architectural Thinking – Why, What, How, When and How Much?
33mFrom Enterprise Architecture to Software Design - Critical Thinking
58mThe past, present and future of Architecture
46mPractical (a.k.a. Actually Useful) Architecture