> Visualize your systems, discover architecture from code, and keep everything in sync.
Not everything.
Lock up your c4 models in a proprietary platform instead of a diagrams-as-code.
Connect to git not to bidirectionally sync c4 models in a preservable text format, but to slurp more info into the golden-handcuffs source of truth.
Avoid detailing how invention intellectual property disclosure and platform security reconnaissance are protected against.
(On the outbound sync, see Structurizer or plant uml c4 for text portable examples, or icepanel.io for JSON metadata export of full models.)
It's a beautiful product and we'd authorize our teams to use it instantly, except for the philosophical and practical non-starters, and we'd need to have a deep understanding for the security model around keys-to-the-kingdom systems.
Has anyone created a set of C4 diagrams for fundamental things, like the various processes that might all be running on an idle Debian/CentOS/Alpine system?
5 comments
[ 3.2 ms ] story [ 21.5 ms ] threadNot everything.
Lock up your c4 models in a proprietary platform instead of a diagrams-as-code.
Connect to git not to bidirectionally sync c4 models in a preservable text format, but to slurp more info into the golden-handcuffs source of truth.
Avoid detailing how invention intellectual property disclosure and platform security reconnaissance are protected against.
(On the outbound sync, see Structurizer or plant uml c4 for text portable examples, or icepanel.io for JSON metadata export of full models.)
It's a beautiful product and we'd authorize our teams to use it instantly, except for the philosophical and practical non-starters, and we'd need to have a deep understanding for the security model around keys-to-the-kingdom systems.
I wasn't able to find information about the company and where it is registered, might want to add that.