The past, present and future of Architecture
summary
Argues that architecture must be evolutionary — explicitly guided and measurable across reliability, scalability, security and maintainability — enabled by continuous delivery and CI safety nets rather than big up‑front design. Cites refactoring databases to decompose schema changes, consumer‑driven contracts for service boundaries, a 100‑trades‑a‑day vs high‑value trading example, and a scientific case of a single observation producing ~6 PB to illustrate microservices vs monolith and data locality trade‑offs.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 4:15What is Architecture
- 6:20Architecture is necessary
- 8:17Incremental change
- 10:20Technological change used to be slow
- 12:40Agile Manifesto
- 15:20The history of Agile
- 18:00Refactoring Databases
- 22:40Monoliths
- 24:20Evolutionary Architecture
- 26:30Continuous Delivery
- 29:25The future
- 30:33Platforms
- 33:50Distributed computing
- 35:35Heterogeneous architectures
- 39:25Thank you
- 40:25Cyber security
- 43:55microservices
- 47:33business capabilities
- 52:55disposability
- 55:53evolutionary
related talks
50mTowards an Evolutionary Architecture
44mDeliberate Architecture
39mPrinciples of Evolutionary Architecture
01h 00mEvolutionary Architectures
35mPrinciples of Evolutionary Architecture
14mThe Evolution of Evolutionary Architecture
37mArchitecting for Tomorrow: A Pragmatic Perspective
49mThe Principles of Evolutionary Architecture