Evolutionary Architecture: The What. The Why. The How.
summary
Claims a four-step evolutionary path for architecture: start as a monolith for 3–5 clinics with ~1,500 patients and 100 staff, evolve code into modules with separate DB schemas and solution-structure tests, adopt inbox/outbox or simple in-memory queues or Postgres outbox for async, then add read replicas and only later cache. For growth (20 clinics → 10k patients; later 300 clinics → 100k patients with patient treatment generating 40% of traffic) the remedy is extracting hotspots into a separate deployable service that scales. Simplicity, Maintainability, Growth, Complexity modular monolith → patient-treatment microservice
AI-written summary · about
chapters (10)
- 0:00Evolutionary Architecture intro
- 3:12Software architecture challenges
- 6:02Four steps overview
- 8:34Healthcare domain case study
- 12:36Step 1: Simplicity
- 21:29Step 2: Maintainability & scaling
- 28:44Step 3: Microservices growth
- 33:01Step 4: Complexity handling
- 37:55Key principles & advice
- 38:59Q&A
related talks
50mTowards an Evolutionary Architecture
41mArchitecture aspects - evolutionary architecture development
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
35mPrinciples of Evolutionary Architecture
58mThe past, present and future of Architecture
39mMinimal Viable Architecture
01h 03mEvolutionary Software Architectures
44mHow Not to Die Trying to Evolve Your Architecture