Diagrams as Code 2.0 • Simon Brown • GOTO 2021
"long-lived documentation" - "Think about diagrams as 'disposable' artifacts"
https://c4model.com/ C4 Model - model for visualizing software architecture; hierarchal dataset; Diagrams as abstractions, differing levels of technical details; think of it as zooming into maps at different levels * Level 1: Context * Level 2: Containers * Level 3: Components * Level 4: Code
Product Comparisions - Working with the DSL (Lite v. CLI v. DSL Editor): https://structurizr.com/help/dsl - Product offerings (Lite v. Cloud v. On-premise): https://structurizr.com/products
The DSL is rendering tool agnostic
Diagrams as code 1.0 - PlantUML, Mermaild, etc are input formats
Diagrams as code 2.0 - PlantUML, Mermaild, etc are output formats
Checkout: - Online REPL: https://structurizr.com/dsl?example=amazon-web-services - DSL Guidance: https://github.com/structurizr/dsl/tree/master/docs/cookbook - Examples: https://github.com/structurizr/examples