Applying architectural principles, processes, and tools
summary
Architecture requires five knowledge areas: environment (cloud, distributed systems, containers, failure modes, security), principles (business goals → quality attribute requirements → design), processes to turn requirements into designs, styles and tactics (microservices give availability and flexibility but hurt performance so use caching and mid‑tier discovery), and tools and frameworks. Protocol buffers provide automatic logging and up‑to‑date interface documentation, feature toggles separate install from activation for continuous deployment, and the DevOps ecosystem counts roughly 500–1000 DevOps tools that shape architectural choices.
AI-written summary · about
chapters (11)
- 0:00Introduction and thanks
- 0:43Five categories of architect knowledge
- 1:26Architecture principles and business goals
- 4:01Architectural styles and patterns
- 6:14Architectural processes and trade-offs
- 10:29DevOps impact on architecture
- 13:00Business and technical environments
- 15:51Cloud and distributed systems
- 17:13Tools and frameworks explosion
- 20:52Summary of key topics
- 22:44Q&A session
related talks
46mArchitecture & DevOps
01h 13mPragmatic Architecture
45mArchitecture and the Architect AD2022
41mSoftware Architecture in a DevOps World
58mThe past, present and future of Architecture
49mAs Much Architecture Work as Necessary
46mPractical (a.k.a. Actually Useful) Architecture
48mArchitecture: The Stuff That's Hard to Change