Keynote The Evolution of Evolutionary Architecture
summary
History of architecture traces concrete shifts: emergent design plus refactoring and tests let teams safely change object hierarchies (example: two pairs rewrote top-level relationships across a 750,000‑line codebase in one week); database refactoring breaks migrations into small, testable steps; continuous integration and continuous delivery pipelines with infrastructure as code automate deploys and rehearsed migrations; microservices follow when coupling and throughput needs dictate; claim: evolvability becomes a first‑class quality alongside security and reliability.
AI-written summary · about
chapters (18)
- 0:00Introduction and keynote opening
- 1:05Defining architecture
- 3:16What is evolutionary architecture
- 4:17Early computing and coupling
- 6:44Changing architectural principles
- 7:47Agile manifesto and team empowerment
- 10:15Emergent design and refactoring
- 13:04Patterns in architecture
- 15:52Agile expansion across roles
- 16:56Database refactoring challenges
- 19:03Data migration patterns
- 21:30NoSQL and database evolution
- 21:52Service-oriented architectures
- 24:24Continuous delivery fundamentals
- 27:56Automation and infrastructure as code
- 30:47Why architecture matters now
- 32:13Changing user expectations
- 34:47Evolvability as architectural quality
related talks
14mThe Evolution of Evolutionary Architecture
35mPrinciples of Evolutionary Architecture
49mThe Principles of Evolutionary Architecture
39mHow will Evolutionary Architecture evolve?
42mBuilding Evolutionary Architectures: Principles and Practices
01h 00mEvolutionary Architectures
53mEvolutionary Architecture: Principles and Patterns
33mBuilding Evolutionary Architectures