Diagram as Code

Diagram as code allows you to track the architecture diagram changes in any version control system. Furthermore, using the code to maintain the diagrams has more benefits.

Version control and collaboration

Diagrams created as code can be stored in a version control system like Git, allowing teams to track changes, collaborate, and review diagrams. This will enable the multiple teams to review and follow the architectural changes together.

Reproducibility

Did you ever ask the team “whether they have original files of PNG like VISIO or Drawio file”? Regardless of the size of the company, you will be able to find many pieces of PNG or PowerPoint files when you refer to the diagram. With Diagram-as-code, you can generate diagrams from code, ensuring consistency and reproducibility.

Automation and Integration

There are some visualization tools of Infrastructure-as-code however, I didn’t hear any diagram-as-code is directly integrated with IaaC like Terraform. Then you can ask ‘Why are you only using IaaC and use the visualisation tool to make the diagram’? For example, there is Driftctl.

However, many visualisation tools of IaaC are neither easy-to-read nor used for the architectural view because IaaC tells about the…