Diagrams as Code
It’s not for everyone.
I prefer to write diagrams out logically and then let the visual aspect be generated.
This helps me by making the visual presentation an artifact of what is basically a written outline.
I’ve learned that communicating flows of information can often be better presented visually than trying to write them out, especially once it involves more than a few “nodes” of responsibility. Visualizing a complicated process can be done more easily in a visual way, as well as help expose some possible issues when ownership is transfered between lanes too many times.
LucidChart, Draw.io and other tools are great for a quick solution.
Mermaid also provides a nice simple text based diagramming tool that is integrated with many markdown tools.
For me, this just never fit. I like a bit of polish and beauty in a visual presentation and most of these are very utilitarian in their output.
I came across diagrams1 and found it a perfect fit for intuitive and beautiful diagram rendering of cloud architecture, and figured it would be worth a blog post to share this.
Do not create a project named the same thing as your dependency, ie project name = diagrams for example.
This will error out and send you down a search in github issues to discover this issue.
Install Poetry2 and create a new poetry project in your directory using
Once it gets to the package additions add
diagrams to your poetry file.
Finally, create a new file called
diagram.py in your directory.
Once you populate this file, you can run your diagram using the virtual env it manages by calling
poetry run python diagram.py.
Additionally, any command line arguments you want to pass would just go through like
poetry run python diagram.py --outdirectory foobar
The documentation is pretty thorough, but detailed examples and shortcuts are very hard to find. You’ll have to dig through the repo issues on occasion if you find yourself wanting to do something that isn’t obvious. This project seems to be a wrapper around graphviz, so a lot of the documentation for parameters and customizations will be in it’s documentation, not in this project.
To find available nodes and shapes, you’ll need to look at the diagram docs3
Using defaults you can create a simple diagram such as this:
From the github issues and my own customizations, I added a few additions to make the edge (ie, lines) flow easier to work with.
I went through the AWS Reference Architecture Diagrams 4 and used this to provide a more complex example.
Take a look at the AWS PDF5 and compare.
|Individual Node Edits|
|Reference for Graph Attributes|