The Unbearable Weight of Architecture
summary
Argues that software complexity comes from surface area over size and that architecture must contain breadth not byte counts, using a real credit‑card platform rebuilt after a half‑decade of brittle microservices/serverless/Cosmos DB decisions; cites Monzo’s ~1,500→2,800 services as a caution. Recommends splitting only for order‑of‑magnitude scale, distinct deployment/traffic or failure profiles, favoring modularization and clear fault boundaries, constant lightweight design cycles, named archetypes and trade‑off language, and the rule never put complexity in infrastructure.
AI-written summary · about
chapters (5)
- 0:00The philosophy of design
- 29:52Pitfalls of decomposition
- 35:11Managing system complexity
- 38:30Evolutionary architecture
- 44:41Mastery through form
related talks
45mThe Unbearable Weight of Architecture
01h 05mE-Commerce vs. Architecture!
58mThe past, present and future of Architecture
44mDeliberate Architecture
43mMonolith? Microservices? Who cares?
42mLarge-Scale Architecture: The Unreasonable Effectiveness of Simplicity
58mDon't Walk Away From Complexity, Run
48mIT Architecture : All your micro-services are wrong PERIOD!