Towards an Evolutionary Architecture
summary
Argues that architecture must evolve across early sprints rather than be fixed up front, recommending vertical slices and prioritizing backlog items by business value plus architectural impact. Advocates continuous refactoring, small surface areas via adapters, and treating frameworks as costly; gives a concrete workflow: prototype on sqlite3 prototype for months, keep automated tests, then swap to the production DB with three failing tests fixed. Pushes last responsible moment decisions, YAGNI, parsimony, triangulation, and warns that microservices are often far more complex than a monolith.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:55What is Architecture
- 6:04The Risk
- 11:19User Stories
- 15:47Risk Mitigation
- 17:29Prioritization
- 20:52Keep it Simple
- 24:35Refactoring
- 28:00Reversibility
- 28:48Programming Languages
- 30:55Libraries
- 32:33Last Responsible Moment
- 35:31Agility
- 36:51Agni Principle
- 39:03Parsimony
- 44:22Reuse
related talks
56mTowards an Evolutionary Architecture
01h 03mEvolutionary Software Architectures
39mPrinciples of Evolutionary Architecture
58mThe past, present and future of Architecture
01h 00mEvolutionary Architectures
48mBuilding Evolutionary Architectures: Principles & Practices
49mThe Principles of Evolutionary Architecture
35mPrinciples of Evolutionary Architecture