Master Software Architecture: From Simplicity to Complexity
summary
Claims a practical roadmap: start with four steps of evolution (simplicity → maintainability → growth → complexity), use workshops like event storming and domain storytelling, and map boundaries with the bounded context canvas. Uses concrete tactics: logical DB schemas, inbox/outbox, feature flags, blue/green deployments; numbers include 3–5 clinics and ~1,000 users initially, later half of the European market and a 15% revenue infrastructure cost. Warns of pitfalls—more services than 1,500 users, logging bills exceeding compute, and a 3‑week firmware audit that blocks continuous deployment.
AI-written summary · about
chapters (18)
- 0:00Intro
- 3:25An example
- 4:33Cognitive shortcuts
- 7:20Context is king
- 9:44First listen, then talk
- 12:29How to minimize risk?
- 19:24Recognize the environment around you
- 25:14Deployment strategy
- 26:56Release strategy
- 29:18Solution architecture
- 32:004 steps of evolution
- 32:261. Simplicity
- 36:082. Maintainability
- 38:123. Growth
- 40:124. Complexity
- 42:15Recap
- 43:40Lessons from the trenches
- 45:39Outro
related talks
40mArchitecture Modernization: Aligning Software, Strategy, and Structure
48mMinimum Viable Architecture
48mBuilding Evolutionary Architectures: Principles & Practices
50mTowards an Evolutionary Architecture
24mBuilding Software Architecture from First Principles
40mFrom Domain Boundaries to Software Architecture
40mPractices from trenches for embracing evolutionary architecture in wild
53mKeynote - Software Architecture, Team Topologies and Complexity Science