Software Architecture in the Age of Agility and DevOps
summary
Six concrete claims: apply the six principles of Continuous Architecture to product-aligned services, prioritize quality attributes when choosing a database (relational for most components, document DB for document store), and postpone hard choices until metrics require them. Case study builds a trade‑finance system on AWS with per‑service databases, REST first then switch to messaging if scalability fails, and a separate VM for the payment gateway for resilience. Low ADR adoption motivates documenting decisions in Git and measuring production feedback via observability and test harnesses.
AI-written summary · about
chapters (22)
- 0:00Intro
- 2:40How many people model their system
- 3:15Agenda
- 3:48How technology evolved
- 9:30Agile and DevOps
- 10:55Developers and DevOps
- 11:28Software vs Buildings
- 12:35Why Architecture is Important
- 14:02Principle 1 Architect Products not Solutions
- 15:35Principle 2 Quality Attributes
- 16:47Quality Attributes Tree
- 17:15Delayed Design Decisions
- 19:00Simulation annealing
- 20:35Architect for change
- 21:57Architect for build test
- 23:22Conways Law
- 26:22Case Study
- 29:59DomainDriven Design
- 31:55Microservices
- 34:12Database Technology
- 37:08Essential Activities
- 39:56Technical Debt
related talks
01h 00mAgile Architecture
46mArchitecture & DevOps
41mSoftware Architecture in a DevOps World
38mAgile Architecture
46mAgility and Architecture Together – Enabling a Fast Flow of Change
44mThe Art of Architecting for Scale
58mThe past, present and future of Architecture
49mCase study of a good enough architecture