Diagrams as code 2.0
summary
Argues that modeling beats drawn diagrams by creating a single source of truth: a Java-based Structurizr DSL model describes elements and relationships once and generates multiple views (context, container, component) with implied relationships and theming. Shows tooling: a CLI that exports to PlantUML/Mermaid/dot, a browser renderer (free Structurizr Lite Docker) with interactive force‑directed views, and a component‑finder plus JSR223 hooks for auto‑generating parts from code. Demonstration claims reduced duplication, automated exports, and usable interactive diagrams for large systems.
AI-written summary · about
chapters (11)
- 0:00The problem with diagrams
- 1:49The C4 model explained
- 4:25Limitations of manual tools
- 7:23Introducing diagrams as code
- 10:41Structurizr DSL basics
- 15:41Styling and presentation
- 18:22Rendering and tool flexibility
- 25:16Handling large systems
- 29:01Advanced automation and hybrid
- 34:32Closing thoughts and demo
- 40:08Q&A session
related talks
01h 00mC4 models as code
41mC4 Models as Code
54mC4 models as code
01h 00mVisualise, document and explore your software architecture
52mC4 Models as Code
57mVisualise, document and explore your software architecture
49mReverse-engineering Architecture Diagrams
45mSet your data free with model-based architecture diagramming
