Principles of Evolutionary Architecture
summary
Claim: architecture must be judged by a concrete fitness function (security, performance, etc.) and decisions delayed to the last responsible moment. Techniques demonstrated include database refactoring triples (small data change, code change, migration), automated continuous delivery pipelines, and contract testing to let teams evolve independently. Surprising example: an underwriting model with 87 parameters breaks online quoting and forces urgent redesign. Emphasis on measuring complexity over time, prioritizing cleanup where code changes frequently, and making key decisions reversible.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:56Agenda
- 1:41Why Should I Care? Expectations for pace of change are increasing rapidly
- 4:43Design and Architecture
- 10:16Principles of Evolutionary Architecture
- 11:43Last Responsible Moment Delay decisions as long as you can, but
- 15:06Architect for Evolvability
- 18:34Develop for Evolvability
- 23:17Postel's Law
- 25:52Architect for Testability Aiming towards testability produces a well-architected system
- 29:01Conway's Law
- 30:42Techniques
- 31:54Continuous Delivery Automate environments and configurations
- 33:39Choreography
- 35:10Contract Testing Acceptance tests at the systems' interface
- 37:07Evolutionary Architecture Define your architectural fitness function
related talks
49mThe Principles of Evolutionary Architecture
35mPrinciples of Evolutionary Architecture
53mEvolutionary Architecture: Principles and Patterns
42mBuilding Evolutionary Architectures: Principles and Practices
39mHow will Evolutionary Architecture evolve?
01h 00mEvolutionary Architectures
01h 03mEvolutionary Software Architectures
56mTowards an Evolutionary Architecture