Organising and Governing Evolutionary Architectures (Fitness Functions)
summary
Explains how to govern evolutionary architectures by turning goals into measurable fitness functions and automating them. Shows Netflix’s Chaos Monkey/Simian Army running continuous chaos experiments in production to enforce resiliency, Java tools like ArchUnit and jdepend to fail builds on cyclic dependencies, simple pipeline checks that require a /status endpoint, GitHub CVE alerts for vulnerable libraries, and inspec scripts that verify only port 443 is open. Notes costs: tooling and training increase deployment overhead and slow early experimentation but catch cross-cutting failures at scale.
AI-written summary · about
chapters (9)
- 0:00Introduction to evolutionary architecture
- 1:13Gardening metaphor for software
- 3:39What is governance in software?
- 8:50Defining fitness functions
- 13:26Trade-offs in architecture decisions
- 17:43Fitness functions as guardrails
- 19:31Real-world fitness function examples
- 34:16Summary and key takeaways
- 34:58Q&A session
related talks
01h 00mEvolutionary Architectures
50mBuilding Evolutionary Architectures
53mEvolutionary Architecture: Principles and Patterns
59mAgile Engineering: The Hard Parts
33mBuilding Evolutionary Architectures
39mHow will Evolutionary Architecture evolve?
01h 03mEvolutionary Software Architectures
42mBuilding Evolutionary Architectures