Some thoughts on architecture

I want to draw a system architecture diagram recently, but I can't draw it no matter how I draw it.
Later, I thought about the reasons carefully, because I drew the architecture diagram of the system that I know currently, but for various reasons, the architecture of this system is actually not very ideal, the functions and services are not clearly divided, and the architecture is used too much. This kind of technology leads to an extremely complex framework, and many pits have been left after many technological changes. Therefore, drawing an architecture diagram on this basis will never draw a better architecture.
So what is the correct approach?
I think the correct approach is to draw a more ideal architecture diagram that is close to the current business needs and existing architecture based on my understanding of the system and business.
After drawing this picture, go back and look at the current architecture, so that you can discover the problems of the current architecture and the direction of future improvement, and you will have a picture and a direction in your heart to make your system better.
And only in this way can you grow better. This is the only way for architects.
So sometimes, the right way of thinking is really important, it can help sort out many problems, and the right way of thinking comes from my continuous hard work and thinking.

Guess you like

Origin blog.csdn.net/shida219/article/details/109740785