Evolutionary Architecture: Principles and Patterns
summary
Defines evolutionary architecture as supporting guided incremental change across multiple dimensions and prescribes using architectural fitness functions (automated checks) plus continuous delivery to govern change. Gives concrete examples: Netflix’s Simian Army and a license-check fitness function that hashes open‑source license files and emails legal on change. Advises waiting until the last responsible moment, favoring dumb pipes and smart endpoints, monitoring trends, and notes a trading-system anecdote where early designs expected ~100 transactions/day.
AI-written summary · about
chapters (14)
- 0:00Introduction to evolutionary architecture
- 3:35Definition and fitness functions
- 9:37Origins in agile and patterns
- 13:10Agile principles in architecture
- 17:42Key principles of evolutionary architecture
- 25:09Evolving governance models
- 31:55Legacy systems and remediation
- 39:51Outcomes over implementations
- 40:53Q&A: Architectural influence
- 44:05Q&A: Commercial software
- 45:27Q&A: Fitness function examples
- 47:32Q&A: Test coverage metrics
- 49:18Q&A: Junior architects
- 51:03Q&A: Resisting change
related talks
49mThe Principles of Evolutionary Architecture
35mPrinciples of Evolutionary Architecture
42mBuilding Evolutionary Architectures: Principles and Practices
39mHow will Evolutionary Architecture evolve?
33mBuilding Evolutionary Architectures
01h 00mEvolutionary Architectures
48mBuilding Evolutionary Architectures: Principles & Practices
01h 03mEvolutionary Software Architectures