Interesting post Simon! I'm a big proponent of codifying anything teams want to repeat, collaborate on, or standardize around. I like the concept of diagrams as code for workflow diagrams or even abstract white-boarding, especially now that we're all remote.
For application infrastructure, Stackery takes this idea a bit further with diagrams as code that can be deployed into a public cloud provider, like AWS. I've embedded a simple example that's bidirectional between the code and the diagram, though the technique really shines as architectures (and code) scale.
What do you think? Have you seen teams turn their architectural diagrams as code into deployable artifacts?
Author "Software Architecture for Developers" | Creator of the "C4 model for visualising software architecture" | Founder at Structurizr | Software architecture training at architectis.je
Interesting post Simon! I'm a big proponent of codifying anything teams want to repeat, collaborate on, or standardize around. I like the concept of diagrams as code for workflow diagrams or even abstract white-boarding, especially now that we're all remote.
For application infrastructure, Stackery takes this idea a bit further with diagrams as code that can be deployed into a public cloud provider, like AWS. I've embedded a simple example that's bidirectional between the code and the diagram, though the technique really shines as architectures (and code) scale.
What do you think? Have you seen teams turn their architectural diagrams as code into deployable artifacts?
I have yes ... here's an example of creating Azure resources with Structurizr for .NET ... github.com/ChristianEder/Structuri...