Architecture & DevOps
summary
Argues five concrete DevOps-informed architecture strategies: choose proven stacks like Spring/Hibernate/Tomcat to keep systems simple and handoffable, adopt docs as code with AsciiDoc/arc42 and Structurizr DSL in CI/CD to keep architecture near developers, extract tiny services incrementally (example: a salutation service run in parallel to a Java EE monolith) to learn safely, defend psychological safety after an outage, and set quality goals from customer language (startup aims to be 20% climate positive).
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:51Defining software architecture
- 4:02What is DevOps?
- 7:10Keeping it local and simple
- 13:50Documentation as code
- 20:50Incremental architecture changes
- 26:46Psychological safety in teams
- 31:01Customer-focused architecture
- 36:23Five DevOps ideals summary
- 39:34Reflection and Q&A
related talks
41mSoftware Architecture in a DevOps World
48mDown the Ivory Tower towards Agile Architecture
42mSoftware Architecture in the Age of Agility and DevOps
37mArchitecting for Tomorrow: A Pragmatic Perspective
49mCase study of a good enough architecture
37mDevOps for Java Developers (Or Maybe Against Them?!)
01h 00mAgile Architecture
08msoftware architecture and agile development