11–20 of 80 posts
If you have to annotate each box you might as well ditch the image. In which case you can describe what it does instead of just naming the service it uses. And use Mermaid markup for the diagrams; GitHub supports it!
I would suggest that if your architecture diagrams are a bunch of icons provided by AWS/Azure/GCP with lines pointing at each other... you are doing it wrong. The 'what does this element do for my system' is vastly more important than the 'which in vogue offering from my cloud provider implements it'. I highly suggest folks take a look at the C4 Model: https://c4model.com/
I would suggest that if your architecture diagrams are a bunch of icons provided by AWS/Azure/GCP with lines pointing at each other... you are doing it wrong. The 'what does this element do for my system' is vastly more important than the 'which in vogue offering from my cloud provider implements it'. I highly suggest folks take a look at the C4 Model: https://c4model.com/
What a useless crap. It’s an over engineered documentation framework focusing on all the wrong things so some agile consultant can sell more cool aid. I don’t trust anything that is designed someone who last did real projects in the 2000’s OOP Java enterprise craze.
1. https://wiki.gnome.org/Apps/Dia/Screenshots>
Earlier quoted context omitted.
What a useless crap. It’s an over engineered documentation framework focusing on all the wrong things so some agile consultant can sell more cool aid. I don’t trust anything that is designed someone who last did real projects in the 2000’s OOP Java enterprise craze.
It's not a hard science. Take the parts that work for your team and scrap the ones that don't.
You don't have to stick to their software either, use DrawIO if that's what you prefer, but understand the main concepts that C4 is trying to impart about the separation, what goes on the arrows, and how useless icons can be.
I would suggest that if your architecture diagrams are a bunch of icons provided by AWS/Azure/GCP with lines pointing at each other... you are doing it wrong. The 'what does this element do for my system' is vastly more important than the 'which in vogue offering from my cloud provider implements it'. I highly suggest folks take a look at the C4 Model: https://c4model.com/
Your preview image has a transparent background, and isn't readable when github renders in dark mode.
It cuts your effective dynamic range in half, but works pretty well. And adjusting opacity is actually somewhat easier than adjusting color hex values
I haven't tried it with colors though - but I expect it'd work as well
In contrast, forcing a white background on people running dark mode is kinda ugly in my opinion as you end up with a border/cutout and it doesn't flow with the rest of the content as well
I'm slightly disappointed.