The Unbearable Weight of Architecture
summary
Argues that architecture’s harm is measurable: over‑uniform tech choices (serverless, Cosmos DB, “everything a microservice”) create sprawling surface area that outpaces teams, forcing half‑decade refactors in real systems. Shows a case of a credit‑card platform born from that mistake, cites Monzo’s ~2,800 services as a caution, and prescribes concrete tools: trade‑off lists (ATAM style), fault boundaries instead of blind decomposition, evolutionary design, prototyping HTTP APIs, and Barry O’Reilly’s residuality theory to stress‑test designs.
AI-written summary · about
chapters (13)
- 0:00🚀 Build Stuff Conference – Get Your Tickets!
- 0:35Introduction: The Weight of Systems & Real-World Experience
- 3:10Why Humans Struggle with Scale & Complexity
- 6:40Complexity vs Size: What Really Makes Software Hard
- 10:20The Problem with Modern Architecture (Microservices & Uniformity)
- 15:30Case Study: When Architecture Goes Wrong at Scale
- 19:40Surface Area vs Depth: What Engineers Actually Feel
- 23:10Rethinking Architecture: Design as Continuous Practice
- 27:00Trade-offs in System Design (Cost, Latency, Consistency)
- 30:20Avoiding Over-Engineering & Premature Decomposition
- 34:10Fault Boundaries & When to Split Systems
- 37:20Evolutionary Architecture: Designing for Change
- 40:10Final Thoughts: Build Smaller, Simpler, Better Systems
related talks
50mThe Unbearable Weight of Architecture
44mDeliberate Architecture
58mThe past, present and future of Architecture
25mThinking Architecturally
48mIT Architecture : All your micro-services are wrong PERIOD!
51mSoftware Architecture for Humans!
48mArchitecture: The Stuff That's Hard to Change
08mLightning Talk: Breaking the Mold: Unveiling Anti-Architectural Patterns in...