Diagram as Code
diagrams.mingrammer.com
Diagram as Code
1–10 of 77 posts
Re: Diagram as Code
#2There are some other kinds of diagrams would we like to draw that’s not system architecture diagrams, eg:
- algorithms
- decision trees
- UML/ER Diagrams
Mermaid (JS) helps draw quality diagrams quickly - more than system architecture diagrams.
It would have been perfect if the development cycles that went here was used to create Mermaid templates instead.
Unless this also lets us draw more than just system architecture diagrams.
Re: Diagram as Code
#3It seems to be hyperfocused on system architecture diagrams. There are some other kinds of diagrams would we like to draw that’s not system architecture diagrams, eg: - algorithms - decision trees - UML/ER Diagrams Mermaid (JS) helps draw quality diagrams quickly - more than system architecture diagrams. It would have been perfect if the development cycles that went here was used to create Mermaid templates instead.…
Re: Diagram as Code
#4Re: Diagram as Code
#5It seems to be hyperfocused on system architecture diagrams. There are some other kinds of diagrams would we like to draw that’s not system architecture diagrams, eg: - algorithms - decision trees - UML/ER Diagrams Mermaid (JS) helps draw quality diagrams quickly - more than system architecture diagrams. It would have been perfect if the development cycles that went here was used to create Mermaid templates instead.…
Re: Diagram as Code
#6It seems to be hyperfocused on system architecture diagrams. There are some other kinds of diagrams would we like to draw that’s not system architecture diagrams, eg: - algorithms - decision trees - UML/ER Diagrams Mermaid (JS) helps draw quality diagrams quickly - more than system architecture diagrams. It would have been perfect if the development cycles that went here was used to create Mermaid templates instead.…
The focus would make sense to me if, say, it exported to initial terraform templates or something like that.
IMO the end days for TF and YAML engineering are close, at least for new work
It’s all HTTP APIs. Build a web UX and store the state in a DB.
SRE/ops people ...at work just use the methods everyone else does
Unless the company still has hardware, cloud ops/SRE is just making their lives harder to be different
Re: Diagram as Code
#7Re: Diagram as Code
#8Earlier quoted context omitted.
The focus would make sense to me if, say, it exported to initial terraform templates or something like that.
I’d prefer to avoid text blob artifacts if this was being used at work with plenty of text blobs to babysit already IMO the end days for TF and YAML engineering are close, at least for new work It’s all HTTP APIs. Build a web UX and store the state in a DB. SRE/ops people ...at work just use the methods everyone else does Unless the company still has hardware, cloud ops/SRE is just making their lives harder to be dif…
Please no. Don't make running a stateful service a requirement for tooling people need to use when the world is on fire. Or needs to load 40Mb of JS to rebuild a deployment, and works only on Chrome 46.012.2039465. Ops/SRE/DevOps/SysAdmin/SysOps/etc are different, and have optimised things to reduce the amount of dependancies.
Re: Diagram as Code
#9A tool I've used in the past is SequenceDiagram.org for diagraming a sequence of service calls. While a bit old-school, it's good for its purpose.
I've also used Whimsical[0] to model flows and graph-like relationships. It's got the added benefit of allowing multiple users to view and edit the same document. Whimsical is still my favorite tool right now due to flexibility, but it's a closed-source/paid product, so I'm open to alternatives.