Software architecture diagrams - which tool should we use?

In Modelling software architecture with PlantUML, I showed you a way to generate multiple software architecture diagrams in PlantUML format, all from a single definition of a model and views. That definition was written using the open source Structurizr DSL, which itself is independent of any diagramming tool.

Static structure diagrams

"Which diagramming tool should we use?" - I hear this question on a regular basis, with teams debating the pros and cons of tools such as PlantUML vs Mermaid, for example. Rather than argue over which diagramming tool you're going to use, why not use them all? Although we only saw PlantUML support in the previous blog post, the open source Structurizr CLI actually allows you to use a number of tools to render your software architecture diagrams. For example, here are four versions of the same view (a C4 model Container diagram), each created from the same DSL file, and rendered in different diagramming tools.

PlantUML

 Mermaid

Structurizr (traditional diagram)

Structurizr (graph view)

Dynamic/behavioural diagrams

The Structurizr DSL and CLI also support Dynamic diagrams for showing collaboration/behaviour, and interactions at runtime. For example, here are four versions of a Dynamic view, again created from the same DSL file, and rendered in different diagramming tools.

PlantUML

Mermaid

WebSequenceDiagrams

Structurizr

Summary

Each diagramming tool has its own pros and cons, so using a tool agnostic format to define your model and views provides an easy way to try them all out, and reduce lock-in.