background
Many people are accustomed to imitating in their studies and work, and it is difficult to think about active innovation.
Those who know how to adapt and innovate are worth learning.
Sometimes, if everyone can take the idea of starting from the end, to draw, to design plans, and to write code, it may be able to increase the speed of advancement .
The same is true for drawing. We should not be dogmatic, but should be clear and understandable as the core goal.
Pattern example
Here is an example to help you understand what I mean.
The following picture shows the picture of "The Shortest Learning Path for DDD" GitChat. It
looks great. Perhaps for the author, you can quickly distinguish the meaning of different colors.
In order for everyone to understand the meaning of different colors, a legend is provided at the top "intimately".
But for readers, it is still necessary to repeatedly check the legend to distinguish the meaning of different colors.
So why can't the domain services, domain capabilities, and value objects be directly marked in the boxes like the "<entity>" in the red part in the figure?
We can see another article "Three Paintings of Alibaba Technical Experts: How to Draw a Good Architecture Diagram
"
This picture not only uses colors, but also identifies the type of system at the top of the box, which is obviously more friendly.
The internal and external systems are distinguished not only by color but also by the dashed frame. The container will also have the container logo. very clearly.
recommend
Recommend a few great websites for learning drawing
VisualParadigm Common UML diagram tutorials
Visual model of C4 software architecture
Thinking
The longer you work, the more you should think about the purpose of doing something.
The more important thing about learning knowledge is to internalize and use it flexibly, not dogmatic! !