Building Evolutionary Architectures: Principles and Practices
summary
Defines an evolutionary architecture as one that supports guided incremental change by encoding measurable fitness functions such as latency uptime or cyclomatic complexity and enforcing them with runtime probes like Netflix Simian Army or a zero day-triggered build breaker. Recommends concrete practices: database refactorings from Refactoring Databases, contract testing between teams, favoring choreography when evolvability matters, and adopting continuous delivery so experiments deploy and roll back safely. Shows how to pick a first dimension to measure and evolve.
AI-written summary · about
chapters (12)
- 0:00Introduction to evolutionary architectures
- 3:00Defining evolutionary architecture
- 9:45Incremental change principles
- 12:15Decision timing and reversibility
- 17:33Team structure and Conway's law
- 18:18Refactoring databases techniques
- 20:06Orchestration vs choreography
- 21:32Contract testing for teams
- 22:57Continuous delivery necessity
- 25:51Culture of experimentation
- 27:13Evolving legacy architectures
- 31:02Q&A session
related talks
33mBuilding Evolutionary Architectures
53mEvolutionary Architecture: Principles and Patterns
35mPrinciples of Evolutionary Architecture
49mThe Principles of Evolutionary Architecture
39mHow will Evolutionary Architecture evolve?
01h 00mEvolutionary Architectures
01h 03mEvolutionary Software Architectures
42mBuilding Evolutionary Architectures