Describing and Documenting Your Architecture
summary
Proposes an Architecture Narrative that sequences why, constraints, alternatives and the final design; shows concrete artifacts: ADRs (example ADR21 chooses a centralized RabbitMQ broker over per-hub clusters), ADLs to generate/enforce architecture, and the C4 model for representational consistency. Uses three systems as examples (ghost kitchen scaling from 400 to 1,500–2,000 meals and 6–8 locations, student testing, ticketing), compares Azure Service Bus federation vs Rabbit MQ, and gives diagram rules (title, unidirectional labeled flows, blue for accessibility).
AI-written summary · about
chapters (6)
- 0:00Introduction to architecture documentation
- 3:55Building a compelling architecture story
- 7:56Act one the setup and context
- 19:44Act two confrontation and challenges
- 37:16Act three resolution and diagrams
- 58:59Closing and Q&A
related talks
45mArchitecture and the Architect AD2022
50mVisualise, Document & Explore Your Software Architecture
58mThe past, present and future of Architecture
54mArchitecture Is Not Nonsense
39mOne Does Not Simply Make Architecture Decisions Alone: ADRs and Architec
44mArchitectural Practices for Greater Scalability and Innovation
36mApplication Architecture Patterns
31mLightweight Software Architecture