In the technical documentation, we often find that topology, architecture, and struct are not strictly differentiated. Sometimes we can see that a topology becomes a pure echure, and sometimes a struct becomes a pure echure.
From a rigorous point of view, how should we define and distinguish them for correct use? My personal understanding is as follows: 1. the focus of topology is network deployment, such as the distribution of data centers. architechure contains various internal modes and subsystems of the system, as well as the relationships between peripheral systems related to or dependent on. 3. struct generally only involves the system. The typical class diagram is the structure of struct, which indicates the last sentence from the field of view to the level of detail: Topology> explain echure> struct: there can be overlaps between the two, which is just a link between the two. The architecture has a broad architecture and a narrow architecture. The broad architecture almost includes the above three. The narrow architecture only refers to elastic echure.