~/talk

Agile Architecture

links:none on file
slides:none on file

Presents a practical method that scores and composes architectural constraints to evolve systems incrementally instead of betting on upfront patterns, using weighted styles (loosely based on Mark Richards) and concrete tactics like DDD, CQRS, API strategies (REST/GraphQL/gRPC), CI/CD and automated governance. Claims microservices pay off only when teams, DevOps and data partitioning reach maturity, cites 136,000 deployments a day at Amazon versus 40 deployments a day at Shopify to show tradeoffs, and recommends starting with a modular monolith and measuring enough to add constraints later.

AI-written summary · about

  1. 0:00Introduction
  2. 1:03Misunderstanding agile
  3. 7:07What is architecture?
  4. 10:41Why architectures fail
  5. 16:18Good design vs overengineering
  6. 21:37Microservices reality check
  7. 27:22Constraints shape architecture
  8. 32:55Evolving layered monolith
  9. 40:21Domain-driven decomposition
  10. 47:28Measuring architectural fit
  11. 57:04Enough is enough
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.