Building Evolutionary Architectures
summary
Argues that evolvability is a measurable property enforced by executable checks called architectural fitness functions, not vague wishes. Shows concrete tools: JDepend/ArchUnit and NetArchTest for package and layering rules, Chaos Monkey/Simian Army for continuous checks, and GitHub’s Scientists experiment with 10 million comparisons over four days yielding 24 hours with zero mismatches. Gives concrete thresholds (cyclomatic complexity block at 50), a 66-item requirements spreadsheet turned fitness tests, and examples of automated enforcement that actually reject bad commits.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:52Evolvability
- 4:05Change
- 6:15Everything Changes
- 8:58Definitions
- 11:12Fitness Functions
- 14:23Multiple Dimensions
- 16:30Architecture Fitness Function
- 18:49Fitness Function Categories
- 24:43Atomic Fitness Functions
- 25:08ConsumerDriven Contracts
- 28:10Fitness Function
- 34:21ArcUnit
- 40:44Architecture Dimensions
- 41:53Incremental Change
- 43:57GitHub
- 44:39Scientists
- 46:46Questions
related talks
42mBuilding Evolutionary Architectures: Principles and Practices
01h 00mEvolutionary Architectures
33mBuilding Evolutionary Architectures
39mHow will Evolutionary Architecture evolve?
49mThe Principles of Evolutionary Architecture
53mEvolutionary Architecture: Principles and Patterns
59mAgile Engineering: The Hard Parts
39mPrinciples of Evolutionary Architecture