Application relation topological graph drawing method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention discloses an application relation topological graph drawing method and device, electronic equipment and a storage medium. The method comprises the steps of obtaining each piece of subscription information data and each piece of registration information data registered by a registration center; obtaining a consumer application and a subscription service corresponding to each piece of subscription information data, and respectively determining the consumer application and the subscription service corresponding to the same piece of subscription information data as an associated calling party application and a called party service; acquiring associated registration information data of each calling party application from each registration information data based on the associated called party service, and acquiring a provider application corresponding to the associated registration information data as a called party application associated with the corresponding calling party application; the application relation topological graph is drawn on the basis of the incidence relation between all the calling party applications and the relevant called party applications. According to the embodiment of the invention, the drawing accuracy and the drawing efficiency when the application relation topology is drawn can be improved.

Description

Technical Field

[0001] The present invention relates to the technical field of computer application systems, and particularly to a method, device, electronic device and storage medium for drawing an application relationship topology diagram. Background Art

[0002] With the widespread application of the microservices architecture (i.e., a technology for deploying applications and services in the cloud), in the application system of the microservices architecture, there are many system objects, many types, and complex call relationships. When operation and maintenance personnel perform operation and maintenance and architects perform system reconstruction and architecture adjustment, they rely on accurate inter-application topology relationship information.

[0003] The prior art mainly draws the application relationship topology diagram through a metadata system. However, when drawing the application relationship topology diagram through the metadata system, due to the differences between the corresponding metadata system and the actual production situation, the data accuracy is poor, resulting in a low accuracy rate of the drawing result of the application relationship topology diagram; and because the data storage of the data system is usually designed according to management needs for table structures and data storage, the associated data is usually scattered in multiple tables, and the steps of querying data are complex and the efficiency is low, resulting in a low drawing efficiency of the application relationship topology diagram. Summary of the Invention

[0004] Embodiments of the present invention provide a method, device, electronic device and storage medium for drawing an application relationship topology diagram, which can improve the drawing accuracy rate and drawing efficiency when drawing the application relationship topology.

[0005] In a first aspect, an embodiment of the present invention provides a method for drawing an application relationship topology diagram, including:

[0006] Obtaining each piece of subscription information data and each piece of registration information data registered in the registration center of the microservices application system;

[0007] Obtaining the consumer application and subscription service corresponding to each piece of subscription information data, and respectively determining the consumer application and subscription service corresponding to the same piece of subscription information data as the associated calling application and called service;

[0008] Based on the associated called service, obtaining the associated registration information data of each calling application from the above-mentioned each piece of registration information data, and obtaining the provider application corresponding to the associated registration information data as the called application associated with the corresponding calling application; and

[0009] Drawing the application relationship topology diagram of the microservices application system based on the association relationship between each calling application and the associated called application.

[0010] In a second aspect, an embodiment of the present invention provides an apparatus for drawing an application relationship topology diagram, characterized by including:

[0011] A data acquisition module, configured to acquire each piece of subscription information data and each piece of registration information data registered in the registration center of the microservice application system;

[0012] A first association relationship acquisition module, configured to acquire the consumer application and the subscription service corresponding to each piece of the subscription information data, and respectively determine the consumer application and the subscription service corresponding to the same piece of subscription information data as the associated calling application and the called service;

[0013] A second association relationship acquisition module, configured to acquire the associated registration information data of each calling application from the each piece of registration information data based on the associated called service, and acquire the provider application corresponding to the associated registration information data as the called application associated with the corresponding calling application; and

[0014] A drawing module, configured to draw an application relationship topology diagram of the microservice application system based on the association relationship between each calling application and the associated called application.

[0015] In a third aspect, an embodiment of the present invention further provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the application relationship topology diagram drawing method according to any one of the embodiments of the present invention is implemented.

[0016] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, the application relationship topology diagram drawing method according to any one of the embodiments of the present invention is implemented.

[0017] The method, device, electronic device, and storage medium for drawing an application relationship topology diagram provided by the embodiments of the present invention obtain each piece of subscription information data and each piece of registration information data from the registration center of the microservice application system, and determine the associated calling application and called application based on the consumer application and subscription service included in each piece of subscription information data, and the information of the subscribed service and provider application included in each piece of registration information data. Furthermore, based on the association relationship between the calling application and the called application, an application relationship topology diagram of the microservice application system is drawn. It can determine the accurate call association relationship between applications based on accurate and immediate subscription information data and registration information data. And since there is no need to obtain the data required for drawing from table structures with diverse structures, the steps for obtaining the data for drawing are few and efficient. Thus, it can improve the drawing accuracy and efficiency when drawing the application relationship topology, and further facilitate quickly and accurately evaluating the scope of the impact of a fault in the microservice application system and improving the emergency response timeliness. In addition, it can also facilitate providing accurate global perspective supporting data for architects when they reconstruct the system and adjust the architecture, so that architects can conveniently evaluate the impact of the architecture adjustment and accurately evaluate the rationality of the system design. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions of the present invention, the accompanying drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as limiting the scope. For those of ordinary skill in the art, other related drawings can be obtained based on these drawings without creative efforts.

[0019] Figure 1 is a flowchart of the method for drawing an application relationship topology diagram provided by the embodiments of the present invention;

[0020] Figure 2 is another flowchart of the method for drawing an application relationship topology diagram provided by the embodiments of the present invention;

[0021] Figure 3 is another flowchart of the method for drawing an application relationship topology diagram provided by the embodiments of the present invention;

[0022] Figure 4 is another flowchart of the method for drawing an application relationship topology diagram provided by the embodiments of the present invention;

[0023] Figure 5 is a structural diagram of the device for drawing an application relationship topology diagram provided by the embodiments of the present invention;

[0024] Figure 6 is a structural diagram of the electronic device provided by the embodiments of the present invention. Detailed implementation manner

[0025] In order to enable those skilled in the art to better understand the solution of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0026] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily need to describe a specific order or sequence. It should be understood that such data used can be interchanged under appropriate circumstances so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device including a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0027] Figure 1 FIG. is a schematic flowchart of a method for drawing an application relationship topology diagram provided by an embodiment of the present invention. This embodiment is applicable to the scenario of drawing an inter-application relationship topology diagram of a microservice application system. This method can be executed by an application relationship topology diagram drawing device provided by an embodiment of the present invention, and the device can be implemented in software and / or hardware. In a specific embodiment, the device can be integrated in an electronic device, such as a computer, a server, etc. The following embodiments will be described by taking the integration of the device in an electronic device as an example. Refer to Figure 1 , the method may specifically include the following steps:

[0028] Step 101, obtain each piece of subscription information data and each piece of registration information data registered in the registration center of the microservice application system. This step can obtain accurate and up-to-date subscription information data and registration information data, which is conducive to obtaining the association relationship between the consumer application, subscription service, and provider application corresponding to the subscription information data and registration information data as the caller or the callee.

[0029] Specifically, the above-mentioned microservice application system may be, for example, a microservice application system of an e-bank.

[0030] Specifically, in a microservices architecture, the registry stores the registration information of all services. Usually, the service providers and consumers are both referred to as applications. The registration information of a service includes the address of the provider application. The consumer application obtains the address of the provider application of the required service by subscribing to the service. The application registration service or subscription service is implemented through communication with the registry client deployed on the application side.

[0031] Specifically, each of the above subscription information data can be understood as a piece of subscription information written when a consumer application subscribes to a service. For example:

[0032] "consumer: / / xxxxip / xxxservice?application=app1&interface=xxx".

[0033] Specifically, each of the above registration information data can be understood as a piece of registration information written when a provider application registers a service. For example:

[0034] "dubbo: / / xxip:xxport / service?application=app2&interface=xxx".

[0035] Optionally, the above registry includes multiple types of registries.

[0036] Specifically, the types of the above multiple registries can be understood as the product types of different registry products.

[0037] Specifically, the above registry can also include only one type of registry.

[0038] Optionally, the process of obtaining each piece of subscription information data and each piece of registration information data registered in the registry of the microservices application system includes: using a pre-designed data synchronization device to obtain the above-mentioned each piece of subscription information data and each piece of registration information data through the data read-write interface of the registry.

[0039] Optionally, the process of obtaining each piece of subscription information data and each piece of registration information data registered in the registry of the microservices application system includes: obtaining the above-mentioned each piece of subscription information data and each piece of registration information data according to the application dimension or the service dimension.

[0040] Step 102: Obtain the consumer application and the subscribed service corresponding to each piece of subscription information data, and respectively determine the consumer application and the subscribed service corresponding to the same piece of subscription information data as the associated calling application and the called service. This step can obtain the association relationship when the consumer application and the subscribed service corresponding to the subscription information data are used as the calling application and the called service respectively.

[0041] Optionally, the process of obtaining the consumer application and subscription service corresponding to each piece of subscription information data includes:

[0042] Identifying the positioning marks of the consumer application identifier and subscription service identifier in the subscription information data; and obtaining the consumer application identifier and subscription service identifier based on the corresponding positioning marks, and correspondingly determining the consumer application and subscription service based on the consumer application identifier and subscription service identifier.

[0043] Optionally, the process of identifying the positioning marks of the consumer application identifier and subscription service identifier in the subscription information data includes:

[0044] Identifying the positioning marks of the consumer application identifier and subscription service identifier in the subscription information data based on the type of the registration center.

[0045] It can be understood that since the formats of the subscription information data on the registration centers of different product types are different. Therefore, it is necessary to obtain the positioning marks of the consumer application identifier and subscription service identifier from the subscription information data based on the data format corresponding to the type of the registration center.

[0046] In a specific example, for the subscription information data:

[0047] "consumer: / / xxxxip / xxxservice?application=app1&interface=xxx" identifies the positioning mark "application=" of the consumer application identifier and the positioning mark "interface=" of the subscription service identifier, and obtains the characters after the corresponding positioning marks to obtain the consumer application identifier and subscription service identifier.

[0048] Specifically, it is also possible to first determine the data characteristics of the consumer application identifier and subscription service identifier, and then obtain the consumer application identifier and subscription service identifier based on the corresponding data characteristics.

[0049] Specifically, obtaining the consumer application identifier and subscription service identifier based on the corresponding positioning marks can help improve the efficiency of obtaining the consumer application identifier and subscription service identifier, and identifying the positioning marks based on the type of the registration center can help improve the identification accuracy and efficiency.

[0050] Step 103: Obtain the associated registration information data of each calling party application from each piece of registration information data based on the associated called party service, and obtain the provider application corresponding to the associated registration information data as the called party application associated with the corresponding calling party application. This step can obtain the association relationship between the calling party application associated with the service registered when obtaining the provider application corresponding to the registration information data as the called party application.

[0051] Optionally, the process of obtaining the provider application corresponding to the associated registration information data includes:

[0052] Identifying the positioning mark of the provider application identifier in the associated registration information data; and obtaining the provider application identifier based on the corresponding positioning mark, and determining the provider application based on the provider application identifier.

[0053] Optionally, the process of identifying the positioning mark of the provider application identifier in the associated registration information data includes: identifying the positioning mark of the provider application identifier in the associated registration information data based on the type of the registration center.

[0054] It can be understood that since the formats of the registration information data on the registration centers of different product types are different. Therefore, it is necessary to obtain the positioning mark of the provider application identifier from the registration information data based on the data format corresponding to the type of the registration center.

[0055] In a specific example, for the registration information data:

[0056] "dubbo: / / xxip:xxport / service?application=app2&interface=xxx" identifies the positioning mark "application=" of the provider application identifier, and obtains the characters after the corresponding positioning mark to obtain the provider application identifier.

[0057] Specifically, it is also possible to first determine the data characteristics of the provider application identifier, and then obtain the provider application identifier based on the corresponding data characteristics.

[0058] Specifically, obtaining the provider application identifier based on the corresponding positioning mark can help improve the efficiency of obtaining the consumer application identifier and the subscribed service identifier, and identifying the positioning mark based on the type of the registration center can help improve the identification accuracy and efficiency.

[0059] Optionally, step 102 and step 103 can be executed by a pre-designed data cleaning device, which can be used to clean up the data irrelevant to the topology after obtaining the consumer application representation, subscribed service representation, and provider application identifier related to the topology, and form a formatted data format, such as {"appa": "appb"}.

[0060] Step 104: Draw an application relationship topology diagram of the microservice application system based on the association relationships between various calling party applications and associated called party applications. Based on Steps 101 to 103, in this step, by obtaining each piece of subscription information data and each piece of registration information data from the registration center of the microservice application system, and based on the consumer applications and subscribed services included in each piece of subscription information data, as well as the information of the subscribed services and provider applications included in each piece of registration information data, determine the associated calling party applications and called party applications. Furthermore, draw an application relationship topology diagram of the microservice application system based on the association relationships between the calling party applications and the called party applications. It can determine the accurate inter-application call association relationships based on accurate and up-to-date subscription information data and registration information data. And since there is no need to obtain the data required for drawing from table structures with diverse structures, the steps for obtaining drawing data are few and efficient, thereby improving the drawing accuracy and efficiency when drawing the application relationship topology, and further facilitating quickly and accurately assessing the scope of the impact of a failure in the microservice application system and improving the emergency response timeliness. In addition, it can also facilitate providing accurate global perspective corroborative data for the architect when the architect reconstructs the system and adjusts the architecture, so as to facilitate the architect to conveniently assess the impact scope of the architecture adjustment and accurately assess the rationality of the system design.

[0061] It should be noted that the same application can serve as both a calling party application and a called party application.

[0062] Optionally, the process of drawing an application relationship topology diagram of the microservice application system based on the association relationships between various calling party applications and associated called party applications includes: determining the importance levels of each calling party application and called party application based on the association relationships between the calling party applications and the called party applications, and drawing topology diagram nodes representing each calling party application and the associated called party applications based on the corresponding importance levels.

[0063] Optionally, the process of drawing an application relationship topology diagram of the microservice application system based on the association relationships between various calling party applications and associated called party applications includes: drawing an application relationship topology diagram of the microservice application system based on the association relationships between the calling party applications and the called party applications, and the association relationships between the calling party applications and the called party services.

[0064] Specifically, adding the association relationship between the called party service and the calling party application in the application relationship topology diagram can display the association relationships between services in a more fine-grained manner, thereby more precisely conducting emergency response to failures when they occur, and facilitating the architect to optimize and adjust the system architecture based on the fine-grained association relationships.

[0065] Optionally, the process of drawing the application relationship topology diagram of the microservice application system based on the association relationship between the calling application and the called application, and the association relationship between the calling application and the called service includes: drawing topology diagram nodes representing each calling application, each called service, and each called application, and drawing connections between the corresponding topology diagram nodes based on the association relationship between the calling application and the called application, and the association relationship between the calling application and the called service, to obtain the above application relationship topology diagram.

[0066] The following further introduces the application relationship topology diagram drawing method provided by the embodiments of the present invention. As Figure 2 shown, that is Figure 1 step 104 in can include the following steps:

[0067] Step 1041, draw topology diagram nodes representing each calling application and each associated called application.

[0068] Optionally, the process of drawing topology diagram nodes representing each calling application and each associated called application includes: drawing topology diagram nodes representing all applications and services corresponding to the foregoing subscription information data and registration information data.

[0069] It can be understood that the applications corresponding to the foregoing subscription information data and registration information data may be used as calling applications or called applications, and the subscription services corresponding to the subscription information data and registration information data will be used as called services. Therefore, drawing topology diagram nodes representing all applications and services corresponding to the foregoing subscription information data and registration information data can complete the topology diagram nodes representing each calling application and each called application.

[0070] Specifically, all topology diagram nodes can be drawn at one time, and then the connections between the topology diagram nodes of the associated calling application and called application are drawn. It is also possible to draw the topology diagram nodes in multiple times, and after completing the drawing of the connections of the topology diagram nodes in the previous time, then draw the topology diagram nodes in the next time.

[0071] Step 1042, generate one-way connections from the topology diagram nodes of each calling application to the topology diagram nodes of the associated called applications to obtain the application relationship topology diagram.

[0072] It can be understood that a calling application may also be used as a called application of other applications.

[0073] In an optional specific embodiment of the present invention, as Figure 3 shown, that is Figure 2 step 1041 in can include the following steps:

[0074] Step 1041A: Determine the importance level of each calling application based on the number of called applications invoked.

[0075] Optionally, the process of determining the importance level of each calling application based on the number of called applications invoked includes: for each calling application, when the number of called applications invoked is greater than the first quantity threshold, determine the importance level of the current calling application as important; otherwise, determine the importance level of the current calling application as normal.

[0076] Optionally, the called applications invoked include directly called applications and indirectly called applications.

[0077] Specifically, the importance level of the corresponding calling application can also be determined as extremely important, important, or normal based on the number of called applications invoked.

[0078] Step 1041B: Determine the node form of the topological graph node of each calling application based on the corresponding importance level.

[0079] Optionally, the process of determining the node form of the topological graph node of each calling application based on the corresponding importance level includes: determine the form of the topological graph node of the more important calling application as the more prominent form. For example, the size of the topological graph node of the more important calling application can be determined as the larger size.

[0080] Step 1041C: Draw the topological graph nodes of each calling application based on the corresponding node form.

[0081] In an optional specific embodiment of the present invention, as Figure 3 shown, that is Figure 2 step 1041 in

[0082] 1041a: Determine the importance level of the corresponding called application based on the number of calling applications that call each called application.

[0083] Optionally, the process of determining the importance level of the corresponding called application based on the number of calling applications that call each called application includes: for each called application, when the number of calling applications that call the current called application is greater than the second quantity threshold, determine the importance level of the current called application as important; otherwise, determine the importance level of the current called application as normal.

[0084] Specifically, the importance level of the current called application can also be determined as extremely important, important, or normal based on the number of calling applications that call the current called application.

[0085] Optionally, the calling party applications that call the called party applications above include the calling party applications that directly and indirectly call the called party applications.

[0086] 1041b. Determine the node form of the topology graph nodes of each called party application based on the corresponding importance level.

[0087] Optionally, the process of determining the node form of the topology graph nodes of each called party application based on the corresponding importance level includes: determining the form of the topology graph nodes of the more important called party applications as the more prominent form. For example, the size of the topology graph nodes of the more important called party applications can be determined as the larger size.

[0088] 1041c. Draw the topology graph nodes of each called party application based on the corresponding node form.

[0089] In an alternative specific embodiment of the present invention, as Figure 4 shown, that is Figure 2 step 1042 in can include the following steps:

[0090] Step 1042A. Determine the importance level of each calling party application based on the number of called party applications called.

[0091] Step 1042B. Determine the connection form of the unidirectional connection lines connecting to the topology graph nodes of the associated called party applications based on the corresponding importance level.

[0092] Optionally, the process of determining the connection form of the unidirectional connection lines connecting to the topology graph nodes of the associated called party applications based on the corresponding importance level includes: determining the unidirectional connection lines corresponding to the more important calling party applications as the thicker connection lines.

[0093] Specifically, the unidirectional connection lines corresponding to calling party applications with different importance levels can also be determined as different colors.

[0094] Step 1042C. Draw the unidirectional connection lines connecting from the topology graph nodes of each calling party application to the topology graph nodes of the associated called party applications based on the corresponding connection form.

[0095] In an alternative specific embodiment of the present invention, as Figure 4 shown, that is Figure 2 step 1042 in can include the following steps:

[0096] Step 1042a. Determine the importance level of the corresponding called party application based on the number of calling party applications that call each called party application.

[0097] Step 1042b: Determine the connection form of the unidirectional connection lines from the topology graph nodes of the calling party application to the topology graph nodes of each called party application based on the corresponding importance level.

[0098] Optionally, the process of determining the connection form of the unidirectional connection lines from the topology graph nodes of the calling party application to the topology graph nodes of each called party application based on the corresponding importance level includes: determining the unidirectional connection line corresponding to the more important called party application as a thicker connection line.

[0099] Specifically, the unidirectional connection lines corresponding to the called party applications with different importance levels can also be determined to have different colors.

[0100] Step 1042c: Draw the unidirectional connection lines from the topology graph nodes of the associated calling party application to the topology graph nodes of each called party application based on the corresponding connection form.

[0101] It can be understood that the more called party applications are called, the more applications the corresponding calling party application depends on. Then, when any of the applications it depends on fails, the calling party application will be affected. Therefore, this calling party application needs to be focused on by the architect. Therefore, determining the importance level of the corresponding calling party application based on the number of called party applications called and drawing the corresponding topology graph nodes according to the importance level can facilitate the architect to evaluate and adjust the architecture.

[0102] In addition, the more calling party applications call a called party application, the more times the called party application is called. Then, once the called party application fails, the associated calling party applications will all be affected. Therefore, this called party application needs to be focused on by the operation and maintenance personnel. Therefore, determining the importance level of the corresponding called party application based on the number of calling party applications calling each called party application and drawing the corresponding topology graph nodes according to the importance level can facilitate the operation and maintenance personnel to perform precise operation and maintenance.

[0103] Figure 5 It is a structural diagram of an application relationship topology graph drawing device provided by an embodiment of the present invention. This device is applicable to execute the application relationship topology graph drawing method provided by the embodiment of the present invention. As Figure 5 shown, this device may specifically include:

[0104] A data acquisition module 501, configured to acquire each piece of subscription information data and each piece of registration information data registered in the registration center of the microservice application system. Being able to acquire accurate and timely subscription information data and registration information data is beneficial to obtaining the association relationship as the calling party or the called party among the consumer application, subscription service, and provider application corresponding to the subscription information data and registration information data.

[0105] Optionally, the above registration center includes multiple registration centers.

[0106] The first association relationship obtaining module 502 is configured to obtain the consuming application and the subscribed service corresponding to each piece of subscription information data, and respectively determine the consuming application and the subscribed service corresponding to the same piece of subscription information data as the associated calling application and the called service. It can obtain the association relationship between the consuming application and the subscribed service corresponding to the subscription information data as the calling application and the called service.

[0107] Optionally, the above-mentioned first association relationship obtaining module 502 can specifically be configured to identify the positioning marks of the consuming application identifier and the subscribed service identifier in the subscription information data; and obtain the consuming application identifier and the subscribed service identifier based on the corresponding positioning marks, and determine the consuming application and the subscribed service based on the consuming application identifier and the subscribed service identifier.

[0108] Optionally, the above-mentioned first association relationship obtaining module 502 can specifically be configured to identify the positioning marks of the consuming application identifier and the subscribed service identifier in the subscription information data based on the type of the registration center.

[0109] The second association relationship obtaining module 503 is configured to obtain the associated registration information data of each calling application from each piece of registration information data based on the associated called service, and obtain the providing application corresponding to the associated registration information data as the called application associated with the corresponding calling application. This step can obtain the providing application corresponding to the registration information data as the called application, and the association relationship between the calling application associated with the registered service.

[0110] Optionally, the above-mentioned second association relationship obtaining module 503 can specifically be configured to identify the positioning mark of the providing application identifier in the associated registration information data; and obtain the providing application identifier based on the corresponding positioning mark, and determine the providing application based on the providing application identifier.

[0111] Optionally, the above-mentioned second association relationship obtaining module 503 can specifically be configured to identify the positioning mark of the providing application identifier in the associated registration information data based on the type of the registration center.

[0112] The drawing module 504 is used to draw an application relationship topology diagram of the microservice application system based on the association relationship between each calling party application and the associated called party application. The combination modules 501 to 503 obtain each subscription information data and each registration information data from the registration center of the microservice application system, and determine the associated calling party application and called party application based on the consumer application and subscription service included in each subscription information data, and the information of the subscribed service and provider application included in each registration information data. Furthermore, based on the association relationship between the calling party application and the called party application, an application relationship topology diagram of the microservice application system is drawn. It can determine the accurate call association relationship between applications based on accurate and immediate subscription information data and registration information data. And since there is no need to obtain the data required for drawing from table structures with diverse structures, the steps for obtaining drawing data are few and efficient. Thus, it can improve the drawing accuracy and efficiency when drawing the application relationship topology, and further facilitate quickly and accurately evaluating the scope of the impact of a failure in the microservice application system, and improving the emergency response timeliness. In addition, it can also facilitate providing accurate global vision corroborative data for the architect when the architect reconstructs the system and adjusts the architecture, so as to facilitate the architect to conveniently evaluate the impact surface of the architecture adjustment and accurately evaluate the rationality of the system design.

[0113] Optionally, the above drawing module 504 can specifically be used to draw an application relationship topology diagram of the microservice application system based on the association relationship between the calling party application and the called party application, and the association relationship between the calling party application and the called party service.

[0114] Optionally, the above drawing module 504 can specifically be used to draw topology diagram nodes representing each calling party application and the associated called party applications; and generate one-way connection lines from the topology diagram nodes of each calling party application to the topology diagram nodes of the associated called party applications to obtain the application relationship topology diagram.

[0115] Optionally, the above drawing module 504 can specifically be used to determine the importance level of each calling party application based on the number of called party applications called; determine the node form of the topology diagram nodes of each calling party application based on the corresponding importance level; and draw the topology diagram nodes of each calling party application based on the corresponding node form.

[0116] Optionally, the above drawing module 504 can specifically be used to determine the importance level of the corresponding called party application based on the number of calling party applications calling the called party application; determine the node form of the topology diagram nodes of each called party application based on the corresponding importance level; and draw the topology diagram nodes of each called party application based on the corresponding node form.

[0117] Optionally, the above-mentioned drawing module 504 can be specifically configured to determine the importance levels of respective calling party applications based on the number of called party applications called; determine the connection forms of one-way connections of topology graph nodes connected to respective associated called party applications based on corresponding importance levels; and draw one-way connections from topology graph nodes of respective calling party applications to topology graph nodes of respective associated called party applications based on corresponding connection forms.

[0118] Optionally, the above-mentioned drawing module 504 can be specifically configured to determine the importance level of a corresponding called party application based on the number of calling party applications calling each called party application, determine the connection form of a one-way connection of a topology graph node connected to each called party application based on the corresponding importance level; and draw a one-way connection from a topology graph node of an associated calling party application to a topology graph node of each called party application based on the corresponding connection form.

[0119] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the above division of each functional module is used as an example. In practical applications, the above functions can be allocated to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. The specific working processes of the above-described functional modules can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0120] An embodiment of the present invention further provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, it implements the application relationship topology graph drawing method provided in any one of the foregoing embodiments.

[0121] An embodiment of the present invention further provides a computer-readable medium, on which a computer program is stored. When the program is executed by a processor, it implements the application relationship topology graph drawing method provided in any one of the foregoing embodiments.

[0122] An embodiment of the present invention further provides a computer program product, including a computer program, which implements the application relationship topology graph drawing method as described in any one of the embodiments of the present invention when executed by a processor.

[0123] Next, refer to Figure 6 , which shows a schematic structural diagram of a computer system 600 of an electronic device suitable for implementing an embodiment of the present invention. Figure 6 The shown electronic device is only an example and should not impose any limitation on the functions and usage scope of the embodiments of the present invention.

[0124] As Figure 6As shown, computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to programs stored in read-only memory (ROM) 602 or programs loaded into random access memory (RAM) 603 from storage section 608. In RAM 603, various programs and data required for the operation of system 600 are also stored. CPU 601, ROM 602, and RAM 603 are connected to each other via bus 604. Input / output (I / O) interface 605 is also connected to bus 604.

[0125] The following components are connected to I / O interface 605: input section 606 including a keyboard, a mouse, etc.; output section 607 including, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), etc. and a speaker, etc.; storage section 608 including a hard disk, etc.; and communication section 609 including a network interface card such as a LAN card, a modem, etc. Communication section 609 performs communication processing via a network such as the Internet. Drive 610 is also connected to I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on drive 610 as needed so that a computer program read therefrom can be installed into storage section 608 as needed.

[0126] In particular, according to the embodiments disclosed in the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes program codes for performing the methods shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from a network via communication section 609, and / or installed from removable medium 611. When the computer program is executed by central processing unit (CPU) 601, the above-described functions defined in the system of the present invention are performed.

[0127] It should be noted that the computer-readable medium shown in the present invention can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the computer-readable storage medium can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, the computer-readable storage medium can be any tangible medium that contains or stores a program, and this program can be used by or in combination with an instruction execution system, apparatus, or device. In the present invention, the computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, in which the computer-readable program code is carried. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, and this computer-readable medium can send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0128] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagram can represent a module, a program segment, or a part of code, and the above module, program segment, or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the block may occur in a different order than marked in the accompanying drawings. For example, two consecutive blocks shown can actually be executed substantially in parallel, and they can sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, and the combination of blocks in the block diagram or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0129] The modules and / or units involved in the embodiments of the present invention can be implemented in software or in hardware. The described modules and / or units can also be provided in a processor. For example, it can be described as: a processor includes a data acquisition module, a first association relationship acquisition module, a second association relationship acquisition module, and a drawing module. Among them, the names of these modules do not constitute a limitation to the module itself in some cases.

[0130] As another aspect, the present invention also provides a computer-readable medium. The computer-readable medium can be included in the device described in the above embodiments; or it can exist alone without being assembled into the device. The above computer-readable medium carries one or more programs. When the one or more programs are executed by the device, the device includes: obtaining each piece of subscription information data and each piece of registration information data registered in the registration center of the microservice application system; obtaining the consumer application and the subscription service corresponding to each piece of subscription information data, and respectively determining the consumer application and the subscription service corresponding to the same piece of subscription information data as the associated calling application and the called service; obtaining the associated registration information data of each calling application from the each piece of registration information data based on the associated called service, and obtaining the provider application corresponding to the associated registration information data as the called application associated with the corresponding calling application; and drawing an application relationship topology diagram of the microservice application system based on the association relationship between each calling application and the associated called application.

[0131] The above specific embodiments do not constitute a limitation to the protection scope of the present invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for drawing an application relationship topology map, characterized in that: include: Obtain each subscription information data and each registration information data registered by the registration center of the microservice application system; Obtaining the consumer application and subscription service corresponding to each piece of subscription information data, and determining the consumer application and subscription service corresponding to the same piece of subscription information data as the associated caller application and called service; Acquire the associated registration information data of each caller application from the pieces of registration information data based on the associated callee service, and acquire the provider application corresponding to the associated registration information data as the callee application associated with the corresponding caller application; as well as An application relationship topology diagram of the microservice application system is drawn based on the association relationship between each caller application and the associated callee application.

2. The method for drawing an application relationship topology diagram according to claim 1, characterized in that: The obtaining of the consumer application and subscription service corresponding to each piece of subscription information data includes: Identify the location mark of the consumer application identifier and the subscription service identifier in the subscription information data; and Acquire a consumer application identifier and a subscription service identifier based on the corresponding location tag, and determine the consumer application and the subscription service based on the consumer application identifier and the subscription service identifier; The step of obtaining the provider application corresponding to the associated registration information data includes: A location tag identifying a provider application identifier in the associated registration information data; and A provider application identifier is obtained based on the corresponding positioning tag, and a provider application is determined based on the provider application identifier.

3. The method for drawing an application relationship topology diagram according to claim 2, characterized in that: The registration center includes multiple registration centers; The identifying the positioning mark of the consumer application identifier and the subscription service identifier in the subscription information data includes: identifying the positioning mark of the consumer application identifier and the subscription service identifier in the subscription information data based on the type of the registration center; The positioning mark for identifying the provider application identifier in the associated registration information data includes: A positioning tag of a provider application identifier in the associated registration information data is identified based on the type of the registration center.

4. The method for drawing an application relationship topology diagram according to claim 1, characterized in that: The step of drawing an application relationship topology diagram of the microservice application system based on the association relationship between each caller application and the associated callee application includes: Drawing a topology map node representing each caller application and each associated callee application; and A one-way connection is generated from each topology map node of the calling application to each associated topology map node of the called application to obtain the application relationship topology map.

5. The method for drawing an application relationship topology diagram according to claim 4, characterized in that: The drawing of topology graph nodes representing each caller application and each associated callee application includes: Determining the importance level of each caller application based on the number of called callee applications; determining the node form of the topology map node of each caller application based on the corresponding importance level; and drawing the topology map node of each caller application based on the corresponding node form; and / or Based on the number of caller applications that call each callee application, determine the importance level of the corresponding callee application; determine the node form of the topology map node of each callee application based on the corresponding importance level; and draw the topology map node of each callee application based on the corresponding node form.

6. The method for drawing an application relationship topology diagram according to claim 4, characterized in that: The generating of a one-way connection from each topology map node of each calling application to each associated topology map node of each called application includes: Determining the importance level of each caller application based on the number of called callee applications; determining the connection form of the one-way connection connected to the topology map node of each associated callee application based on the corresponding importance level; and drawing the one-way connection from the topology map node of each caller application to the topology map node of each associated callee application based on the corresponding connection form; and / or Based on the number of caller applications that call each callee application, determine the importance level of the corresponding callee application, determine the connection form of the one-way connection connected to the topology map node of each callee application based on the corresponding importance level; and draw the one-way connection from the topology map node of the associated caller application to the topology map node of each callee application based on the corresponding connection form.

7. The method for drawing an application relationship topology diagram according to claim 1, characterized in that: The step of drawing an application relationship topology diagram of the microservice application system based on the association relationship between each caller application and the associated callee application includes: Based on the association relationship between the caller application and the called application, and the association relationship between the caller application and the called service, an application relationship topology diagram of the microservice application system is drawn.

8. A device for drawing an application relationship topology map, characterized in that: include: The data acquisition module is used to obtain each subscription information data and each registration information data registered by the registration center of the microservice application system; A first association relationship acquisition module is used to acquire the consumer application and subscription service corresponding to each subscription information data, and respectively determine the consumer application and subscription service corresponding to the same subscription information data as the associated caller application and called service; A second association relationship acquisition module, configured to acquire the associated registration information data of each caller application from the respective registration information data based on the associated callee service, and acquire the provider application corresponding to the associated registration information data as the callee application associated with the corresponding caller application; as well as The drawing module is used to draw an application relationship topology diagram of the microservice application system based on the association relationship between each caller application and the associated callee application.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the program, the method for drawing an application relationship topology map as described in any one of claims 1 to 8 is implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method for drawing an application relationship topology map as described in any one of claims 1 to 8 is implemented.

Images