Keeping Up with the Times: Flexible Architectures
summary
The talk explains how agile teams can design, document, communicate and maintain flexible yet robust software architectures over time. It compares architectural choices and trade-offs—monolith vs. decoupled runtime, DevOps vs. traditional operations, serverless/cloud vs. on‑premises, relational vs. NoSQL/in‑memory storage, and designs aimed at longevity vs. throwaway systems—and discusses implications of modern architecture styles and patterns for these decisions.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:17Agenda
- 3:07Experts on: What is Software Architecture?
- 4:27What is Architecture to Me?
- 4:51What Does 'Flexible' Actually Mean?
- 6:06The Classic
- 7:41Why Ditch the Monolith Partner?
- 10:55Microservices – in Brief...
- 15:10Microservices in Practice
- 19:18Or Put More Drastically...
- 19:56Compromises/Alternatives
- 21:52Influences on Decisions
- 25:03Quality Characteristics
- 25:36Example: Quality Goals – Corona Warn App
- 27:56High-Level Solution Approaches
- 29:30Classification of Solution Approaches
- 29:58Strengths and Challenges
- 32:26Typical Framework Conditions
- 35:04Solution Strategy
- 38:23Mission Statement
related talks
58mThe past, present and future of Architecture
01h 00mAgile Architecture
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
38mAgile Architecture
02mThe evolution of software architecture
44mDeliberate Architecture
37mArchitecting for Tomorrow: A Pragmatic Perspective
43mResilience, Scalability, Performance – On the Architecture of Agile Product Teams