Architecture aspects - evolutionary architecture development
summary
Starts with a working in-memory prototype and 23 checklist items, then adds small abstractions so business logic doesn’t change when persistence is implemented; chooses SQL Server after measuring data shape and growth; evolves from single-node vertical scaling to auto-scaling by time windows and multi-node horizontal scaling on Azure; solves history with event sourcing vs CRUD plus snapshots and read-models; fixes performance with a local+distributed cache with token invalidation and parallel requests — all decisions driven by measured feedback and incremental steps.
AI-written summary · about
chapters (13)
- 0:00Intro
- 2:22Evolutionary architecture
- 2:56Two principles
- 3:25Persistence
- 9:23Storage
- 10:41Event sourcing
- 16:37Distributed cache
- 19:16Layering
- 22:12Scaling
- 26:49Response times
- 28:39Parallel requests
- 30:29Conclusions
- 34:59Questions
related talks
50mTowards an Evolutionary Architecture
42mBuilding Evolutionary Architectures: Principles and Practices
56mTowards an Evolutionary Architecture
43mEvolutionary Architecture: How do you build systems that can evolve?
35mPrinciples of Evolutionary Architecture
01h 03mEvolutionary Software Architectures
49mThe Principles of Evolutionary Architecture
01h 25mCreating an Incremental Architecture for your System