Building Evolutionary Architectures
summary
Claims that an evolutionary architecture “supports incremental guided change” and treats change as a first principle, backed by practices: continuous delivery and DevOps to reduce cycle time (Accelerate metrics); automated fitness functions such as JDepend-style dependency tests and continuously running resilience checks like Chaos Monkey; architecture styles compared (big ball of mud, layered, microkernel, microservices) with tradeoffs; Netflix’s resilience during the S3 outage as a concrete payoff of these practices.
AI-written summary · about
chapters (8)
- 0:00Introduction to evolutionary architectures
- 3:55Domain change and business evolution
- 7:23Continuous delivery and DevOps culture
- 12:57Fitness functions for guided change
- 20:05Technical vs domain change dimensions
- 27:30Organizational design and principles
- 30:17When to use evolutionary architecture
- 32:02Conclusion and Q&A
related talks
42mBuilding Evolutionary Architectures: Principles and Practices
48mBuilding Evolutionary Architectures: Principles & Practices
53mEvolutionary Architecture: Principles and Patterns
35mPrinciples of Evolutionary Architecture
01h 00mEvolutionary Architectures
49mThe Principles of Evolutionary Architecture
01h 03mEvolutionary Software Architectures
39mHow will Evolutionary Architecture evolve?