Agile Architecture
summary
Presents a practical method that scores and composes architectural constraints to evolve systems incrementally instead of betting on upfront patterns, using weighted styles (loosely based on Mark Richards) and concrete tactics like DDD, CQRS, API strategies (REST/GraphQL/gRPC), CI/CD and automated governance. Claims microservices pay off only when teams, DevOps and data partitioning reach maturity, cites 136,000 deployments a day at Amazon versus 40 deployments a day at Shopify to show tradeoffs, and recommends starting with a modular monolith and measuring enough to add constraints later.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:03Misunderstanding agile
- 7:07What is architecture?
- 10:41Why architectures fail
- 16:18Good design vs overengineering
- 21:37Microservices reality check
- 27:22Constraints shape architecture
- 32:55Evolving layered monolith
- 40:21Domain-driven decomposition
- 47:28Measuring architectural fit
- 57:04Enough is enough
related talks
38mAgile Architecture
13mAgile Architecture: Enabling Innovation in a Rapidly Changing World
46mAgility and Architecture Together – Enabling a Fast Flow of Change
42mSoftware Architecture in the Age of Agility and DevOps
37mArchitecting for Tomorrow: A Pragmatic Perspective
51mWhy We Need Architects (and Architecture) on Agile Projects
48mAgility and Architecture Together – Enabling a Fast Flow of Change
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
