CN113364632B - Method, device, storage medium and apparatus for generating architecture diagram of service system - Google Patents
Method, device, storage medium and apparatus for generating architecture diagram of service system Download PDFInfo
- Publication number
- CN113364632B CN113364632B CN202110669013.8A CN202110669013A CN113364632B CN 113364632 B CN113364632 B CN 113364632B CN 202110669013 A CN202110669013 A CN 202110669013A CN 113364632 B CN113364632 B CN 113364632B
- Authority
- CN
- China
- Prior art keywords
- cluster
- server cluster
- server
- layered
- architecture diagram
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a method, a device, a storage medium and a device for generating a business system architecture diagram, wherein the method comprises the following steps: acquiring a domain main body and a server corresponding to a service system to be processed, acquiring a host name of the server, grouping the servers according to the host name and the domain main body to acquire a server cluster topological graph, and performing hierarchical positioning on the server cluster topological graph to acquire a service system architecture graph of the service system to be processed; according to the invention, the service system architecture diagram does not need to be drawn manually, and the servers are grouped and positioned based on the server host names and the domain main bodies of the service systems to be processed so as to obtain the service system architecture diagram of the service systems to be processed, so that the service system architecture diagram can be generated quickly and effectively, and the reliability of the service system architecture diagram is ensured.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method, an apparatus, a storage medium, and a device for generating a business system architecture diagram.
Background
Each system platform typically consists of several pieces of software and tens or even hundreds of machines, and a business system architecture diagram that groups and associates the software and servers is essential to developers, maintenance personnel, and others who want to understand the system.
In the prior art, the business system architecture diagram is often drawn manually after the system platform is built, so that time and labor are wasted, manual redrawing is required when the system architecture is changed, and the maintenance cost is high.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide a method, equipment, a storage medium and a device for generating a business system architecture diagram, and aims to solve the technical problem that the time and labor are wasted by manually drawing the business system architecture diagram in the prior art.
In order to achieve the above object, the present invention provides a method for generating a business system architecture diagram, wherein the method for generating the business system architecture diagram comprises the following steps:
acquiring a domain main body and a server corresponding to a business system to be processed, and acquiring a host name of the server;
grouping the servers according to the host names and the domain main bodies to obtain a server cluster topological graph;
and carrying out hierarchical positioning on the server cluster topological graph to obtain a service system architecture graph of the service system to be processed.
Optionally, the step of performing hierarchical positioning on the server cluster topology map to obtain a service system architecture map of the service system to be processed specifically includes:
extracting a server cluster set to be layered from the server cluster topological graph;
obtaining the out-degree of each server cluster to be layered in the server cluster set to be layered, and selecting a target server cluster from the server cluster set to be layered according to the out-degree;
acquiring a target cluster level value of the target server cluster;
adding the target server cluster into a layered server cluster set, and deleting the target server cluster from the server cluster set to be layered;
and when the cluster set of the servers to be layered is a preset empty set, generating a business system architecture diagram according to the layered cluster set of the servers and the target cluster level value.
Optionally, after the step of adding the target server cluster to the layered server cluster set and deleting the target server cluster from the to-be-layered server cluster set, the method for generating the business system architecture diagram further includes:
when the cluster set of the server to be layered is not a preset empty set, adjusting the level value of the target cluster to obtain a level value of a cluster to be added;
adjusting the cluster level value of a server cluster to be processed in the server cluster set to be layered according to the cluster level value to be added, wherein the server cluster to be processed points to the target server cluster;
and returning to the step of obtaining the output degree of each server cluster to be layered in the server cluster set to be layered, and selecting a target server cluster from the server cluster set to be layered according to the output degree.
Optionally, the step of generating a service system architecture diagram according to the layered server cluster set and the target cluster hierarchy value when the to-be-layered server cluster set is a preset empty set specifically includes:
when the server cluster set to be layered is a preset empty set, sorting each server cluster in the layered server cluster set according to the target cluster level value;
determining the target hierarchical position of each server cluster in the hierarchical server cluster set according to the sorting result;
and adjusting the position of the architecture diagram of each server cluster in the layered server cluster set based on the target level position to obtain a service system architecture diagram.
Optionally, the step of grouping the servers according to the host names and the domain subjects to obtain a server cluster topology map specifically includes:
extracting characters from the host name to obtain usage description characters;
grouping the servers according to the application description characters and the domain main body to obtain an initial grouping result;
when the initial grouping result is successful, determining an initial server cluster according to the initial grouping result;
and carrying out cluster merging on the initial server cluster based on a preset cluster use rule to obtain a server cluster topological graph.
Optionally, after the step of grouping the servers according to the usage description characters and the domain subject to obtain an initial grouping result, the method for generating the architecture diagram of the service system further includes:
when the initial grouping result is that grouping fails, generating reminding information, and receiving domain main body supplementary information fed back by a user based on the reminding information;
and updating the domain main body corresponding to the service system to be processed according to the domain main body supplementary information, returning to the step of obtaining the domain main body and the server corresponding to the service system to be processed, and obtaining the host name of the server.
Optionally, the step of grouping the servers according to the usage description characters and the domain subject to obtain an initial grouping result specifically includes:
generating a cluster attribution label of each server according to a preset grouping rule, the use description character and the domain main body;
and grouping the servers according to the cluster attribution label to obtain an initial grouping result type.
In addition, in order to achieve the above object, the present invention further provides a business system architecture diagram generating device, where the business system architecture diagram generating device includes a memory, a processor, and a business system architecture diagram generating program stored in the memory and executable on the processor, and the business system architecture diagram generating program is configured to implement the steps of the business system architecture diagram generating method described above.
In addition, to achieve the above object, the present invention further provides a storage medium, which stores a business system architecture diagram generating program, and the business system architecture diagram generating program realizes the steps of the business system architecture diagram generating method as described above when executed by a processor.
In addition, to achieve the above object, the present invention further provides a business system architecture diagram generating device, where the business system architecture diagram generating device includes: the device comprises an acquisition module, a grouping module and a layering module;
the acquisition module is used for acquiring a domain main body and a server corresponding to the service system to be processed and acquiring a host name of the server;
the grouping module is used for grouping the servers according to the host names and the domain main bodies to obtain a server cluster topological graph;
the layering module is used for carrying out layering positioning on the server cluster topological graph so as to obtain a service system architecture graph of the service system to be processed.
The method comprises the steps of obtaining a domain main body and a server corresponding to a service system to be processed, obtaining a host name of the server, grouping the servers according to the host name and the domain main body to obtain a server cluster topological graph, and carrying out hierarchical positioning on the server cluster topological graph to obtain a service system architecture graph of the service system to be processed; the invention does not need to draw the architecture diagram of the service system manually, but carries out grouping positioning on the servers based on the name of the server host of the service system to be processed and the domain main body so as to obtain the architecture diagram of the service system to be processed, thereby being capable of quickly and effectively generating the architecture diagram of the service system and ensuring the reliability of the architecture diagram of the service system.
Drawings
Fig. 1 is a schematic structural diagram of a business system architecture diagram generation device of a hardware operating environment according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of a first embodiment of a method for generating a business system architecture diagram according to the present invention;
fig. 3 is a schematic diagram of a main body of a constructed domain of an embodiment of a method for generating a business system architecture diagram according to the present invention;
fig. 4 is a schematic view of inter-cluster contact according to an embodiment of the method for generating a business system architecture diagram of the present invention;
fig. 5 is a schematic view of a domain body corresponding to a to-be-processed service system according to an embodiment of a method for generating an architecture diagram of a service system of the present invention;
fig. 6 is a flowchart illustrating a second embodiment of a method for generating a business system architecture diagram according to the present invention;
fig. 7 is a schematic diagram of an initial grouping result according to an embodiment of the method for generating a service system architecture diagram of the present invention;
fig. 8 is a server cluster topology diagram according to an embodiment of the method for generating a service system architecture diagram of the present invention;
fig. 9 is a flowchart illustrating a method for generating a business system architecture diagram according to a third embodiment of the present invention;
fig. 10 is an architecture diagram of cluster hierarchy initial value assignment according to an embodiment of a method for generating an architecture diagram of a service system of the present invention;
fig. 11 to 14 are schematic diagrams illustrating adjustment of cluster hierarchy values according to an embodiment of a method for generating a service system architecture diagram;
fig. 15 is a block diagram showing the structure of a first embodiment of the service system architecture diagram generating apparatus according to the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 1, fig. 1 is a schematic structural diagram of a business system architecture diagram generation device of a hardware operating environment according to an embodiment of the present invention.
As shown in fig. 1, the business system architecture diagram generating apparatus may include: a processor 1001, such as a Central Processing Unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to implement connection communication among these components. The user interface 1003 may include a Display screen (Display), and the optional user interface 1003 may further include a standard wired interface and a wireless interface, and the wired interface for the user interface 1003 may be a USB interface in the present invention. The network interface 1004 may optionally include a standard wired interface, a WIreless interface (e.g., a WIreless-FIdelity (WI-FI) interface). The Memory 1005 may be a Random Access Memory (RAM) Memory or a Non-volatile Memory (NVM), such as a disk Memory. The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the architecture shown in FIG. 1 does not constitute a limitation of business system architecture diagram generation apparatus, and may include more or fewer components than shown, or some components in combination, or a different arrangement of components.
As shown in FIG. 1, a memory 1005, identified as one type of computer storage medium, may include an operating system, a network communication module, a user interface module, and a business system architecture diagram generation program.
In the service system architecture diagram generating device shown in fig. 1, the network interface 1004 is mainly used for connecting to a background server and performing data communication with the background server; the user interface 1003 is mainly used for connecting user equipment; the service system architecture diagram generation device calls a service system architecture diagram generation program stored in the memory 1005 through the processor 1001, and executes the service system architecture diagram generation method provided by the embodiment of the present invention.
Based on the above hardware structure, an embodiment of the method for generating a business system architecture diagram of the present invention is provided.
Referring to fig. 2, fig. 2 is a flowchart illustrating a method for generating a business system architecture diagram according to a first embodiment of the present invention.
Step S10: the method comprises the steps of obtaining a domain main body and a server corresponding to a service system to be processed, and obtaining a host name of the server.
It should be understood that the main body of the method of the embodiment may be a computing service device with data processing, network communication and program running functions, such as a server and a computer, or other electronic devices capable of implementing the same or similar functions, which is not limited in this embodiment.
It should be noted that the ontology may be a conceptualized explicit specification. The understanding of the definition of an ontology can be from four aspects: conceptualized, explicit, formalized, and shared. The conceptualization is the abstraction of things in objective reality to form an abstract conceptual model; explicit means that the abstracted concepts and their relationships are explicit, unambiguous; formalization refers to the concept of a description that can be understood and processed by a computer; shared means that knowledge in the ontology is recognized and commonly accepted. The body has 5 basic elements, which are respectively: concepts, relationships, functions, axioms, and instances. The concept is also called a class, and is anything abstracted; relationships are the interrelationships between concepts; the function is a special relation, namely the first n-1 elements can uniquely determine the nth element; axiom stands for eternal true assertion; an instance is some specific entity of a class. The ontology aims to acquire knowledge of related fields, and the most fundamental difference from the traditional knowledge is that the content of the ontology is 'computer understandable' and has a large amount of semantic information.
Domain bodies are used to refer to terms appropriate for certain domains that are recognized and defined in particular domains. For example, "Kafka" is commonly understood as a novice kaffian, but in the IT domain, IT is an open-source, distributed messaging system.
It should be understood that the domain master is generally pre-constructed by experts in each domain due to its expertise.
In particular implementations, for example, an ontology model, may be represented by a triplet: ON ═ C, P, R, where C represents the set of concepts, P represents the set of attributes, and R represents the set of relationships. Specifically, the field is denoted OND.
It can be understood that, for a new service system, a new field body is not needed, and only a perfect and shared field body needs to be added, so that the cluster name and the host application name can be found in the field body.
Therefore, the domain main body corresponding to the service system to be processed can be obtained by supplementing, perfecting and acquiring the information such as software, software types, services and the like related to the service system to be processed on the basis of the established domain main body. Sophisticated content may include concepts (classes), relationships, and instances of domain ontologies. The constructed domain body may be a domain body of an IT domain constructed according to the business system of a company, and a plurality of business systems of a company may share one domain body. For the present invention, 3 concepts, relationships and examples are used in the ontology 5 element. Concepts are representations of specific software and types of software; relationships are relationships between concepts, such as relationships between parent and child classes of subclasiof, equality of equivalentClass, relationships between instanceOf class and instances, etc.; an instance is some actual existence of a concept. As in the IT field, three concepts of webserver, web and tomcat are provided, tomcat is a subclass of webserver, web and webserver are in an equal relationship (web is an abbreviation of webserver in the host name), and admin is an instance of tomcat and represents a management function module.
It should be noted that for some companies, the number of servers is large, and there is a host name naming specification for the servers for clear distinction and identification, and the host name is already planned at the time of applying for the machine. The host name in the invention is named according to the specification: "use + number, project, department". For example, db01.monitor. yw, tomcat03.pay. yf, voice02.app. yf. The "use" may be specific software, or a type of software, or a business use; "project" is used to specify which servers are to build the architecture diagram for the project.
In a specific implementation, for example, the server may be represented by S, the hostname of the server may be represented by H, and the content of the H hostname is normalized and represented by un.i.d., where U represents usage, N represents two digits, I represents a project, and D represents a department.
For ease of understanding, the description will be made with reference to fig. 3,4, and 5 and table 1, but this scheme is not limited thereto. Fig. 3 is a schematic diagram of a constructed domain subject, fig. 4 is a schematic diagram of a connection between clusters, fig. 5 is a schematic diagram of a domain subject corresponding to a to-be-processed service system, and table 1 is a server table corresponding to the to-be-processed service system. In fig. 3, rectangles represent concepts or classes, parent-child relationships are represented between upper and lower classes, and comma-separated classes in the rectangles represent equality relationships. If nginx is a subclass of the web, database is an equivalence relation class with db. The domain ontology is common to multiple projects, commonly maintained. FIG. 4 is the project macro-framework-network topology data set-provided by the project manager or architect: which clusters and how they are related to each other. The cluster can be treated as a vertex, CL is a finite and non-empty set of vertices with no duplicates, E is a set of relationships between two vertices, the vertices and their relationships form a directed graph G. The number of servers will typically be large, and the number of clusters will not be large.
According to fig. 4 and table 1, it can be known that 4 instances of business system business, admin, voicedb, and imagedb are to-be-added instances, and therefore, based on the inter-cluster connection in fig. 4, the 4 instances of business system business, admin, voicedb, and imagedb are added to the constructed domain ontology to form the domain main body corresponding to the business system to be processed as shown in fig. 5. Wherein rounded rectangles represent examples.
Table 1 server table corresponding to service system to be processed
| Serial number | Server (S) | Host name (H) |
| 1 | 10.0.1.1 | nginx01.item.yw |
| 2 | 10.0.1.2 | nginx02.item.yw |
| 3 | 10.0.1.3 | business01.item.yw |
| 4 | 10.0.1.4 | business02.item.yw |
| 5 | 10.0.1.5 | admin01.item.yw |
| 6 | 10.0.1.6 | fdfs01.item.yw |
| 7 | 10.0.1.7 | fdfs02.item.yw |
| 8 | 10.0.1.8 | fdfs03.item.yw |
| 9 | 10.0.1.9 | voicedb01.item.yw |
| 10 | 10.0.1.10 | imagedb01.item.yw |
Step S20: and grouping the servers according to the host names and the domain main bodies to obtain a server cluster topological graph.
It should be noted that, the server grouping may be to classify servers of the same purpose into the same cluster according to the purpose of the server, and perform data interaction (association) with other clusters as a whole. For example, there are 10 clusters with 100 servers, and server grouping is to divide the 100 servers into the 10 clusters according to the purpose, and each server can be divided into only one cluster.
It can be understood that the servers are grouped according to the host name and the domain subject, and the obtaining of the server cluster topological graph may be that the host name is subjected to character extraction to obtain the use description characters, the servers are grouped according to the use description characters and the domain subject to obtain an initial grouping result, and the server cluster topological graph is generated according to the initial grouping result.
Or extracting characters of the host name to obtain usage description characters, grouping the servers according to the usage description characters and the domain main body to obtain an initial grouping result, determining an initial server cluster according to the initial grouping result when the initial grouping result is successful, and performing cluster merging on the initial server cluster based on a preset cluster usage rule to obtain a server cluster topological graph. This embodiment is not limited in this regard.
In particular implementations, the server cluster set CL ═ { CL ═ CL1,CL2,CL3,…,CLmWhere m denotes the number of clusters, the set of servers to be grouped S ═ S1,S2,S3,…,SnAnd n represents the number of servers. The purpose of the server grouping is to group each server SiDetermine its cluster home label CLj(Si) Where i e (1,2,3, …, n) and j e (1,2,3, …, m).
Step S30: and carrying out hierarchical positioning on the server cluster topological graph to obtain a service system architecture graph of the service system to be processed.
It should be noted that the hierarchical positioning may be to divide each grouped cluster into hierarchies to enhance readability in order to more clearly show the architecture diagram in the visualization system.
It should be understood that the step of performing hierarchical positioning on the server cluster topological graph to obtain the service system architecture graph of the service system to be processed may be to extract a server cluster set to be layered from the server cluster topological graph, obtain the degree of departure of each server cluster to be layered in the server cluster set to be layered, select a target server cluster from the server cluster set to be layered according to the degree of departure, obtain a target cluster level value of the target server cluster, add the target server cluster to the layered server cluster set, delete the target server cluster from the server cluster set to be layered, and generate the service system architecture graph according to the layered server cluster set and the target cluster level value when the server cluster set to be layered is a preset empty set.
In a particular implementation, the cluster hierarchy set may be represented as L ═ L (L)1,L2,L3,…,Ln) Where n represents the number of levels. The purpose of cluster level positioning is to CL each clusteriDetermine its hierarchical attribution label Lj(CLi) Where i e (1,2,3, …, m) and j e (1,2,3, …, n).
In this embodiment, a domain main body and a server corresponding to a service system to be processed are obtained, a host name of the server is obtained, the servers are grouped according to the host name and the domain main body to obtain a server cluster topological graph, and the server cluster topological graph is hierarchically positioned to obtain a service system architecture graph of the service system to be processed; the invention does not need to draw the architecture diagram of the service system manually, but carries out grouping positioning on the servers based on the name of the server host of the service system to be processed and the domain main body so as to obtain the architecture diagram of the service system to be processed, thereby being capable of quickly and effectively generating the architecture diagram of the service system and ensuring the reliability of the architecture diagram of the service system.
Referring to fig. 6, fig. 6 is a flowchart illustrating a second embodiment of the method for generating a business system architecture diagram according to the present invention, and the second embodiment of the method for generating a business system architecture diagram according to the present invention is proposed based on the first embodiment illustrated in fig. 2.
In the second embodiment, the step S20 includes:
step S201: and extracting characters of the host name to obtain the usage description characters.
It should be noted that the usage description character may be specific software, may be a type of software, and may also be a service usage, which is not limited in this embodiment.
It should be understood that the character extraction of the host name to obtain the usage description character may be to parse the host name "usage + number. project. department" of all servers, separate out the "usage" part, and convert all into lower case letters.
For ease of understanding, the description will be made with reference to tables 1 and 2, but this scheme is not limited thereto. Table 2 is a server table corresponding to the analyzed service system to be processed. The host name in table 1 is parsed into the "use" part, and is converted into lower case letters in its entirety, to obtain the use (U) in table 2.
Table 2 server table corresponding to analyzed-purpose pending service system
| Serial number | Server (S) | Host name (H) | Use (U) |
| 1 | 10.0.1.1 | nginx01.item.yw | nginx |
| 2 | 10.0.1.2 | nginx02.item.yw | nginx |
| 3 | 10.0.1.3 | business01.item.yw | |
| 4 | 10.0.1.4 | business02.item.yw | business |
| 5 | 10.0.1.5 | admin01.item.yw | admin |
| 6 | 10.0.1.6 | fdfs01.item.yw | fdfs |
| 7 | 10.0.1.7 | fdfs02.item.yw | fdfs |
| 8 | 10.0.1.8 | fdfs03.item.yw | fdfs |
| 9 | 10.0.1.9 | voicedb01.item.yw | voicedb |
| 10 | 10.0.1.10 | imagedb01.item.yw | imagedb |
Step S202: and grouping the servers according to the application description characters and the domain main body to obtain an initial grouping result.
It should be noted that, the server grouping may be to classify servers of the same purpose into the same cluster according to the purpose of the server, and perform data interaction (association) with other clusters as a whole. For example, there are 10 clusters with 100 servers, and server grouping is to divide the 100 servers into the 10 clusters according to the purpose, and each server can be divided into only one cluster.
It should be understood that, grouping the servers according to the usage description characters and the domain subject, and obtaining the initial grouping result may be generating cluster attribution labels of the servers according to a preset grouping rule, the usage description characters and the domain subject, and grouping the servers according to the cluster attribution labels to obtain the initial grouping result.
It can be understood that the cluster attribution label generated for each server according to the preset grouping rule, the usage description character and the domain subject can be class C, instance I, server S, usage U and cluster CL based on the existing ontology, and each server S is given a preset rule according to the preset ruleiDetermine its cluster home label CLj(Si)。
It should be noted that the preset grouping rule may be preset by an administrator of the business system architecture diagram generation apparatus. In a specific implementation, the preset grouping rule may be as follows, and the embodiment does not limit this.
Rule 5 is class C, instance I, Server S, usage U, and Cluster CL for ontology if Ui＝Im-，CLj＝Cn，ImIs CnExample of (1), then SiHome cluster CLjI.e. determining the home tag CLj(Si)。
Rule 6 is class C, instance I, Server S, usage U, and Cluster CL for ontology if Ui＝Im-，CLj＝Cn，CkIs CnSubclass of (1), ImIs CkExample of (1), then SiHome cluster CLjI.e. determining the home tag CLj(Si)。
For ease of understanding, the description will be made with reference to fig. 4, 5, and 7 and table 2, but this scheme is not limited thereto. Fig. 7 is a schematic diagram of an initial grouping result, based on class C (fig. 5), example I (fig. 5), server S (table 2), usage U (table 2), and cluster CL (fig. 4) of the existing ontology, according to rule 1, server 10.0.1.1 whose usage U is "nginx", and 10.0.1.2 belonging to cluster "nginx"; according to rule 4, servers 10.0.1.3 and 10.0.1.4 with usage U ═ business "belong to the cluster" business ", servers 10.0.1.9 with usage U ═ voicedb" belong to the cluster "voicedb", and servers 10.0.1.10 with usage U ═ imagedb "belong to the cluster" imagedb "; according to rule 5, server 10.0.1.5 with usage U ═ admin "belongs to the cluster" tomcat "; according to rule 2, servers 10.0.1.6, 10.0.1.7, 10.0.1.8 with usage U ═ fdfs "home to the cluster" fastdfs ", and the grouping results are shown in fig. 7.
Further, in order to be able to continue processing with the server when a packet fails. After the step S202, the method further includes:
when the initial grouping result is that grouping fails, generating reminding information, and receiving domain main body supplementary information fed back by a user based on the reminding information;
and updating the domain main body corresponding to the service system to be processed according to the domain main body supplementary information, returning to the step of acquiring the domain main body and the server corresponding to the service system to be processed, and acquiring the host name of the server.
It should be noted that the reminding information may be preset by a manager of the business system architecture diagram generation device. For example, will "packet failed, please supplement the Domain principal! "as a reminder.
The domain main body supplementary information may be information such as software, software type, and service that are not present in the domain ontology.
It should be understood that, the domain subject corresponding to the service system to be processed is updated according to the domain subject supplementary information, so that the domain subject corresponding to the service system to be processed can be generated in a targeted manner, and it is ensured that the server group corresponding to the service system to be processed is successful.
Step S203: and when the initial grouping result is successful, determining an initial server cluster according to the initial grouping result.
For ease of understanding, the description will be made with reference to fig. 7, but this solution is not limited thereto. Fig. 7 is a schematic diagram of an initial grouping result, and when the initial grouping result is that the grouping is successful, the initial server cluster is as shown in fig. 7, where the server 10.0.1.1, the 10.0.1.2 home cluster "nginx", the server 10.0.1.3, the 10.0.1.4 home cluster "business", the server 10.0.1.9 home cluster "voicedb", the server 10.0.1.10 home cluster "imagedb", the server 10.0.1.5 home cluster "tomcat", and the server 10.0.1.6, 10.0.1.7, 10.0.1.8 home cluster "fastdfs".
Step S204: and carrying out cluster merging on the initial server cluster based on a preset cluster use rule to obtain a server cluster topological graph.
It can be understood that, cluster merging is performed on the initial server cluster based on the preset cluster use rule, the obtained server cluster topological graph may be based on the class C of the existing ontology, the instance I and the grouped cluster CL, and the cluster merging optimization is performed according to the preset cluster use rule. The merging optimization can be merging edges of the same-purpose cluster in the cluster topology.
It should be noted that the preset cluster usage rule may be preset by a manager of the service system architecture diagram generation device. In a specific implementation, the preset cluster usage rule may be as follows, which is not limited by this embodiment.
Rule 7 may be class C for ontology, cluster topology G ═ (CL, E), if CLi、CLjEdge E ofiAnd EjAre identical and CLi＝Cm，CLj＝Cn，CmAnd CnHaving a common parent class CoThen CLiAnd CLjCan be combined into CLoHere CLo＝Co。
Rule 8 may be instance I for an ontology, cluster topology G ═ (CL, E), if CLi、CLjEdge E ofiAnd EjAre identical and CLi＝Im，CLj＝In，ImAnd InAre all CoExample of (1), then CLiAnd CLjCan be combined into CLoHere CLo＝Co。
For ease of understanding, the description will be made with reference to fig. 5, 7, and 8, but this scheme is not limited thereto. FIG. 8 is a server cluster topology diagram, based on class C (FIG. 5), instance I (FIG. 5) and grouped cluster CL (FIG. 7) of the existing ontology, according to rule 8, "voicedb" and "imagedb" are all instances of "mysql" and their edges are identical, merging them. The cluster merge optimization is shown in fig. 8.
The second embodiment obtains usage description characters by extracting characters of a host name, groups servers according to the usage description characters and a domain main body to obtain an initial grouping result, determines an initial server cluster according to the initial grouping result when the initial grouping result is successful, and performs cluster merging on the initial server cluster based on a preset cluster usage rule to obtain a server cluster topological graph; compared with the prior art that the organization structure is positioned by acquiring the server interaction data after the codes are embedded or calculating the server similarity based on the data of a big data platform, the method is realized by utilizing the interaction data after the operation of the business system, has certain delay and has larger workload in the early stage. Because the semantic characteristics of the ontology and the standardized host name are used as entry points in this embodiment, before the service system is deployed, the servers are grouped and positioned according to the defined rules based on the domain ontology, the host name and the inter-cluster contact. A company only needs to construct a field body, and with the continuous addition and perfection of the field body, the new business system almost does not need to modify the field body, and the organizational structure positioning can be quickly realized.
Referring to fig. 9, fig. 9 is a flowchart illustrating a method for generating a business system architecture diagram according to a third embodiment of the present invention, and the third embodiment of the business system architecture diagram generating method according to the present invention is proposed based on the second embodiment illustrated in fig. 6.
In the third embodiment, the step S30 includes:
step S301: and extracting a set of server clusters to be layered from the server cluster topological graph.
It should be noted that, in this embodiment, before execution, the layered server cluster set is empty, and all clusters are in the server cluster set to be layered.
It will be appreciated that an initial cluster level value may also need to be set for each cluster to perform subsequent operations.
For ease of understanding, the description will be made with reference to fig. 10, but this scheme is not limited thereto. Fig. 10 is an architecture diagram of cluster level initial values, a to-be-layered server cluster CL _ level ═ { nginx, bussiness, tomcat, mysql, fastdfs }, and a layered server cluster set CL _ level ═ NULL, where a cluster level value of each cluster is set to 1, 1 represents a level of a bottom layer, and the higher the number is, the higher the level is.
Step S302: and acquiring the out-degree of each server cluster to be layered in the server cluster set to be layered, and selecting a target server cluster from the server cluster set to be layered according to the out-degree.
In the directed graph, the number of edges of a vertex is the degree of departure of the vertex. In this embodiment, the out-degree may be the number of clusters pointed to by the server cluster to be layered.
It should be understood that, the obtaining of the out-degree of each server cluster to be layered in the server cluster set to be layered, and the selecting of the target server cluster from the server cluster set to be layered according to the out-degree may be to use the server cluster with the out-degree of 0 as the target server cluster. This is because the cluster with out-degree 0 has already computed its hierarchy and does not need to continue to participate in the hierarchy.
Step S303: and acquiring a target cluster level value of the target server cluster.
It should be understood that the target cluster hierarchy value is used to indicate the cluster level at which the target server cluster is located, with larger numbers being higher levels.
Step S304: and adding the target server cluster into a layered server cluster set, and deleting the target server cluster from the server cluster set to be layered.
It should be understood that the cluster with out degree of 0 has already calculated its hierarchy, and therefore, may be removed from the server cluster set to be layered and added to the layered server cluster set.
Further, in order to enable the server clusters in the server cluster set to be layered when the server clusters still exist in the server cluster set to be layered, the server clusters in the server cluster set to be layered are layered continuously. After the step S304, the method further includes:
when the server cluster set to be layered is not a preset empty set, adjusting the target cluster level value to obtain a cluster level value to be added;
adjusting the cluster level value of a server cluster to be processed in the server cluster set to be layered according to the cluster level value to be added, wherein the server cluster to be processed points to the target server cluster;
and returning to the step of obtaining the output degree of each server cluster to be layered in the server cluster set to be layered, and selecting a target server cluster from the server cluster set to be layered according to the output degree.
It should be understood that when the set of server clusters to be layered is not a preset empty set, it indicates that the server clusters in the set of server clusters to be layered are not layered. At this time, the cluster level values of other server clusters in the server cluster set to be layered need to be adjusted.
For ease of understanding, the description will be made with reference to fig. 11, but this scheme is not limited thereto. Fig. 11 is a schematic diagram illustrating adjustment of cluster hierarchy values, where in a cluster set CL _ level of a server to be layered, a target cluster hierarchy value of a cluster "mysql" and "fastdfs" with an out-degree of 0 is a maximum value of respective corresponding cluster hierarchy values, that is, levelmysql is 1 and levelfastfs is 1. And (3) moving the clusters 'mysql' and 'fastdfs' with the out-degree of 0 from CL _ Levelu to CL _ Levelo, wherein the CL _ Levelu is { nginx, business, tomcat }, and the CL _ Levelo is { mysql, fastdfs }. The layered clusters and the edges thereof are all removed from the cluster set of the server to be layered, and the edges are represented by dotted lines. At this time, the cluster set of the server to be layered is not an empty set. Therefore, the cluster level value +1 (i.e., 2) of the clusters "mysql" and "fastdfs" with out degree of 0 needs to be added to the cluster level values of the cluster "business" pointing to "mysql" and the cluster "tomcat" pointing to "fastdfs", as shown in fig. 11.
Step S305: and when the cluster set of the servers to be layered is a preset empty set, generating a business system architecture diagram according to the layered cluster set of the servers and the target cluster level value.
It can be understood that, when the set of server clusters to be layered is a preset empty set, generating a service system architecture diagram according to the layered server cluster set and the target cluster level value may be that, when the set of server clusters to be layered is a preset empty set, ranking each server cluster in the layered server cluster set according to the target cluster level value, determining a target level position of each server cluster in the layered server cluster set according to the ranking result, and adjusting the architecture diagram position of each server cluster in the layered server cluster set based on the target level position to obtain the service system architecture diagram.
For ease of understanding, reference is made to fig. 10-14, which are not intended to limit the present solution. Fig. 10 is an architecture diagram of initial values of cluster hierarchy, and fig. 11 to 14 are schematic diagrams of adjusting cluster hierarchy values. The step of carrying out hierarchical positioning on the server cluster topological graph to obtain the service system architecture graph of the service system to be processed is as follows:
step 1: determining an initial state: CL _ Level of server cluster to be layeredu{ nginx, business, tomcat, mysql, fastdfs }, hierarchical server cluster set CL _ Levelo＝NULL。
The cluster level value of each cluster is set to 1, 1 represents the lowest level, and the higher the number, the higher the level, as shown in fig. 10.
Step 2: server cluster set CL _ Level to be layereduIn the method, the target cluster level values of the clusters with the out-degree of 0, namely mysql and fastdfs, take the maximum value, namely level, of the corresponding cluster level valuesmysql＝1，level fastdfs1. The clusters 'mysql' and 'fastdfs' with the out degree of 0 are changed from CL _ LeveluMove to CL _ LeveloMiddle, CL _ Levelu＝{nginx,business,tomcat}，CL_Levelo= mysql, fastdfs }. The layered clusters and the edges thereof are all removed from the cluster set of the server to be layered, and the edges are represented by dotted lines. At this time, the cluster set of the server to be layered is not an empty set. Therefore, the cluster level value +1 (i.e., 2) of the clusters "mysql" and "fastdfs" with out degree of 0 needs to be added to the cluster level values of the cluster "business" pointing to "mysql" and the cluster "tomcat" pointing to "fastdfs", as shown in fig. 11.
And 3, step 3: server cluster set CL _ Level to be layereduThe maximum value of the cluster level values, namely level, is taken as the target cluster level value of the cluster 'business' with the out-degree of 0businessMax (1,2) 2. The cluster 'bussiness' with the out degree of 0 is driven from CL _ LeveluMove to CL _ LeveloMiddle, CL _ Levelu＝{nginx,tomcat}，CL_Levelo= mysql, fastdfs, business }. At this time, the cluster set of the server to be layered is not an empty set. Therefore, the cluster level +1 (i.e., 3) of the cluster "business" with the out degree of 0 needs to be added to the cluster level values of the clusters "nginx" and "tomcat" pointing to "business", as shown in fig. 12.
And 4, step 4: server cluster set CL _ Level to be layereduIn the method, the target cluster level value of the cluster "tomcat" with the out-degree of 0 takes the maximum value in the cluster level values, namely leveltomcatMax (1,2,3) is 3. The cluster 'tomcat' with the out degree of 0 is driven from CL _ LeveluMove to CL _ LeveloIn this case, CL _ Levelu＝{nginx}，CL_Levelo= mysql, fastdfs, business, tomcat }. At this time, the cluster set of the server to be layered is not an empty set. Therefore, the cluster level +1 (i.e., 4) of the cluster "tomcat" with out 0 needs to be added to the cluster level value of the cluster "nginx" pointing to "tomcat", as shown in fig. 13.
And 5: server cluster set CL _ Level to be layereduIn the cluster with out-degree of 0, the target cluster level value of the "nginx" takes the maximum value of the cluster level values, namely levelnginxMax (1,3,4) is 4. This step is fingerlessTo the cluster of "nginx", continue to take the cluster of "nginx" whose out degree is 0 from CL _ LeveluMove to CL _ LeveloIn this case, CL _ Levelu＝NULL，CL_Levelo= mysql, fastdfs, business, tomcat, nginx. To-be-layered cluster set CL _ LeveluNow empty, the algorithm ends. After adjusting the hierarchy according to the target cluster hierarchy value of each cluster, a service system architecture diagram of the service system to be processed is formed, as shown in fig. 14.
The third embodiment extracts a server cluster set to be layered from a server cluster topological graph, obtains the degree of departure of each server cluster to be layered in the server cluster set to be layered, selects a target server cluster from the server cluster set to be layered according to the degree of departure, obtains a target cluster level value of the target server cluster, adds the target server cluster into the layered server cluster set, deletes the target server cluster from the server cluster set to be layered, and generates a service system architecture graph according to the layered server cluster set and the target cluster level value when the server cluster set to be layered is a preset empty set; compared with the prior art, the method is complex by determining a plurality of algorithms of the cluster which only serves as the server side, the same-layer cluster subdivision layer, the cluster level positioning, the similarity matrix calculation similarity and the like. Since the present embodiment surrounds 3 types of sets, i.e., the set of clusters to be layered, the layered set and the candidate level set of each cluster, the algorithm of the present application starts with the cluster with the out degree of 0, gradually takes the maximum value of the candidate level set to determine the level of the cluster with the out degree of 0, gradually takes the level value +1 of the cluster with the out degree of 0 to add to the cluster candidate level set pointing to the cluster, and repeats the above operations until the set of clusters to be layered is empty, thereby increasing the level location speed and improving the level location accuracy.
In addition, an embodiment of the present invention further provides a storage medium, where a service system architecture diagram generation program is stored in the storage medium, and the service system architecture diagram generation program, when executed by a processor, implements the steps of the service system architecture diagram generation method described above.
In addition, referring to fig. 15, an embodiment of the present invention further provides a business system architecture diagram generating device, where the business system architecture diagram generating device includes: an acquisition module 10, a grouping module 20 and a layering module 30;
the acquiring module 10 is configured to acquire a domain main body and a server corresponding to a to-be-processed service system, and acquire a host name of the server;
the grouping module 20 is configured to group the servers according to the host name and the domain subject to obtain a server cluster topological graph;
the layering module 30 is configured to perform hierarchical positioning on the server cluster topological graph to obtain a service system architecture graph of the service system to be processed.
The method comprises the steps of obtaining a domain main body and a server corresponding to a service system to be processed, obtaining a host name of the server, grouping the servers according to the host name and the domain main body to obtain a server cluster topological graph, and carrying out hierarchical positioning on the server cluster topological graph to obtain a service system architecture graph of the service system to be processed; the invention does not need to draw the architecture diagram of the service system manually, but carries out grouping positioning on the servers based on the name of the server host of the service system to be processed and the domain main body so as to obtain the architecture diagram of the service system to be processed, thereby being capable of quickly and effectively generating the architecture diagram of the service system and ensuring the reliability of the architecture diagram of the service system.
Other embodiments or specific implementation manners of the apparatus for generating a business system architecture diagram according to the present invention may refer to the above method embodiments, and are not described herein again.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in the process, method, article, or system in which the element is included.
The above-mentioned serial numbers of the embodiments of the present invention are only for description, and do not represent the advantages and disadvantages of the embodiments. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, third, etc. do not denote any order, but rather the words first, second, third, etc. are to be interpreted as names.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention or portions thereof that contribute to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium (e.g., a Read Only Memory (ROM)/Random Access Memory (RAM), a magnetic disk, an optical disk), and includes several instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (9)
1. A method for generating a business system architecture diagram is characterized by comprising the following steps:
acquiring a domain main body and a server corresponding to a service system to be processed, and acquiring a host name of the server;
grouping the servers according to the host names and the domain main bodies to obtain a server cluster topological graph;
carrying out hierarchical positioning on the server cluster topological graph to obtain a service system architecture graph of the service system to be processed;
wherein, the step of performing hierarchical positioning on the server cluster topological graph to obtain the service system architecture graph of the service system to be processed specifically includes:
extracting a server cluster set to be layered from the server cluster topological graph;
obtaining the out-degree of each server cluster to be layered in the server cluster set to be layered, and selecting a target server cluster from the server cluster set to be layered according to the out-degree;
acquiring a target cluster level value of the target server cluster;
adding the target server cluster into a layered server cluster set, and deleting the target server cluster from the server cluster set to be layered;
and when the cluster set of the servers to be layered is a preset empty set, generating a business system architecture diagram according to the layered cluster set of the servers and the target cluster level value.
2. The business system architecture diagram generation method of claim 1, wherein after the step of adding the target server cluster to a set of layered server clusters and deleting the target server cluster from the set of to-be-layered server clusters, the business system architecture diagram generation method further comprises:
when the cluster set of the server to be layered is not a preset empty set, adjusting the level value of the target cluster to obtain a level value of a cluster to be added;
adjusting the cluster level value of a server cluster to be processed in the server cluster set to be layered according to the cluster level value to be added, wherein the server cluster to be processed points to the target server cluster;
and returning to the step of obtaining the output degree of each server cluster to be layered in the server cluster set to be layered, and selecting a target server cluster from the server cluster set to be layered according to the output degree.
3. The method for generating a business system architecture diagram according to claim 1, wherein the step of generating a business system architecture diagram according to the layered server cluster set and the target cluster hierarchy value when the to-be-layered server cluster set is a preset empty set specifically includes:
when the server cluster set to be layered is a preset empty set, sorting each server cluster in the layered server cluster set according to the target cluster level value;
determining the target hierarchical position of each server cluster in the hierarchical server cluster set according to the sorting result;
and adjusting the position of the architecture diagram of each server cluster in the layered server cluster set based on the target level position to obtain a service system architecture diagram.
4. The method for generating a business system architecture diagram according to any one of claims 1 to 3, wherein the step of grouping the servers according to the host names and the domain subjects to obtain a server cluster topology diagram specifically includes:
extracting characters from the host name to obtain usage description characters;
grouping the servers according to the application description characters and the domain main body to obtain an initial grouping result;
when the initial grouping result is successful, determining an initial server cluster according to the initial grouping result;
and carrying out cluster merging on the initial server cluster based on a preset cluster use rule to obtain a server cluster topological graph.
5. The method for generating a business system architecture diagram according to claim 4, wherein after the step of grouping the servers according to the usage description characters and the domain master to obtain an initial grouping result, the method for generating a business system architecture diagram further comprises:
when the initial grouping result is that grouping fails, generating reminding information, and receiving domain main body supplementary information fed back by a user based on the reminding information;
and updating the domain main body corresponding to the service system to be processed according to the domain main body supplementary information, returning to the step of acquiring the domain main body and the server corresponding to the service system to be processed, and acquiring the host name of the server.
6. The method for generating a business system architecture diagram according to claim 4, wherein the step of grouping the servers according to the application description characters and the domain master to obtain an initial grouping result specifically includes:
generating a cluster attribution label of each server according to a preset grouping rule, the use description character and the domain main body;
and grouping the servers according to the cluster attribution label to obtain an initial grouping result.
7. A business system architecture diagram generation apparatus, characterized by comprising: a memory, a processor and a business system architecture diagram generation program stored on the memory and executable on the processor, the business system architecture diagram generation program when executed by the processor implementing the steps of the business system architecture diagram generation method as claimed in any one of claims 1 to 6.
8. A storage medium, characterized in that the storage medium has stored thereon a business system architecture diagram generation program, which when executed by a processor implements the steps of the business system architecture diagram generation method according to any one of claims 1 to 6.
9. A business system architecture diagram generation apparatus, comprising: the device comprises an acquisition module, a grouping module and a layering module;
the acquisition module is used for acquiring a domain main body and a server corresponding to the service system to be processed and acquiring a host name of the server;
the grouping module is used for grouping the servers according to the host names and the domain main bodies to obtain a server cluster topological graph;
the layering module is used for carrying out layering positioning on the server cluster topological graph so as to obtain a service system architecture graph of the service system to be processed;
the layering module is further used for extracting a server cluster set to be layered from the server cluster topological graph; obtaining the out-degree of each server cluster to be layered in the server cluster set to be layered, and selecting a target server cluster from the server cluster set to be layered according to the out-degree; acquiring a target cluster level value of the target server cluster; adding the target server cluster into a layered server cluster set, and deleting the target server cluster from the server cluster set to be layered; and when the cluster set of the servers to be layered is a preset empty set, generating a business system architecture diagram according to the layered cluster set of the servers and the target cluster level value.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110669013.8A CN113364632B (en) | 2021-06-16 | 2021-06-16 | Method, device, storage medium and apparatus for generating architecture diagram of service system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110669013.8A CN113364632B (en) | 2021-06-16 | 2021-06-16 | Method, device, storage medium and apparatus for generating architecture diagram of service system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113364632A CN113364632A (en) | 2021-09-07 |
| CN113364632B true CN113364632B (en) | 2022-07-01 |
Family
ID=77534712
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110669013.8A Active CN113364632B (en) | 2021-06-16 | 2021-06-16 | Method, device, storage medium and apparatus for generating architecture diagram of service system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113364632B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109783568A (en) * | 2018-12-29 | 2019-05-21 | 咪咕文化科技有限公司 | A kind of generation method of network topological diagram, device and storage medium |
| CN110597789A (en) * | 2019-09-19 | 2019-12-20 | 泰康保险集团股份有限公司 | Automatic generation method, device and equipment of architecture diagram and computer readable storage medium |
| CN111639120A (en) * | 2020-06-05 | 2020-09-08 | 中国建设银行股份有限公司 | Method, device and equipment for forming graph of architecture view and readable storage medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140160979A1 (en) * | 2012-12-12 | 2014-06-12 | Futurewei Technologies, Inc. | Determination and Visualization of Hierarchical Network Topology |
| CN109450677B (en) * | 2018-10-29 | 2021-07-13 | 中国联合网络通信集团有限公司 | Method and device for positioning root fault |
| CN110287987B (en) * | 2019-05-16 | 2021-06-25 | 北京交通大学 | Method for discovering hierarchical organization structure of business system with hierarchical network structure |
| CN111181769B (en) * | 2019-12-11 | 2023-04-07 | 中移（杭州）信息技术有限公司 | Network topological graph drawing method, system, device and computer readable storage medium |
| CN111831548B (en) * | 2020-05-29 | 2024-04-05 | 微民保险代理有限公司 | Dependency relationship topological graph drawing method and device |
-
2021
- 2021-06-16 CN CN202110669013.8A patent/CN113364632B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109783568A (en) * | 2018-12-29 | 2019-05-21 | 咪咕文化科技有限公司 | A kind of generation method of network topological diagram, device and storage medium |
| CN110597789A (en) * | 2019-09-19 | 2019-12-20 | 泰康保险集团股份有限公司 | Automatic generation method, device and equipment of architecture diagram and computer readable storage medium |
| CN111639120A (en) * | 2020-06-05 | 2020-09-08 | 中国建设银行股份有限公司 | Method, device and equipment for forming graph of architecture view and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113364632A (en) | 2021-09-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2015055067A1 (en) | Method and apparatus for pushing messages | |
| US20220036175A1 (en) | Machine learning-based issue classification utilizing combined representations of semantic and state transition graphs | |
| US20210390496A1 (en) | Method for model-based project scoring classification and reporting | |
| CN109063838B (en) | Knowledge model servization and flow customization system | |
| CN113094560A (en) | Data label library construction method, device, equipment and medium based on data middlebox | |
| CN114021156A (en) | Method, device and equipment for organizing vulnerability automatic aggregation and storage medium | |
| CN112765127B (en) | Construction method and device of traffic data warehouse, storage medium and terminal | |
| US20220092470A1 (en) | Runtime estimation for machine learning data processing pipeline | |
| CN113364632B (en) | Method, device, storage medium and apparatus for generating architecture diagram of service system | |
| CN111324594A (en) | Data fusion method, device, equipment and storage medium for grain processing industry | |
| CN111858617A (en) | User searching method and device, computer readable storage medium and electronic equipment | |
| US20220164377A1 (en) | Method and apparatus for distributing content across platforms, device and storage medium | |
| CN113344074B (en) | Model training method, device, equipment and storage medium | |
| CN109949090A (en) | Lead referral method, apparatus, electronic equipment and medium | |
| CN115204971A (en) | Product recommendation method and device, electronic equipment and computer-readable storage medium | |
| CN112818223A (en) | Query processing method, device, equipment, program product and medium for user portrait | |
| CN113760695A (en) | Method and device for positioning problem code | |
| CN111310090A (en) | Content data management system, method, equipment and storage medium of website page | |
| CN111552847A (en) | Method and device for changing number of objects | |
| CN113364775B (en) | Calling method and device of microservice and server | |
| CN115221205B (en) | Policy determination method, device and storage medium | |
| US11947504B1 (en) | Multi-cloud data processing and integration | |
| CN113760267A (en) | Conditional rule multiplexing method based on interactive rule engine | |
| CN113722016A (en) | Application program configuration method, device, equipment, storage medium and program product | |
| CN116089617A (en) | Statistical result output method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |