Achieving an evolutionary architecture through simplicity
summary
A practical model maps solutions from concrete specific to abstract generic and recommends starting at bottom-right concrete specific solutions, adding features, then continuously refactoring back to simpler designs. Concrete tips: model behavior not large entity blobs, modularize into small high‑cohesion modules, prefer hard‑coding over premature configurability, apply a zero-bug policy, use rolling refactoring when migrating runtimes, and split and defer decisions so persistence, archiving and scaling choices are made after real usage data.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:56Three enablers
- 3:47Simplicity
- 8:18User Model
- 10:32Behavior vs Entities
- 13:16Modularization
- 15:15Flexibility
- 16:41rucksack principle
- 19:23Splitting decisions
- 21:51Persistence
- 27:03Architecture refactoring
- 33:10Features management
- 39:14Summary
related talks
56mTowards an Evolutionary Architecture
50mTowards an Evolutionary Architecture
49mThe Principles of Evolutionary Architecture
39mPrinciples of Evolutionary Architecture
57mSoftware Architecture: The Hard Parts
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
42mBuilding Evolutionary Architectures: Principles and Practices
40mEvolutionary Architecture - The art of making decisions