Software Architecture in a DevOps World
summary
Argues for concrete practices: generate architecture diagrams with PlantUML, enforce rules with ArcUnit and policy checks (Open Policy Agent), and use infrastructure-as-code and autoscaling for deployable systems. Shares failures: an over‑configurable government project produces 6,000 pages of queries and terrible performance, rescued by simplifying and rebuilding; a hidden metric shows a feature logged only 21 accesses (all by one user), prompting safe removal. Recommends small iterative proofs and team ownership.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:01What is software architecture?
- 9:12DevOps principle: gradual changes
- 11:01DevOps principle: customer oriented
- 13:25DevOps principle: automation
- 15:20DevOps principle: ownership
- 19:06DevOps principle: collaboration
- 21:18DevOps principle: experimentation
- 24:44DevOps principle: continuous improvement
related talks
46mArchitecture & DevOps
48mDown the Ivory Tower towards Agile Architecture
45mSoftware Architecture for Humans!
51mSoftware Architecture for Humans!
30m5 Things Every Developer Should Know about Software Architecture
45mFive things every developer should know about software architecture
42mSoftware Architecture in the Age of Agility and DevOps
45mDemocratising Software Architecture