How will Evolutionary Architecture evolve?
summary
Defines evolutionary architecture as guided incremental change and insists fitness functions (build failures, alerts) make nonfunctional goals objective. Recommends concrete practices: evolutionary database design (refactoring databases for safe migrations), contract testing to let teams work independently, choreography versus orchestration tradeoff (choreography raises evolvability but forces more error handling), and continuous delivery to make deployments boring. Reports early AI experiments (Copilot/ChatGPT) extract flows with mixed success and warns generated code can be millions of lines of garbage.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:13Evolutionary architecture defined
- 9:14Principles and practices
- 15:56Future changes
- 24:29Key practices
- 30:34Practices evolution
- 34:50Future of architecture
related talks
49mThe Principles of Evolutionary Architecture
35mPrinciples of Evolutionary Architecture
42mBuilding Evolutionary Architectures: Principles and Practices
53mEvolutionary Architecture: Principles and Patterns
01h 00mEvolutionary Architectures
33mBuilding Evolutionary Architectures
39mPrinciples of Evolutionary Architecture
14mThe Evolution of Evolutionary Architecture