Application calling method, computer device and storage medium

Abstract

The present application relates to an application calling method, a computer device and a storage medium, and relates to the field of computer technology. The application calling method is applied to a service grid, and the application calling method includes: receiving a call request for a first application; the first application is an application provided based on a target microservice architecture; the target microservice architecture and the service grid are mutually heterogeneous; through the control plane component of the service grid, according to the call request for the first application, the application information of the first application is obtained from the registration center of the target microservice architecture; the control plane component and the registration center are respectively configured with target services; the first application is called according to the application information of the first application. This method can realize mutual calling between mutually heterogeneous service grid applications and target microservice architecture applications.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an application calling method, a computer device, and a storage medium. Background Art

[0002] With the development of software technology, microservice architecture has been widely used in the development of various systems. Microservice architecture includes SpringCloud and Service Mesh.

[0003] Spring Cloud-based applications (referred to as Spring Cloud applications) typically rely on traditional service registration and discovery mechanisms, such as Eureka or Nacos, to implement service registration, discovery, and invocation through server-side and client-side configuration. Service Mesh-based applications (referred to as Service Mesh applications) implement service governance by deploying proxies between services, including flow control, circuit breaking, retry, and monitoring.

[0004] In real-world applications, there are scenarios where both Spring Cloud applications and Service Mesh applications are used simultaneously. Due to significant differences in the microservice architectures and operating principles of these two applications, calls between Spring Cloud applications and Service Mesh applications cannot be made, increasing system complexity and maintenance costs. Summary of the Invention

[0005] Based on this, it is necessary to provide an application calling method, computer equipment and storage medium to address the above technical problems, which can realize the calling of service grid applications to target microservice architectures such as SpringCloud applications, and realize the calling of target microservice architectures such as SpringCloud applications to service grid applications.

[0006] This application provides an application calling method, which is applied to a service grid. The method includes:

[0007] Receiving a call request for a first application; the first application is an application provided based on a target microservice architecture; the target microservice architecture is heterogeneous with the service grid;

[0008] Obtaining, through a control plane component of the service grid, application information of the first application from a registry of the target microservice architecture according to a call request for the first application; the control plane component and the registry are respectively configured with a target service;

[0009] The first application is called according to the application information of the first application.

[0010] In one embodiment, obtaining, by the control plane component of the service grid, application information of the first application from a registration center of the target microservice architecture according to a call request to the first application, includes:

[0011] Configuring the target service for the control plane component; the target service includes a messaging and collaboration platform service based on an extensible service discovery protocol;

[0012] Based on the target service, obtaining, from the registration center through the control plane component, first full information based on the target microservice architecture; the first full information includes application information of all applications registered with the registration center, and the first full information includes at least application information of the first application;

[0013] According to the call request for the first application, application information of the first application is obtained from the control plane component.

[0014] In one embodiment, the service grid is configured with an edge proxy component; and obtaining application information of the first application from the control plane component according to a call request to the first application includes:

[0015] Obtaining the first full information from the control plane component through the edge proxy component;

[0016] The edge proxy component determines the application information of the first application from the first full information according to a call request for the first application.

[0017] In one embodiment, the method further comprises:

[0018] monitoring a second full amount of information of the service grid, wherein the second full amount of information includes application information of all applications registered with the control plane component;

[0019] When it is monitored that the second full information is updated, the updated second full information is synchronized to the target microservice architecture through the control plane component.

[0020] The application calling method provided in the above embodiment is applied to the service grid. The method receives a calling request for the first application, obtains the application information of the first application from the registration center of the target microservice architecture through the control plane component of the service grid according to the calling request for the first application, and calls the first application according to the application information of the first application. Since the control plane component of the service grid and the registration center of the target microservice architecture are respectively configured with the same target service, the control plane component can synchronously obtain the application information in the target microservice architecture from the registration center through the target service. Based on this, the application based on the service grid can obtain the application information of the first application, and thus can call the first application through the application information of the first application, thereby realizing the call of the service grid to the target microservice architecture, solving the problem in the related technology that the service grid and the heterogeneous target microservice architecture such as SpringCloud applications cannot call each other, improving the scalability and overall performance of the system, and reducing the difficulty of development and maintenance.

[0021] This application provides an application calling method, which is applied to a target microservice architecture, and the method includes:

[0022] Receive a call request for a second application; the second application is an application provided by a service grid; the service grid uses the above-mentioned application call method to call the first application; the target microservice architecture and the service grid are heterogeneous;

[0023] Obtaining, from a registration center of the target microservice architecture, application information of the second application according to a call request for the second application; the target microservice architecture is mounted with a proxy plug-in, the proxy plug-in being configured to obtain second full information from a control plane component of the service grid, the second full information including at least the application information of the second application;

[0024] The second application is called according to the application information of the second application.

[0025] In one embodiment, the method further comprises:

[0026] Mounting the proxy plug-in on the target microservice architecture; the proxy plug-in and the control plane component respectively support the target protocol;

[0027] Based on the target protocol, obtaining second full information based on the service grid from the control plane component through the proxy plug-in; the second full information includes application information of all applications registered with the control plane component;

[0028] The second full amount of information is sent to the registration center through the proxy plug-in.

[0029] In one embodiment, sending the second full amount of information to the registration center through the proxy plug-in includes:

[0030] Performing format conversion on the second full amount of information by the proxy plug-in; the second full amount of information after format conversion complies with the format requirements of the target microservice architecture;

[0031] The second full amount of information after format conversion is sent to the registration center through the proxy plug-in.

[0032] In one embodiment, the method further comprises:

[0033] Monitoring first full information based on the target microservice architecture; the first full information includes application information of all applications registered with the registration center;

[0034] When it is detected that the first full information is updated, the updated first full information is synchronized to the service grid through the registration center.

[0035] The present application provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above method when executing the computer program.

[0036] The present application provides a computer-readable storage medium having a computer program stored thereon, and the computer program implements the steps of the above method when executed by a processor.

[0037] The above-mentioned embodiment provides an application calling method, a computer device, and a storage medium. The method receives a calling request for a second application, obtains application information of the second application from a registration center of a target microservice architecture according to the calling request for the second application, and calls the second application according to the application information of the second application. Since the target microservice architecture is mounted with a proxy plug-in, and the proxy plug-in can obtain the second full amount of information from the control plane component of the service grid, and the second full amount of information at least includes the application information of the second application, therefore, the target microservice architecture obtains the application information of the second application based on the service grid. Based on this, the call to the second application can be realized through the application information of the second application. In this way, on the basis of realizing the call of the service grid application to the target microservice architecture application, the call of the application based on the target microservice architecture to the application based on the service grid is further realized, which solves the problem in the related technology that the service grid and the heterogeneous target microservice architecture, such as SpringCloud, cannot be called, improves the scalability and overall performance of the system, and reduces the difficulty of development and maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1An application environment diagram of an application calling method in one embodiment;

[0039] Figure 2 A schematic diagram of the target microservice architecture in one embodiment;

[0040] Figure 3 This is a schematic diagram of the structure of a service grid in one embodiment;

[0041] Figure 4 A flowchart of an application calling method in one embodiment is shown;

[0042] Figure 5 A schematic diagram of the target microservice architecture and service grid in one embodiment;

[0043] Figure 6 A flowchart of an application calling method according to another embodiment;

[0044] Figure 7 A flowchart of an application calling method in another embodiment is shown;

[0045] Figure 8 A schematic diagram of the structure of the target microservice architecture and service grid in another embodiment;

[0046] Figure 9 A flowchart of an application calling method in yet another embodiment;

[0047] Figure 10 A schematic diagram of the structure of the target microservice architecture and service grid in another embodiment;

[0048] Figure 11 A structural block diagram of an application calling device in one embodiment;

[0049] Figure 12 It is a structural block diagram of an application calling device in another embodiment;

[0050] Figure 13 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0052] Understandably, as service mesh-based microservices architectures continue to mature, many projects are adopting them as their microservices architecture. However, existing projects still rely on Spring Cloud-based microservices. Due to differences in service registration and discovery mechanisms between Spring Cloud applications and service mesh applications, applications in the two architectures cannot call or communicate with each other.

[0053] Based on the above, an embodiment of the present application provides an application calling method that can realize the calling of a service grid application to a SpringCloud application, and can also realize the calling of a SpringCloud application to a service grid application, thereby realizing the mutual calling of a service grid application and a SpringCloud application, that is, realizing the mutual communication between applications in heterogeneous microservice architectures, which helps to improve the overall performance and scalability of the system and reduce the difficulty of development and maintenance.

[0054] The application calling method provided in the embodiment of the present application can be applied to Figure 1 The application environment shown. Among them, the target microservice architecture 10 and the service grid 20 such as SpringCloud are two mutually heterogeneous microservice architectures. Among them, the target microservice architecture 10 such as SpringCloud is a microservice framework based on the Java language, which provides a series of tools and components for building distributed systems. The service grid 20 is an infrastructure layer for processing inter-service communication. Its core idea is to separate the logic of inter-service communication from the application program and deploy it next to each service instance in the form of an independent proxy process, which is responsible for inter-service communication, load balancing, circuit breaking, security and other functions. The service grid 20 is a new microservice architecture in the cloud-native era. It uses a non-invasive way to solve the problem of mutual communication between services, and it has no restrictions on development languages. Based on the application calling method provided in the embodiment of the present application, it is possible to realize mutual application calling between the service grid 20 and the target microservice architecture 10 such as SpringCloud.

[0055] In some embodiments, as Figure 2 As shown, a schematic diagram of the structure of a target microservice architecture 10 is provided. Figure 2As shown, the target microservice architecture 10 can be configured with at least one first application 11 (or at least one service). Furthermore, the target microservice architecture 10 can be configured with a registration center 12 and a service invocation component 13. Each first application 11 is configured with a corresponding service invocation component 13. For example, the target microservice architecture 10 includes SpringCloud. SpringCloud includes the Nacos registration center and the Feign service invocation component. SpringCloud uses the Nacos registration center to register and discover services, and the Feign service invocation component enables inter-service communication. Feign retrieves the service list from the Nacos registration center. When initiating a service call, it matches the service name to the corresponding service list and initiates the service call.

[0056] In some embodiments, as Figure 3 As shown, a schematic diagram of the structure of a service grid 20 is provided. Figure 3 As shown, a service mesh 20 can be configured with at least one second application 21 (or at least one service). Furthermore, the service mesh 20 is equipped with a control plane component 22 and an edge proxy component 23. Each second application 21 is configured with a corresponding edge proxy component 23, and both the second application 21 and the corresponding edge proxy component 23 are deployed in a container 24. Container 24 can be built on Kubernetes (a container orchestration platform, or Kubernetes). For example, a service mesh including Istio includes a control plane component, Pilot, and an edge proxy component, Envoy. Pilot is responsible for service discovery and intelligent routing, while Envoy, as a data platform proxy, enables communication between applications. When a service starts, Envoy sends service information to Pilot, which then synchronizes the latest service information with the Envoys of other services. When services need to communicate, Envoy retrieves the corresponding service list and initiates a call to the service.

[0057] It should be noted that in the embodiments of the present application, an application can be understood as a service, and a service can also be understood as an application. The terms "first", "second", etc. used in this application can be used herein to describe various objects, but these objects are not limited by these terms. These terms are only used to distinguish the first object from another object. For example, without departing from the scope of this application, the first application 11 can be referred to as the second application 21, and similarly, the second application 21 can be referred to as the first application 11. Both the first application 11 and the second application 21 are applications, but they are not the same application.

[0058] In some embodiments, combined Figures 1 to 5, provides an application calling method, and takes the application of the application calling method to the service grid 20 as an example for explanation. The method may include the following steps.

[0059] S402: Receive a call request for a first application.

[0060] The first application 11 is an application provided based on the target microservice architecture 10. The target microservice architecture 10 and the service grid 20 are heterogeneous. Exemplarily, the target microservice architecture 10 includes Spring Cloud; accordingly, the first application 11 is an application based on Spring Cloud.

[0061] The call request to the first application 11 may be initiated by the service grid 20. The call request to the first application 11 is used to call the first application 11 in the target microservice architecture 10.

[0062] In the application, you can receive call requests from the service grid 20 to the SpringCloud application.

[0063] S404: Obtain application information of the first application from a registration center of the target microservice architecture through a control plane component of the service grid according to a call request to the first application.

[0064] The control plane component 22 is responsible for managing all services in the service mesh 20, including configuration, service discovery, and certificate distribution. It does not directly handle inter-service communication, but rather manages and configures proxies in the data plane to route traffic and enforce policies. For example, in the case of the Istio service mesh, the control plane component 22 might include a pilot, which is responsible for service discovery and intelligent routing.

[0065] The registry center 12 of the target microservice architecture 10 is a dynamic service discovery, configuration management, and service management platform that can be used to build cloud-native applications. The core functions of the registry center 12 include service discovery and health checks, dynamic configuration services, and dynamic DNS services. For example, if the target microservice architecture 10 is Spring Cloud, the registry center 12 can include Nacos.

[0066] The control plane component 22 and the registry 12 are respectively configured with target services. That is, the control plane component 22 based on the service grid 20 and the registry 12 based on the target microservice architecture 10 are respectively configured with the same services.

[0067] In some embodiments, the target service may be a service natively provided by the service grid 20. For this purpose, the target service may be pre-configured for the target microservice architecture 10. In some embodiments, the target service may be a service natively provided by the target microservice architecture 10. For this purpose, the target service may be pre-configured for the service grid 20. This allows the service grid 20 and the target microservice architecture 10 to configure the target service separately, allowing the service grid 20 to synchronize application information of the target microservice architecture 10 with the target microservice architecture 10 based on the target service.

[0068] It can be understood that since the control plane component 22 of the service grid 20 and the registration center 12 of the target microservice architecture 10 are respectively configured with the same target service, the control plane component 22 can synchronously obtain the application information in the target microservice architecture 10 from the registration center 12 through the target service; based on this, when a call request for the first application 11 of the target microservice architecture 10 is received, the terminal can obtain the application information of the first application 11 from the registration center 12 through the control plane component 22 and according to the call request for the first application 11.

[0069] In some embodiments, the call request for the first application 11 includes a first application identifier, which can be understood as a unique identifier of the first application 11. Based on this, the terminal can obtain application information of the first application 11 from the registration center 12 according to the first application identifier through the control plane component 22. The application information of the first application 11 is used to call the first application 11 and may include all information related to calling the first application 11. For example, the application information includes service registration information, a service instance list, etc., which is not limited here.

[0070] S406: Call the first application according to the application information of the first application.

[0071] In the application, the service grid 20 can send a call request to the first application 11 according to the application information of the first application 11, and receive the processing result returned by the first application 11, thereby implementing the call of the service grid 20 to the first application 11.

[0072] Taking the service mesh Istio, the control plane component pilot, the target microservice architecture SpringCloud, and the registration center Nacos as an example, the service mesh 20 can obtain the application information of the SpringCloud application from Nacos through the pilot according to the call request to the SpringCloud application, and implement the call to the SpringCloud application based on the obtained application information, thereby realizing the call of the service mesh application to the SpringCloud application.

[0073] The application calling method provided in the above embodiment is applied to the service grid 20. The method receives a call request for the first application 11 and, through the control plane component 22 of the service grid 20, obtains application information of the first application 11 from the registration center 12 of the target microservice architecture 10 based on the call request for the first application 11, and calls the first application 11 based on the application information of the first application 11. Because the control plane component 22 of the service grid 20 and the registration center 12 of the target microservice architecture 10 are respectively configured with the same target service, the control plane component 22 can synchronously obtain application information in the target microservice architecture 10 from the registration center 12 through the target service. Based on this, applications based on the service grid 20 can obtain the application information of the first application 11, and can thus call the first application 11 based on the application information of the first application 11, thereby enabling the service grid 20 to call the target microservice architecture 10. This solves the problem in the related art of being unable to call applications between the service grid 20 and heterogeneous target microservice architecture 10 (such as Spring Cloud), improves the scalability and overall performance of the system, and reduces the difficulty of development and maintenance.

[0074] In some embodiments, as Figure 6 As shown, S404, through the control plane component of the service grid, according to the call request of the first application, obtains the application information of the first application from the registration center of the target microservice architecture, which may include the following steps.

[0075] S602: Configure target services for the control plane component.

[0076] The target service may include a Messaging and Collaboration Platform over Extensible Service Discovery Protocol (MCP-over-XDS) service.

[0077] It is understandable that the registration center 12 of the target microservice architecture 10, such as Spring Cloud's Nacos, natively provides the MCP-over-XDS service, while the service grid 20 does not natively provide the MCP-over-XDS service. Therefore, the MCP-over-XDS service can be configured for the control plane components 22 of the service grid 20, such as the pilot.

[0078] In applications, such as Figure 5 As shown in the figure, you can configure the MCP-over-XDS service for the pilot, the control plane component in the service mesh Istio; based on this, after the pilot is started, it can establish a gRPC (remote interface call) link with the MCP-over-XDS service.

[0079] S604: Based on the target service, obtain first full information based on the target microservice architecture from the registration center through the control plane component.

[0080] The first full information includes application information for all applications registered with the registration center 12. The first full information includes at least the application information for the first application 11. It should be noted that the first full information refers to all information related to the target microservice grid 20, including but not limited to registration information and service lists. The registration center 12 of the target microservice architecture 10 includes the first full information. For example, the Nacos registration center caches registered application registration information, which can be abbreviated as NacosServer information.

[0081] In an application, a service mesh 20 (including a first application 11) can be registered with a registry 12. Registry 12 then stores the first full set of information for service mesh 20, including information about first application 11. This first full set of information can then be synchronously retrieved from registry 12 based on the target service. For example, if a SpringCloud application is registered with the Nacos registry, the control plane component pilot can synchronously retrieve the first full set of information from the Nacos registry using the MCP-over-XDS service.

[0082] It is understandable that the application information formats of heterogeneous microservice architectures are different, or in other words, the application information structures of heterogeneous microservice architectures are different. In this regard, the control plane component 22 can also convert the format of the first full information based on the target service during the synchronization of the first full information based on the target service, thereby obtaining the first full information that meets the format requirements of the service grid 20, and providing support for the application of the service grid 20 to call the application based on the target microservice architecture 10. Taking the registration center Nacos and the control plane component pilot as an example, the service grid 20 can convert the NacosServer information into an Endpoint list based on the MCP-over-XDS service, and the Endpoint list meets the format requirements of the service grid 20.

[0083] S606: Acquire application information of the first application from the control plane component according to the call request for the first application.

[0084] Exemplarily, the call request to the first application 11 includes a first application identifier, which can be understood as a unique identifier of the first application 11; based on this, the control plane component 22 can match the application information of the first application 11 from the first full information according to the first application identifier. In this way, the application based on the service grid 20 can initiate a call to the first application 11 according to the application information of the first application 11.

[0085] The application calling method provided in the above embodiment configures the target service for the control plane component 22, and based on the target service, obtains the first full information based on the target microservice architecture 10 from the registration center 12 through the control plane component 22, and obtains the application information of the first application 11 from the control plane component 22 according to the call request for the first application 11; since the registration center 12 of the target microservice architecture 10, such as Nacos of SpringCloud, natively provides the target service, namely the MCP-over-XDS service, and the service grid 20 does not natively provide the MCP-over-XDS service, in this regard, the present application configures the MCP-over-XDS service for the control plane component 22 of the service grid 20, such as pilot, so that the control plane component 22 can establish a link with the registration center 12 based on the MCP-over-XDS service, and synchronously obtains the first full information of all applications registered with the registration center 12 from the registration center 12, and then the application based on the service grid 20 can realize the call of the application of the target microservice architecture 10.

[0086] Please continue reading Figures 1 to 6 In some embodiments, the service mesh 20 is configured with an edge proxy component 23 , which can be used for the data plane of the service mesh 20 .

[0087] Based on the above, S606, according to the call request for the first application, obtains the application information of the first application from the control plane component, which may include: obtaining the first full information from the control plane component through the edge agent component; through the edge agent component, according to the call request for the first application, determining the application information of the first application from the first full information.

[0088] In this way, applications in the service grid 20 can call applications in the target microservice architecture 10 based on the edge proxy component 23, thereby improving the scalability of the system.

[0089] Taking the target microservice architecture 10 as SpringCloud as an example, if the second application 21 in the service mesh Istio needs to call the first application 11 in the target microservice architecture 10 such as SpringCloud, the edge proxy component Envoy of the second application 21 receives a call request to the first application 11. The edge proxy component Envoy can obtain the first full information from the control plane component pilot, and match the application information of the first application 11 from the first full information according to the call request, so that the second application 21 can initiate a call to the first application 11 based on the edge proxy component Envoy.

[0090] Please continue reading Figures 1 to 6In some embodiments, the application calling method further includes: monitoring the second full amount information of the service grid; when it is monitored that the second full amount information is updated, synchronizing the updated second full amount information to the target microservice architecture through the control plane component.

[0091] In this way, the second full information in the service grid 20 is synchronized to the target microservice architecture 10, providing support for the application of the target microservice architecture 10 to call the application of the service grid 20.

[0092] The second full information includes application information for all applications registered with control plane component 22. Monitoring the second full information can be understood as monitoring applications in service grid 20. Updates to the second full information can be understood as changes to applications in service grid 20. Application changes include, but are not limited to, adding or removing applications from service grid 20 and changes to registered services.

[0093] In the application, the application in the service grid 20 can be monitored. When an application in the service grid 20 is updated, the control plane component 22 synchronizes the updated second full data to the proxy plug-in 14 in the target microservice architecture 10, such as the SpringCloud proxy plug-in, based on the target protocol, such as the Extensible Discovery Service (XDS) protocol. For details, see the following embodiment of the application invocation method applied to the target microservice architecture SpringCloud.

[0094] Based on similar inventive concepts, in some embodiments, the present application also provides an application calling method, which is applied to a target microservice architecture such as SpringCloud, and can realize the call of the target microservice architecture to the service grid, solving the problem of the inability to call between the target microservice architecture and the service grid, improving the scalability and overall performance of the system, and reducing the difficulty of development and maintenance.

[0095] In some embodiments, as Figure 7 and Figure 8 As shown, an application calling method is provided, and the application of the application calling method to the target microservice architecture 10 such as SpringCloud is used as an example for explanation. The method may include the following steps.

[0096] S702: Receive a call request for a second application.

[0097] The second application 21 is an application provided by the service grid 20. The target microservice architecture 10 and the service grid 20 are heterogeneous. The service grid 20 can use the aforementioned application calling method to call the first application 11 based on the target microservice architecture 10. For details, please refer to the relevant description above and will not be repeated here.

[0098] The call request to the second application 21 may be initiated by the target microservice architecture 10. The call request to the second application 21 is used to call the second application 21 in the service grid 20.

[0099] In the application, a call request from a target microservice architecture 10 , such as a SpringCloud application, to a service grid 20 , such as a second application 21 , may be received.

[0100] S704: According to the call request for the second application, obtain application information of the second application from the registration center of the target microservice architecture.

[0101] The target microservice architecture 10 is mounted with an agent plug-in 14. Exemplarily, each first application 11 in the target microservice architecture 10 is respectively mounted with an agent plug-in 14. Taking the target microservice architecture 10 as SpringCloud as an example, the corresponding agent plug-in 14 can be an agent.

[0102] The proxy plug-in 14 is configured to obtain the second full information from the control plane component 22 of the service grid 20. Exemplarily, the control plane component 22 is configured with an interface; accordingly, the proxy plug-in 14 can be used to access the interface of the control plane component 22. Based on this, the proxy plug-in 14 can obtain the second full information from the control plane component 22 through the interface of the control plane component 22. Exemplarily, the interface includes an interface based on the XDS protocol.

[0103] The second full information may include application information for all applications registered with the control plane component 22. The second full information includes at least application information for the second application 21. It should be noted that the second full information refers to information related to all service grids 20 registered with the control plane component 22, including but not limited to registration information, service lists, etc. Exemplarily, the second full information includes an endpoint list.

[0104] In the application, after obtaining the second full information from the control plane component 22, the proxy plug-in 14 can send the second full information to the registration center 12, and integrate the first full information and the second full information and cache them locally. The first full information refers to information related to all target microservice architectures 10 registered with the registration center 12.

[0105] In some embodiments, the call request for the second application 21 includes a second application identifier, which can be understood as a unique identifier for the second application 21. Based on this, the service call component 13 can match the application information of the second application 21 from the second full information based on the second application identifier. The application information of the second application 21 is used to call the second application 21 and may include all information related to calling the second application 21, for example, the application information includes service registration information, a service instance list, etc., which is not limited here.

[0106] In the application, the service calling component 13 can obtain the application information of the second application 21 from all the integrated full information according to the calling request of the second application 21.

[0107] S706: Call the second application according to the application information of the second application.

[0108] In the application, the target microservice architecture 10 can send a call request to the second application 21 according to the application information of the second application 21, and receive the processing result returned by the second application 21, thereby realizing the call of the target microservice architecture 10 to the second application 21, that is, realizing the call of the target microservice architecture 10 to the service grid 20.

[0109] Taking the service mesh Istio including the control plane component pilot and the edge proxy component Envoy, and the target microservice architecture SpringCloud including the registration center Nacos, the proxy plug-in agent and the service call component feign as an example, the SpringCloud application can synchronously obtain the second full information from the pilot through the agent and send it to the registration center Nacos; when receiving a call request to the service mesh 20, SpringCloud can obtain the application information of the SpringCloud application from Nacos through feign according to the call request to the SpringCloud application, and call the SpringCloud application through feign, thereby realizing the call of the SpringCloud application to the service mesh 20.

[0110] The application calling method provided in the above embodiment is applied to the target microservice architecture 10. The method receives a call request for the second application 21, obtains the application information of the second application 21 from the registration center 12 of the target microservice architecture 10 according to the call request for the second application 21, and calls the second application 21 according to the application information of the second application 21. Since the target microservice architecture 10 is mounted with a proxy plug-in 14, and the proxy plug-in 14 can obtain the second full information from the control plane component 22 of the service grid 20, and the second full information at least includes the application information of the second application 21, therefore, the target microservice architecture 10 obtains the application information of the second application 21 based on the service grid 20; based on this, the call to the second application 21 can be implemented through the application information of the second application 21. In this way, on the basis of implementing the call of the service grid application to the target microservice architecture application, the call of the application based on the target microservice architecture 10 to the application based on the service grid 20 is further implemented, which solves the problem in the related art that the service grid 20 and the heterogeneous target microservice architecture 10 (such as SpringCloud) application cannot be called, improves the scalability and overall performance of the system, and reduces the difficulty of development and maintenance.

[0111] In some embodiments, as Figure 8 and Figure 9 As shown, the application calling method applied to the target microservice architecture 10 such as SpringCloud can also include the following steps.

[0112] S902: Mount the proxy plug-in to the target microservice architecture.

[0113] The proxy plug-in 14 and the control plane component 22 each support a target protocol. For example, the service mesh 20 is Istio, and the control plane component 22 is pilot; correspondingly, the target protocol includes the XDS protocol.

[0114] It is understandable that the control plane component pilot natively supports the XDS protocol, or in other words, the control plane component pilot provides an interface that supports the XDS protocol; to this end, the present application mounts a proxy plug-in 14 on the target microservice architecture 10, such as SpringCloud, thereby accessing the pilot interface that supports the XDS protocol through the proxy plug-in 14.

[0115] For example, bytecode enhancement technology can be used to enhance the logic of the target microservice architecture 10 in obtaining the second full information from the control plane component 22. That is, by mounting the proxy plug-in 14 on the target microservice architecture 10, the synchronization function of the second full information can be implemented. Bytecode enhancement technology refers to the process of dynamically modifying or adding functionality by operating on the generated .class files (containing Java bytecode) during the post-compilation phase of a Java application. This technology can enhance the behavior of a class during program runtime or loading without changing the original source code.

[0116] It is understandable that the target microservice architecture SpringCloud is a Java-based microservice architecture. Based on this, this application uses bytecode enhancement technology to mount an agent plug-in in each application in SpringCloud without changing the SpringCloud source code, thereby increasing the performance of obtaining application information of the service grid 20 from the service grid 20, having little impact on the original architecture and being easy to implement.

[0117] S904: Based on the target protocol, obtain the second full amount of information based on the service grid from the control plane component through the proxy plug-in.

[0118] The second full information includes application information of all applications registered with the control plane component 22 , and the second full information includes at least application information of the second application 21 .

[0119] As can be seen from the foregoing, the proxy plug-in 14 and the control plane component 22 support the same target protocol, namely the XDS protocol. Therefore, the proxy plug-in 14 can obtain the second full information from the control plane component 22 based on the XDS protocol. In the application, the proxy plug-in 14 can periodically obtain the second full information, improving the synchronization and consistency of application information between the target microservice architecture 10 and the service architecture.

[0120] S906: Send the second full amount of information to the registration center through the proxy plug-in.

[0121] After obtaining the second full information, the proxy plug-in 14 may send the second full information to the registration center 12. The registration center 12 may integrate the second full information with the first full information, and all the integrated full information may be cached locally. This helps to directly obtain application information from the local computer, implement application calls, and improve data processing performance.

[0122] In the application, the registration center Nacos may store the first full information in a pre-established data structure for storing application information, such as serviceInfoMap. Based on this, the registration center 12 can integrate the second full information sent by the proxy plug-in 14 with the first full information by calling an integration function based on the data structure, such as serviceInfoMap.put().

[0123] The application calling method provided in the above embodiment mounts the proxy plug-in 14 on the target microservice architecture 10, obtains the second full information based on the service grid 20 from the control plane component 22 through the proxy plug-in 14 based on the target protocol, and sends the second full information to the registration center 12 through the proxy plug-in 14, so that the registration center 12 can integrate the second full information with the first full information to obtain all the full information of the service grid 20 and the target microservice architecture 10, thereby providing support for the target microservice architecture 10 to call the service grid 20, thereby not only realizing the call between the target microservice architectures 10, but also realizing the call of the target microservice architecture 10 to the service grid 20, thereby improving the system performance.

[0124] Please continue reading Figure 8 and Figure 9 In some embodiments, S906, sending the second full amount of information to the registration center through the proxy plug-in includes: converting the format of the second full amount of information through the proxy plug-in; and sending the second full amount of information after format conversion to the registration center through the proxy plug-in.

[0125] The second full information after format conversion complies with the format requirements of the target microservice architecture 10 .

[0126] It is understandable that heterogeneous microservice architectures have different application information formats, or in other words, different application information structures. To this end, after obtaining the second full information from the control plane component 22, the agent plug-in 14 can convert the second full information to a format that meets the format requirements of the target microservice architecture 10. Taking the registration center Nacos and the control plane component pilot as an example, the agent plug-in agent can obtain the endpoint list from the pilot based on the XDS protocol and convert the endpoint list into NacosServer information. This NacosServer information meets the format requirements of the service grid 20.

[0127] In the process of synchronizing the first full information based on the target service, the control plane component 22 can also convert the format of the second full information based on the target service, thereby obtaining the second full information that meets the format requirements of the target microservice architecture 10, and providing support for the application of the target microservice architecture 10 to call the application based on the service grid 20.

[0128] Please continue reading Figure 8 and Figure 9 In some embodiments, the application calling method further includes: monitoring the first full amount of information based on the target microservice architecture; and when it is monitored that the first full amount of information is updated, synchronizing the updated first full amount of information to the service grid through the registration center.

[0129] In this way, the first full information in the target microservice architecture 10 is synchronized to the service grid 20, providing support for the application of the service grid 20 to call the application of the target microservice architecture 10.

[0130] The first full information includes application information for all applications registered with the registration center 12. Monitoring the first full information can be understood as monitoring the applications in the target microservice architecture 10. An update to the first full information can be understood as a change to an application in the target microservice architecture 10. Application changes include, but are not limited to, adding or removing an application from the target microservice architecture 10 and changes to registered services.

[0131] In the application, the application in the target microservice architecture 10 can be monitored. When an update is detected in the target microservice architecture 10, the updated first full information is synchronized to the control plane component 22 in the service grid 20, such as Istio's pilot, through the registration center 12, such as Spring Cloud's Nacos, based on the MCP-over-XDS service. The specific implementation process of the registration center 12 synchronously obtaining the first full information from the control plane component 22 can be found in the application call method applied to the service grid 20, and will not be repeated here.

[0132] It should be noted that in the embodiment of the present application, the service grid 20 can implement the service grid 20 calling the target microservice architecture 10, such as the SpringCloud application, based on the application calling method applied to the service grid 20 provided above; in addition, the target microservice architecture 10, such as SpringCloud, can implement the target microservice architecture 10, such as the SpringCloud application, calling the service grid 20 based on the application calling method applied to the target microservice architecture 10 described above; in this way, mutual calling, or mutual communication, is implemented between the service grid 20 and the target microservice architecture 10, such as the SpringCloud application.

[0133] In one embodiment, combined Figures 1 to 10 , provides an application calling method, taking the consumer application 121 and the provider application 211 as examples to illustrate the application calling method.

[0134] The consumer application 111 is a Spring Cloud application, and the provider application 211 is a service grid 20. The following describes the implementation process of the consumer application 111 calling the provider application 211.

[0135] In the application, register the consumer application 111 to the registration center Nacos. The specific configuration content includes:

[0136] Spring:

[0137] Cloud: / / SpringCloud Microservice Architecture

[0138] Nacos: / / Registration Center Nacos

[0139] Discovery: / / Service Registration

[0140] Server-addr:127.0.0.1:8848 / / Service address

[0141] Group: default

[0142] Namespace: public

[0143] Service: consumer / / consumer application

[0144] Username: nacos

[0145] Password: XXXXXXX

[0146] For ease of understanding, the text following the " / / " in the above is a comment. Based on the above, a Java-based proxy plug-in agent, which can be referred to as javaagent, is mounted on the consumer application 111. javaagent is used to synchronize the application registration information of the service grid 20, that is, the second full information. Specifically, the javaagent parameter and the environment variable profile.micro.service.envoy.xds.server can be added to the startup command to indicate the service information address in the synchronization service grid 20. The specific configuration is as follows:

[0147] java-javaagent:agent.jar-Dprofile.micro.service.envoy.xds.server=istiod.istio-system.svc:15010 -jar consumer.jar

[0148] After the above configuration, the SpringCloud service, that is, the consumer application 111, can be registered with the Nacos registration center 12 and the javaagent is mounted. The javaagent will synchronize the application registration information such as the Endpoint list to the service grid 20 through the XDS protocol.

[0149] In the application, consumer application 111 uses a javaagent to obtain an endpoint list from the pilot based on the XDS protocol, converts the endpoint list into NacosServer information, and sends it to Nacos. Nacos integrates the NacosServer information of the service grid 20 with the NacosServer information of the SpringCloud application and caches it locally. When consumer application 111 calls provider application 211 in service grid 20, it can obtain the application information of provider application 211 from Nacos through feign and initiate a call to provider application 211.

[0150] The following describes the implementation process of the provider application 211 calling the consumer application 111.

[0151] First, configure the MCP-over-XDS service for the control plane component pilot in the service mesh Istio. This way, the pilot can establish a connection with the registration center Nacos through the MCP-over-XDS service. In the application, the pilot can synchronize the service registration information in Nacos, that is, the first full information, such as NacosServer information, through the MCP-over-XDS protocol. Among them, the MCP-over-XDS service is configured for the pilot as follows:

[0152] configSources:

[0153] - address: xds: / / 127.0.0.1:18848

[0154] Then, the provider application 211 is deployed in K8s.

[0155] In the application, the pilot can obtain the first full information of the SpringCloud application from Nacos. When the provider application 211 calls the consumer application 111, the provider application 211 can obtain the application information of the consumer application 111 from the pilot through the corresponding edge proxy component Envoy, thereby initiating a call to the consumer application 111.

[0156] After deploying consumer application 111 and provider application 211 as described above, they can call each other, that is, they can communicate with each other. It should be noted that the above configuration uses a Spring Cloud application as consumer application 111 and a service grid 20 as provider application 211 as an example. In your application, you can configure the Spring Cloud application and service grid 20 accordingly based on your specific scenario to enable communication between the two applications.

[0157] In the application invocation method provided in the above embodiment, when the service grid 20 calls a SpringCloud application, Envoy can obtain SpringCloud application information and initiate a call to the SpringCloud application. When the SpringCloud application calls the service grid 20, the Javaagent enhances the service list acquisition method. The service list is synchronized with the service grid 20 information, and the feign component can then obtain the service grid 20 information and initiate a call to the service grid 20. This enables communication between the SpringCloud application and the service grid 20, improving the system's scalability and overall performance while reducing development and maintenance difficulties.

[0158] It should be understood that, although the steps in the flowcharts of the above embodiments are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the flowcharts of the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily to be performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0159] Based on the same inventive concept, embodiments of the present application also provide an application invocation device for implementing the aforementioned application invocation method. The implementation solution provided by this device is similar to the implementation solution described in the aforementioned method. Therefore, the specific limitations in one or more application invocation device embodiments provided below can be found in the above-mentioned limitations on the application invocation method and will not be further elaborated here.

[0160] In some embodiments, as Figure 11As shown, an application calling device 1100 is provided, which is applied to a service grid. The application calling device 1100 includes: a first receiving module 1101, a first obtaining module 1102, and a first calling module 1103. The first receiving module 1101 is used to receive a call request for a first application; the first application is an application provided based on a target microservice architecture; the target microservice architecture and the service grid are heterogeneous. The first obtaining module 1102 is used to obtain application information of the first application from a registration center of the target microservice architecture through the control plane component of the service grid based on the call request for the first application; the control plane component and the registration center are respectively configured with a target service. The first calling module 1103 is used to call the first application based on the application information of the first application.

[0161] The above-mentioned application calling device 1100 receives a calling request for a first application through a first receiving module 1101; the first application is an application provided based on the target microservice architecture, and through the first obtaining module 1102 and the control plane component of the service grid, according to the calling request for the first application, obtains the application information of the first application from the registration center of the target microservice architecture, and calls the first application according to the application information of the first application through the first calling module 1103; since the control plane component of the service grid and the registration center of the target microservice architecture are respectively configured with the same target service, the control plane component can synchronously obtain the application information in the target microservice architecture from the registration center through the target service; based on this, the application based on the service grid can obtain the application information of the first application, and thus can call the first application through the application information of the first application, thereby realizing the call of the service grid application to the target microservice architecture application, solving the problem in the related technology that the service grid and the heterogeneous target microservice architecture (such as SpringCloud) applications cannot call each other, improving the scalability and overall performance of the system, and reducing the difficulty of development and maintenance.

[0162] In some embodiments, the first acquisition module is also used to configure the target service for the control plane component; the target service includes a messaging and collaboration platform service based on the extensible service discovery protocol; based on the target service, the control plane component obtains the first full information based on the target microservice architecture from the registration center through the control plane component; the first full information includes application information of all applications registered to the registration center, and the first full information includes at least application information of the first application; according to the call request for the first application, the application information of the first application is obtained from the control plane component.

[0163] In some embodiments, the service grid is configured with an edge proxy component. The first acquisition module is further configured to obtain the first full information from the control plane component via the edge proxy component; and determine, via the edge proxy component, application information of the first application from the first full information based on a call request to the first application.

[0164] In some embodiments, the application calling device further includes a first monitoring module and a first synchronization module. The first monitoring module is configured to monitor the second full information of the service grid; the second full information includes application information of all applications registered with the control plane component. Upon detecting an update to the second full information, the first synchronization module is configured to synchronize the updated second full information to the target microservice architecture via the control plane component.

[0165] In some embodiments, as Figure 12 As shown, an application calling device 1200 is provided, which is applied to a target microservice architecture such as SpringCloud. The application calling device 1200 includes: a second receiving module 1201, a second obtaining module 1202, and a second calling module 1203. Among them, the second receiving module 1201 receives a call request for the second application; the second application is an application provided based on the service grid; the service grid can use the aforementioned application calling method to call the first application; the target microservice architecture and the service grid are heterogeneous. The second obtaining module 1202 is used to obtain the application information of the second application from the registration center of the target microservice architecture based on the call request for the second application; the target microservice architecture is mounted with a proxy plug-in, and the proxy plug-in is used to obtain the second full amount of information from the control plane component of the service grid, and the second full amount of information at least includes the application information of the second application. The second calling module 1203 is used to call the second application based on the application information of the second application.

[0166] The above-mentioned application calling device 1200 receives a call request for a second application through a second receiving module 1201; the second application is an application provided by the service grid, and the second obtaining module 1202 obtains the application information of the second application from the registration center of the target microservice architecture according to the call request for the second application, and the second calling module 1203 calls the second application according to the application information of the second application. Because the target microservice architecture is mounted with a proxy plug-in, and the proxy plug-in can obtain the second full amount of information from the control plane component of the service grid, and the second full amount of information at least includes the application information of the second application, therefore, the target microservice architecture obtains the application information of the second application based on the service grid; based on this, it is possible to call the second application through the application information of the second application, thereby realizing the call of the application based on the target microservice architecture to the application based on the service grid, solving the problem in the related art that the service grid and the heterogeneous target microservice architecture (such as SpringCloud) cannot call each other, improving the scalability and overall performance of the system, and reducing the difficulty of development and maintenance.

[0167] In some embodiments, the application calling device method further includes a mounting module configured to mount a proxy plug-in to the target microservice architecture; the proxy plug-in and the control plane component each support a target protocol. The second acquisition module is further configured to obtain, based on the target protocol, second full information based on the service grid from the control plane component via the proxy plug-in; the second full information includes application information of all applications registered with the control plane component; and the second full information is sent to a registration center via the proxy plug-in.

[0168] In some embodiments, the second acquisition module is also used to convert the format of the second full information through a proxy plug-in; the second full information after format conversion meets the format requirements of the target microservice architecture; and the second full information after format conversion is sent to the registration center through the proxy plug-in.

[0169] In some embodiments, the application calling device further includes a second monitoring module and a second synchronization module. The second monitoring module is configured to monitor first full information based on the target microservice architecture; the first full information includes application information of all applications registered with the registration center. Upon detecting an update to the first full information, the second synchronization module is configured to synchronize the updated first full information to the service grid via the registration center.

[0170] Each module in the above-mentioned application calling device can be implemented in whole or in part through software, hardware, or a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor of the computer device in hardware form, or can be stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of each of the above modules.

[0171] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 13 As shown. The computer device includes a processor, memory, and a network interface connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, an application calling method is implemented.

[0172] Those skilled in the art will understand that Figure 13The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0173] In one embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps of the aforementioned method when executing the computer program.

[0174] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the aforementioned method are implemented.

[0175] In one embodiment, a computer program product is provided, comprising a computer program, which implements the steps of the aforementioned method when executed by a processor.

[0176] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0177] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the above-mentioned embodiments. In particular, any reference to memory, database, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processors involved in the various embodiments provided herein may be, but are not limited to, general-purpose processors, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), programmable logic devices (PLDs), data processing logic devices based on quantum computing, and the like.

[0178] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0179] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. An application calling method, characterized in that: Applied to a service grid, the method includes: Receiving a call request for a first application; the first application is an application provided based on a target microservice architecture; the target microservice architecture and the service grid are heterogeneous; Obtaining, through a control plane component of the service grid, application information of the first application from a registry of the target microservice architecture according to a call request for the first application; the control plane component and the registry are respectively configured with a target service; calling the first application according to the application information of the first application; The target service is a service natively provided by the registration center; the target service includes a messaging and collaboration platform service based on an extensible service discovery protocol; the control plane component is used to synchronously obtain application information in the target microservice architecture from the registration center based on the target service; The target microservice architecture is mounted with a proxy plug-in; each first application in the target microservice architecture is respectively mounted with a proxy plug-in; the proxy plug-in is used to obtain second full information from the control plane component and send the second full information to the registration center; the second full information includes at least application information of the second application; the second application is an application provided based on the service grid.

2. The method according to claim 1, characterized in that The obtaining, through the control plane component of the service grid, application information of the first application from a registration center of the target microservice architecture according to a call request for the first application, includes: configuring the target service on the control plane component; Based on the target service, obtaining, from the registration center through the control plane component, first full information based on the target microservice architecture; the first full information includes application information of all applications registered with the registration center, and the first full information includes at least application information of the first application; According to the call request for the first application, application information of the first application is obtained from the control plane component.

3. The method according to claim 2, characterized in that The service grid is configured with an edge proxy component; and obtaining application information of the first application from the control plane component according to a call request for the first application includes: Obtaining the first full information from the control plane component through the edge proxy component; The edge proxy component determines the application information of the first application from the first full information according to a call request for the first application.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: monitoring a second full amount of information of the service grid, wherein the second full amount of information includes application information of all applications registered with the control plane component; When it is monitored that the second full information is updated, the updated second full information is synchronized to the target microservice architecture through the control plane component.

5. An application calling method, characterized in that: Applied to the target microservice architecture, the method includes: Receiving a call request for a second application; the second application is an application provided based on a service grid; the service grid calls the first application using the application calling method according to any one of claims 1 to 4; the target microservice architecture and the service grid are heterogeneous; Obtaining application information of the second application from a registration center of the target microservice architecture according to a call request for the second application; The second application is called according to the application information of the second application.

6. The method according to claim 5, characterized in that The method further comprises: Mounting the proxy plug-in on the target microservice architecture; the proxy plug-in and the control plane component respectively support the target protocol; Based on the target protocol, obtaining second full information based on the service grid from the control plane component through the proxy plug-in; the second full information includes application information of all applications registered with the control plane component; The second full amount of information is sent to the registration center through the proxy plug-in.

7. The method according to claim 6, characterized in that The sending the second full amount of information to the registration center through the proxy plug-in includes: Performing format conversion on the second full amount of information by the proxy plug-in; the second full amount of information after format conversion complies with the format requirements of the target microservice architecture; The second full amount of information after format conversion is sent to the registration center through the proxy plug-in.

8. The method according to claim 5, characterized in that The method further comprises: Monitoring first full information based on the target microservice architecture; the first full information includes application information of all applications registered with the registration center; When it is detected that the first full information is updated, the updated first full information is synchronized to the service grid through the registration center.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 8 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

Images