WO2023273240A1

WO2023273240A1 - Micro-service calling method and apparatus, electronic device, and readable storage medium

Info

Publication number: WO2023273240A1
Application number: PCT/CN2021/140935
Authority: WO
Inventors: 伍锦盘; 黄润怀; 李旭
Original assignee: 天翼云科技有限公司
Priority date: 2021-06-29
Filing date: 2021-12-23
Publication date: 2023-01-05
Also published as: CN113364885A; CN113364885B

Abstract

The present application relates to the technical field of computers, and provides a micro-service calling method and apparatus, an electronic device, and a computer readable storage medium. The micro-service calling method comprises: in response to a calling request of a target micro-service sent by a micro-service calling end, obtaining a micro-service instance list matching the calling request, the micro-service list being used for recording micro-service information of all nodes on a micro-service instance chain, and the micro-service instance chain comprising at least one micro-service node; and sending the micro-service instance list to the micro-service calling end, so that the calling end calls the target micro-service on the basis of the micro-service instance list. By means of the technical solution of the present application, strong dependence on a registration center is eliminated, and thus, a call fault cannot be caused by a fault of the registration center, thereby improving the reliability of micro-service calling.

Description

Microservices invoke methods, devices, electronic devices and readable storage media

This application claims the priority of the Chinese patent application submitted to the China Patent Office on June 29, 2021, with the application number 202110726509.4, and the title of the invention is "microservice calling method, device, electronic device, and readable storage medium", the entire content of which Incorporated in this application by reference.

technical field

The present application relates to the field of computer technology, and in particular to a microservice calling method, device, electronic equipment, and computer-readable storage medium.

Background technique

The microservice architecture provides the discovery function of microservices by introducing a registration center. In the process of microservice registration and invocation, the registration center, as the overall server, provides microservice registration and client discovery, while microservice callers and microservice providers are implemented by the client.

When the application starts, the microservice provider will register the microservices provided by itself with the registry, and periodically send heartbeats to update the instance status.

The microservice caller obtains the required microservice list from the microservice registration center, caches it locally and periodically requests the registration center to update the state of the local cache, and after obtaining the microservice list, according to the microservice The name obtains the specific microservice instance and the access information of the instance, so as to further determine the selected instance to implement the call according to the load balancing strategy.

It can be seen from the above that the registration and discovery mechanism used by the current microservice architecture strongly relies on the registration center. If the registration center fails, all microservices may not be called.

It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the application, and therefore may include information that does not constitute prior art known to those of ordinary skill in the art.

Contents of the invention

The purpose of the present application is to provide a microservice invocation method, device, electronic device and computer-readable storage medium, at least to a certain extent, to overcome the problem of strong dependence on the registration center in the related art.

Other features and advantages of the present application will become apparent from the following detailed description, or in part, be learned by practice of the present application.

According to one aspect of the present application, a method for invoking a microservice is provided, including: in response to the invocation request of the target microservice sent by the microservice invocation end, obtaining a list of microservice instances matching the invocation request, the microservice list It is used to record the microservice information of all nodes on the microservice instance chain, and the microservice instance chain includes at least one of the microservice nodes; the microservice instance list is sent to the microservice calling end, that is, the The calling end calls the target microservice based on the microservice instance list.

In one embodiment of the present application, before obtaining the list of microservice instances matching the invocation request in response to the invocation request of the target microservice sent by the microservice invocation end, it further includes: based on the IP segment scanning operation, At least one of the microservice nodes is configured as the microservice instance chain; and the microservice instance list is generated based on the transfer operation of the microservice information of the microservice nodes along the microservice instance chain.

In one embodiment of the present application, the IP segment-based scanning operation constructs at least one of the microservice nodes as the microservice instance chain, which specifically includes: when receiving the registration information of the node to be registered, from the The IP segment information of the node to be registered is extracted from the registration information, and the node to be registered is the microservice node to be registered; when the microservice instance chain is an empty chain, based on the IP segment information, the The nodes to be registered are sorted to construct the microservice instance chain; when the microservice instance chain is a non-empty chain, the IP segment scan is performed on the microservice instance chain of the non-empty chain to determine the Describe the original front node and the original back node of the node to be registered, insert the said to-be-registered node between the original front node and the original back node, and record it as an insertion node, wherein the first IP of the original front node The segment information is the largest IP segment in the microservice instance chain that is smaller than the IP segment information, and the second IP segment information of the original node is the smallest IP segment in the microservice instance chain that is larger than the IP segment information. IP segment.

In an embodiment of the present application, the method further includes: returning registration success information to the node to be registered.

In one embodiment of the present application, the microservice instance chain is a circular instance chain.

In one embodiment of the present application, generating the microservice instance list based on the transfer operation of the microservice information of the microservice node along the microservice instance chain specifically includes: When the instance chain is an empty chain, keep the microservice information of the node to be registered in the microservice instance list; when the microservice instance chain is a non-empty chain, transfer the microservice information of the inserted node to the original rear node, so that the original rear node updates the microservice instance list, and passes the updated microservice instance list along the ring instance chain until it is passed to the insertion node, wherein , the microservice information includes at least one of node IP segment information, node port, microservice name, instance name, and instance detection interface.

In an embodiment of the present application, the method further includes: detecting the status of nodes in the microservice instance chain based on a preset detection frequency.

In one embodiment of the present application, the detecting the state of the nodes in the microservice instance chain based on the preset detection frequency specifically includes: when detecting the abnormal heartbeat of the previous microservice node, sending the previous The microservice node is set to an unavailable state in the microservice instance list, and updates the microservice instance list; when it is detected that the number of abnormal heartbeats of the previous microservice node reaches the abnormal threshold, the The microservice node is deleted from the microservice instance list, and the microservice instance list is updated, and the microservice instance chain is reconstructed.

According to another aspect of the present application, a microservice invocation method is provided, including: sending a microservice invocation request to a microservice node; receiving a microservice instance list fed back by the microservice node based on the invocation request, the The microservice list is used to record the instance information of at least one microservice node, and the at least one microservice node forms a chain structure; select the target microservice node from the microservice instance list based on the load balancing strategy; The access information of the service node invokes the target microservice.

According to another aspect of the present application, a microservice invocation device is provided, including: an acquisition module, configured to acquire a list of microservice instances matching the invocation request in response to the invocation request of the target microservice sent by the microservice invocation end , the microservice list is used to record the microservice information of all nodes on the microservice instance chain, and the microservice instance chain includes at least one microservice node; the first sending module is used to list the microservice instance sent to the microservice caller, that is, the caller invokes the target microservice based on the microservice instance list.

According to another aspect of the present application, a microservice invocation device is provided, including: a second sending module, configured to send a target microservice invocation request to a microservice node; a receiving module, configured to receive the microservice node based on the The microservice instance list of the call request feedback, the microservice list is used to record the instance information of at least one microservice node, and the at least one microservice node forms a chain structure; the selection module is used to select from all the microservice nodes based on the load balancing strategy Selecting a target microservice node from the list of microservice instances; a calling module, configured to call the target microservice based on the access information of the target microservice node.

According to another aspect of the present application, there is provided an electronic device, including: a processor; and a memory for storing executable instructions of the processor; wherein, the processor is configured to execute any of the above-mentioned first aspects by executing the executable instructions. One of the described microservice call methods.

According to another aspect of the present application, there is provided an electronic device, including: a processor; and a memory for storing executable instructions of the processor; wherein, the processor is configured to execute any of the above-mentioned second aspects by executing the executable instructions. One of the described microservice call methods.

According to yet another aspect of the present application, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, any one of the microservice calling methods above is implemented.

The microservice invocation scheme provided by the embodiment of the present application configures a microservice instance chain by using at least one microservice provider terminal as a microservice node, so that the microservice information belonging to all nodes on the microservice instance chain can be chained In this way, each microservice node can save the latest component status of all microservice nodes in the way of saving microservice information. Further, based on random transmission or polling transmission, the microservice provider terminal as a microservice node directly receives the target microservice invocation request sent by the microservice invocation terminal, so that the microservice provider terminal directly sends the microservice invocation terminal The microservice instance list that can realize the target microservice is fed back, so that the microservice calling terminal realizes the invocation of the target microservice based on the microservice instance list.

The above microservice call scheme, on the one hand, the above request and call process does not require the participation of the registration center, that is to say, it gets rid of the strong dependence on the registration center, so the call failure will not be caused by the failure of the registration center, thereby improving the micro service. Reliability of service calls. On the other hand, when the microservice instance chain includes multiple microservice nodes, since each microservice node stores a list of microservice instances, even if there is a faulty node, it can be fed back by other normal nodes. The list of instances and the calls to execute microservices can further improve the reliability of microservice calls.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description serve to explain the principles of the application. Apparently, the drawings in the following description are only some embodiments of the present application, and those skilled in the art can obtain other drawings according to these drawings without creative efforts.

FIG. 1 shows a flow chart of a method for invoking a microservice in an embodiment of the present application;

FIG. 2 shows a flow chart of another microservice calling method in the embodiment of the present application;

FIG. 3 shows a flowchart of another microservice calling method in the embodiment of the present application;

FIG. 4 shows a schematic structural diagram of a microservice instance chain in an embodiment of the present application;

FIG. 5 shows a flow chart of another microservice calling method in the embodiment of the present application;

FIG. 6 shows a flow chart of another microservice calling method in the embodiment of the present application;

FIG. 7 shows a flow chart of another microservice calling method in the embodiment of the present application;

FIG. 8 shows a flowchart of another microservice calling method in the embodiment of the present application;

FIG. 9 shows a flow chart of another microservice calling method in the embodiment of the present application;

FIG. 10 shows a schematic diagram of a microservice calling system in the embodiment of the present application;

FIG. 11 shows a schematic diagram of a microservice invocation device in the embodiment of the present application;

FIG. 12 shows a schematic diagram of another microservice invocation device in the embodiment of the present application;

FIG. 13 shows a schematic diagram of an electronic device in an embodiment of the present application; and

Fig. 14 shows a schematic diagram of a computer-readable storage medium in an embodiment of the present application.

detailed description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be thorough and complete, and will fully convey the concepts of example embodiments to those skilled in the art. The described features, structures or properties may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided in order to give a thorough understanding of embodiments of the present application. However, those skilled in the art will appreciate that the technical solutions of the present application can be practiced without one or more of the specified details, or other components, devices, steps, etc. can be adopted. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the application.

In addition, the drawings are only schematic illustrations of the present application, and the same reference numerals in the drawings represent the same or similar components, and thus their repeated descriptions will be omitted. Some of the block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different network and/or processor means and/or microcontroller means.

The exemplary implementation manners of the present application will be described in detail below in conjunction with the accompanying drawings.

As shown in Figure 1, the microservice provides the terminal to execute the microservice calling method, including the following steps:

Step S102, in response to the invocation request of the target microservice sent by the microservice caller, obtain a list of microservice instances matching the invocation request. The microservice list is used to record the microservice information of all nodes on the microservice instance chain. The microservice instance A chain includes at least one microservice node.

Among them, the microservice invocation terminal directly receives the invocation request of the target microservice sent by the microservice invocation terminal, that is, the invocation request of the target microservice sent by the microservice invocation terminal. The microservice provider terminal of the service instance is the microservice node.

The microservice instance chain is to sort multiple microservice nodes according to the specified sorting method, so that information can be exchanged between the microservice nodes, so that each microservice node can store all the microservice instances on the microservice instance chain. The microservice instance list of the microservice information of the service node.

Those skilled in the art can also understand that the microservice instance chain does not exclude the situation that there is only one microservice node.

In addition, the microservice instance chain can be an open chain structure or a closed chain structure.

Step S104, sending the microservice instance list to the microservice calling end, that is, the calling end invokes the target microservice based on the microservice instance list.

In this embodiment, at least one microservice provider terminal is used as a microservice node to configure a microservice instance chain, so that the microservice information belonging to all nodes on the microservice instance chain can be transmitted in a chain, so that each Each microservice node can save the latest component status of all microservice nodes in the way of saving microservice information. Further, based on random transmission or polling transmission, the microservice provider terminal as a microservice node directly receives the target microservice invocation request sent by the microservice invocation terminal, so that the microservice provider terminal directly sends the microservice invocation terminal Feedback can realize the microservice instance list of the target microservice, so that the microservice calling terminal can realize the invocation of the target microservice based on the microservice instance list. Strong dependence on the registry, so the failure of the registry will not cause call failures, which can improve the reliability of microservice calls. On the other hand, when the microservice instance chain includes multiple microservice nodes, because each Each microservice node stores a list of microservice instances. Even if there is a faulty node, other normal nodes can feed back the instance list and execute the called microservice, so the reliability of microservice invocation can be further improved.

In addition, those skilled in the art can also understand that the microservice providing terminal as the execution subject can be any microservice node in the microservice instance chain, or a microservice node to be registered.

As shown in Figure 2, in one embodiment of the present application, in step S102, in response to the invocation request of the target microservice sent by the microservice caller, before obtaining the list of microservice instances matching the invocation request, it also includes:

Step S202, constructing at least one microservice node as a microservice instance chain based on an IP segment scanning operation.

Among them, when the node is started, only the address segment of the node needs to be configured without specifying a specific IP address. The IP address can be configured flexibly, and the IP segment scanning of other nodes that can belong to the same microservice instance chain can be performed, which can improve the scanning efficiency.

Step S204, based on the transfer operation of the microservice information of the microservice nodes along the microservice instance chain, a list of microservice instances is generated.

In this embodiment, by configuring the IP address segment for the started node, and scanning the node address based on the IP address segment, and then sorting the multiple micro-service nodes based on the scanning structure, the micro-service instance chain is obtained, and further based on the micro-service instance The chain can perform information transfer and list update to ensure that microservices are effectively invoked.

As shown in Figure 3, in one embodiment of the present application, step S202, based on the IP segment scanning operation, constructs at least one microservice node as a specific implementation of a microservice instance chain, including:

Step S302, when the registration information of the node to be registered is received, the IP segment information of the node to be registered is extracted from the registration information, and the node to be registered is a microservice node to be registered.

Wherein, the registration information of the node to be registered may be the same as the microservice information of the node.

Step S304, when the microservice instance chain is empty, sort the nodes to be registered based on the IP segment information to construct a microservice instance chain.

Step S306, when the microservice instance chain is a non-empty chain, perform an IP segment scan on the microservice instance chain of the non-empty chain to determine the original front node and the original back node of the node to be registered, and insert the node to be registered into the original front node Between the node and the original node, it is recorded as an insertion node.

Among them, the first IP segment information of the original former node is the largest IP segment smaller than the IP segment information in the microservice instance chain, and the second IP segment information of the original post node is the smallest IP segment larger than the IP segment information in the microservice instance chain part.

As shown in Figure 3, in an embodiment of the present application, it also includes:

Step S308, returning registration success information to the node to be registered.

In this embodiment, the microservice instance chain is constructed by sorting the nodes based on the size of the IP segment, so that microservice information can be transmitted between nodes with similar IP addresses.

As shown in Figure 4, each microservice instance represents a microservice node. Microservice instance 1 to microservice instance 8 form a circular instance chain, and the instance information of the microservice node is transmitted in the ring in a chained manner. At the same time, each instance simultaneously updates the state of all components currently saved in the local machine during the transfer process. By constructing a ring-shaped instance chain, a complete list of instances can be generated after passing around one by one, and further passed in sequence, so that each microservice node can save the list of microservice instances, no matter which microservice node receives the call request , the instance list can be sent to the calling terminal, so that the calling terminal can execute the calling operation smoothly.

As shown in Figure 5, in one embodiment of the present application, in step S204, based on the transfer operation of the microservice information of the microservice nodes along the microservice instance chain, a specific implementation manner of generating a list of microservice instances includes :

Step S502, when the microservice instance chain is empty, keep the microservice information of the node to be registered in the microservice instance list.

Step S504, when the microservice instance chain is non-empty, transfer the microservice information of the inserted node to the original post node, so that the original post node updates the microservice instance list, and sends the updated microservice instance list along the ring instance The chain is passed until it is passed to the insertion node.

Wherein, the microservice information includes at least one of node IP segment information, node port, microservice name, instance name and instance detection interface.

In this embodiment, when the microservice instance chain is an empty chain, the node to be registered can be understood as the original node, that is, the node that constructs the microservice instance list; when the microservice instance chain is a non-empty chain, the node to be registered can understand To insert a node, that is, update the microservice instance list based on the microservice information of the inserted node, and then realize the construction and update of the microservice instance list.

As shown in Figure 6, according to the registration process of the microservice node in the microservice invocation scheme of the present application, it includes:

In step S602, the node to be registered performs an IP segment scanning operation.

Step S604, check whether other microservice nodes in the instance chain are scanned, if the detection result is "Yes", go to Step S608, and if the detection result is "No", go to Step S606.

Step S606, generating a microservice instance list based on its own microservice information.

Step S608, sending its own microservice information to the next adjacent microservice node to perform a registration operation.

In step S610, the latter microservice node registers the node to be registered based on the registration information, and returns registration success information to the node to be registered, and the node to be registered is changed to a registered node.

In step S612, the latter microservice node transmits the registration information in a circular manner.

Step S614, the registration node receives the microservice instance list, and selects the previous microservice node from the microservice instance list.

Step S616, the registration node updates the microservice instance list based on the selected previous microservice node to form a new circular instance chain.

Specifically, when a node starts up, it scans backwards according to the specified IP segment, which is called ring scan. When scanning to a post-node whose IP segment is larger than its own, stop scanning and save its own microservice instance information, including but not limited to the following information: current machine IP, port, current microservice name, instance name, instance detection interface Wait for the specific information to be sent to the target machine, that is, the post node. After receiving the successful registration information, pull the entire microservice list information of the target machine to the local and save it.

Obtain the largest IP that is smaller than itself in the registration list as its own front node, and insert the node between the front node and the back node to form a circular instance chain.

When no other available service can be found even when it loops to the IP deployed by itself during registration, it saves its own component information as the only instance in the microservice list, and terminates the scan.

When the component runs healthy and receives the registration information of the new node, check the registered node information. If the node information is greater than the current node IP value, write the node information to the microservice list, and then return success to the newly registered node information.

Further, the registration information of the new node is sent to the original front node and the back node. After receiving the information, the original front node pulls a complete list of microservices and adjusts its own back node.

After the post node in the original chain receives the new registration information, it transmits its registration information to its own post node until the registration information is updated to all microservice nodes in the ring and then stops.

In this embodiment, the availability and reachability of microservices are ensured through a mutual detection mechanism, and its component status is more accurate than heartbeat updates.

As shown in Figure 7, in one embodiment of the present application, the detection of the node status in the microservice instance chain based on the preset detection frequency specifically includes:

Step S702, when detecting an abnormal heartbeat of the previous microservice node, setting the previous microservice node to an unavailable state in the microservice instance list, and updating the microservice instance list.

Step S704, when it is detected that the number of abnormal heartbeats of the previous microservice node reaches the abnormal threshold, delete the previous microservice node from the microservice instance list, update the microservice instance list, and reconstruct the microservice instance chain.

In this embodiment, by using the subsequent node in the chain to detect the heartbeat of the adjacent previous node, instead of reporting its own heartbeat information to the registration center in the related art, it is possible to improve the exception handling when the node is abnormal. real-time and reliability.

As shown in Figure 8, in one embodiment of the present application, detecting the state of the nodes in the microservice instance chain based on the preset detection frequency specifically includes:

Step S802, any current node detects the heartbeat information of the previous node.

Step S804, based on the heartbeat information, detect whether the heartbeat of the previous node is normal, if the detection result is "Yes", proceed to Step S806, and if the detection result is "No", proceed to Step S808.

Step S806, recording the detection time.

Step S808, detect whether the number of abnormal heartbeats reaches the abnormal threshold, if the detection result is "Yes", proceed to Step S810, and if the detection result is "No", proceed to Step S812.

Step S810, delete the former node from the microservice instance list.

Step S812, setting the state of the previous node as unreachable, and updating the instance list.

In step S814, the state information is transmitted to the subsequent node.

Step S816, after detecting whether the node is reachable, if the detection result is "yes", go to step S820, and if the detection result is "no", go to step S818.

Step S818, selecting a node following the post node as a temporary post node.

Step S820, circularly transmit the updated instance list.

Step S822, until the updated instance list is delivered to the current node.

Specifically, in the component, that is, the node state detection process, when the microservice component is successfully registered on the chain, the timing detection task will be started. When the timing detection task occurs, the current node needs to detect the state of the previous node. The state is not abnormal, the current node only records its health detection history, but there is no need to synchronize data to the backward node.

When the previous node fails, that is, when the heartbeat is abnormal, if the configured heartbeat abnormal threshold is not reached, only the status of the previous node in the microservice list is set as unavailable, and it is passed to the subsequent node. If the later node is unavailable at this time, then further take the next node in the ring as a temporary later node to send an information synchronization signal until all new information is synchronized to the entire ring and then ends.

When the number of abnormal heartbeats of the previous node is detected to be greater than or equal to the abnormal threshold, the previous node is removed from the microservice list and passed to the backward node until the new information is synchronized to the entire ring, and at the same time one is taken from the microservice list Nodes that happen to be smaller than themselves to form new rings.

When a node receives the synchronization information and finds that the current post-node information is no longer behind the registration list, the post-node information in the new ring from the new registration list information is used as the post-node to form a new ring.

If a node has formed a new ring, but still receives the synchronization signal from the previous node, it will return refresh failure.

When a node receives a failure message when synchronizing information backwards, the local microservice list information is used, and the registration process is re-executed.

As shown in Figure 9, an implementation of the microservice invocation terminal to execute the microservice invocation method includes the following steps:

Step S902, sending an invocation request of the target microservice to the microservice node.

Step S904, receiving the microservice instance list fed back by the microservice node based on the call request, the microservice list is used to record instance information of at least one microservice node, and at least one microservice node forms a chain structure.

Step S906, selecting a target microservice node from the list of microservice instances based on the load balancing policy.

Step S908, calling the target microservice based on the access information of the target microservice node.

As shown in FIG. 10 , another implementation manner in which the microservice invocation terminal executes the microservice invocation method includes the following steps:

Step S1002, the microservice calling terminal initiates a remote calling request.

In step S1004, a list of matching microservice instances is obtained based on the name of the microservice.

Step S1006, check whether there is the required target microservice in the microservice instance list, if the detection result is "No", go to step S1008, and if the detection result is "Yes", go to step S1010.

Step S1008, returning an error message to the microservice providing terminal.

Step S1010, obtain an access address of a running instance from the list of detected microservice instances based on the load balancing strategy.

Step S1012, perform a remote call operation based on the instance access address.

Step S1014, check whether the calling operation is successful, if the detection result is "No", go to Step S1016, and if the detection result is "Yes", go to Step S1018.

Step S1016, detect whether there is another available instance address in the microservice instance list, if the detection result is "No", go to Step S1020, and if the detection result is "Yes", return to Step S1012.

Step S1018, return the call result.

Step S1020, returning an error message to the microservice providing terminal.

Specifically, based on the ring transfer mechanism, the entire microservice list information is stored at each microservice point, and it can be quickly synchronized to the ring no matter when a node is unhealthy or new. Therefore, when calling, directly obtain the list of microservice instances whose microservice status is available according to the name of the microservice that needs to be called, and then select the actual microservice instance to call according to the configuration low to high availability strategy.

It should be noted that the above-mentioned figures are only schematic illustrations of processes included in the method according to the exemplary embodiments of the present disclosure, and are not intended to be limiting. It is easy to understand that the processes shown in the above figures do not imply or limit the chronological order of these processes. In addition, it is also easy to understand that these processes may be executed synchronously or asynchronously in multiple modules, for example.

Those skilled in the art can understand that various aspects of the present application can be implemented as a system, method or program product. Therefore, various aspects of the present application can be specifically implemented in the following forms, that is: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software implementations, which can be collectively referred to herein as "circuit", "module" or "system".

The microservice calling apparatus 1100 according to this embodiment of the present application will be described below with reference to FIG. 11 . The microservice invoking apparatus 1100 shown in FIG. 11 is only an example, and should not impose any limitation on the functions and application scope of this embodiment of the present application.

The microservice calling device 1100 is expressed in the form of a hardware module. The components of the microservice invocation apparatus 1100 may include but not limited to: an acquisition module 1102, configured to respond to the invocation request of the target microservice sent by the microservice invocation end, and obtain a list of microservice instances matching the invocation request, and the microservice list is used for Record the microservice information of all nodes on the microservice instance chain, the microservice instance chain includes at least one microservice node; the first sending module 1104 is used to send the microservice instance list to the microservice calling end, that is, the calling end is based on the microservice A list of service instances to call the target microservice.

In one embodiment of the present application, it also includes: a construction module 1106, configured to construct at least one microservice node as a microservice instance chain based on an IP segment scanning operation; The microservice information transfer operation of the microservice node generates a list of microservice instances.

In one embodiment of the present application, the construction module 1106 is also used to: when receiving the registration information of the node to be registered, extract the IP segment information of the node to be registered from the registration information, and the node to be registered is a microservice node to be registered ; When the microservice instance chain is an empty chain, sort the nodes to be registered based on the IP segment information to construct a microservice instance chain; when the microservice instance chain is a non-empty chain, execute Scan the IP segment to determine the original front node and the original back node of the node to be registered, insert the node to be registered between the original front node and the original back node, and record it as an inserted node, where the first IP segment information of the original front node is The microservice instance chain is smaller than the largest IP segment in the IP segment information, and the second IP segment information of the original node is the smallest IP segment in the microservice instance chain that is larger than the IP segment information.

In one embodiment of the present application, it further includes: a return module 1110, configured to return registration success information to the node to be registered.

In one embodiment of the present application, the delivery module 1108 is also used to: when the microservice instance chain is an empty chain, keep the microservice information of the node to be registered in the microservice instance list; when the microservice instance chain is non-empty When chaining, the microservice information of the inserted node is transmitted to the original post node, so that the original post node updates the microservice instance list, and the updated microservice instance list is passed along the ring instance chain until it is passed to the inserted node, wherein, The microservice information includes at least one of node IP segment information, node port, microservice name, instance name and instance detection interface.

In one embodiment of the present application, it further includes: a detection module 1112, configured to detect the status of nodes in the microservice instance chain based on a preset detection frequency.

In one embodiment of the present application, the detection module 1112 is also used to: when detecting an abnormal heartbeat of the previous microservice node, set the previous microservice node to an unavailable state in the microservice instance list, and update the microservice Instance list; when detecting that the number of abnormal heartbeats of the previous microservice node reaches the abnormal threshold, delete the previous microservice node from the list of microservice instances, update the list of microservice instances, and reconstruct the chain of microservice instances.

The microservice calling apparatus 1200 according to this embodiment of the present application will be described below with reference to FIG. 12 . The microservice invoking apparatus 1200 shown in FIG. 12 is only an example, and should not limit the functions and scope of use of this embodiment of the present application.

The microservice calling device 1200 is expressed in the form of a hardware module. Components of the microservice invocation apparatus 1200 may include but not limited to: a second sending module 1202, configured to send the invocation request of the target microservice to the microservice node; a receiving module 1204, configured to receive the microservice fed back by the microservice node based on the invocation request The instance list, the microservice list is used to record the instance information of at least one microservice node, and at least one microservice node forms a chain structure; the selection module 1206 is used to select the target microservice node from the microservice instance list based on the load balancing strategy; A calling module 1208, configured to call the target microservice based on the access information of the target microservice node.

An electronic device 1300 according to this embodiment of the present application is described below with reference to FIG. 13 . The electronic device 1300 shown in FIG. 13 is only an example, and should not limit the functions and scope of use of this embodiment of the present application.

As shown in FIG. 13, electronic device 1300 takes the form of a general-purpose computing device. Components of the electronic device 1300 may include but not limited to: at least one processing unit 1310 , at least one storage unit 1320 , and a bus 1330 connecting different system components (including the storage unit 1320 and the processing unit 1310 ).

Wherein, the storage unit stores program codes, and the program codes can be executed by the processing unit 1310, so that the processing unit 1310 executes the steps according to various exemplary embodiments of the present application described in the “Exemplary Method” section of this specification. For example, the processing unit 1310 may execute steps S202, S204, S206, and S208 as shown in FIG. 1, and other steps defined in the microservice calling method of the present application.

The storage unit 1320 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 13201 and/or a cache storage unit 13202 , and may further include a read-only storage unit (ROM) 13203 .

The storage unit 1320 may also include a program/utility 13204 having a set (at least one) of program modules 13205, such program modules 13205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, Implementations of networked environments may be included in each or some combination of these examples.

Bus 1330 may represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local area using any of a variety of bus structures. bus.

Electronic device 1300 may also communicate with one or more external devices 1370 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), and may also communicate with one or more devices that enable a user to interact with the electronic device, and/or communicate with one or more devices that enable The electronic device 1300 is capable of communicating with any device (eg, router, modem, etc.) that communicates with one or more other computing devices. Such communication may occur through input/output (I/O) interface 1350 . Moreover, the electronic device 1300 can also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN) and/or a public network such as the Internet) through the network adapter 1360 . As shown, the network adapter 1360 communicates with other modules of the electronic device 1300 through the bus 1330 . It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and Data backup storage system, etc.

Through the description of the above implementations, those skilled in the art can easily understand that the example implementations described here can be implemented by software, or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of the present application can be embodied in the form of software products, which can be stored in a non-volatile storage medium (which can be CD-ROM, U disk, mobile hard disk, etc.) or on the network , including several instructions to make a computing device (which may be a personal computer, server, terminal device, or network device, etc.) execute the method according to the embodiment of the present application.

In an exemplary embodiment of the present application, a computer-readable storage medium is also provided, on which a program product capable of implementing the above-mentioned method in this specification is stored. In some possible implementations, various aspects of the present application can also be implemented in the form of a program product, which includes program code. When the program product runs on the terminal device, the program code is used to make the terminal device execute the above-mentioned Steps according to various exemplary embodiments of the present application described in the "Exemplary Methods" section.

As shown in FIG. 14 , a program product 1400 for implementing the above method according to an embodiment of the present application is described, which can adopt a portable compact disk read-only memory (CD-ROM) and include program codes, and can be used in terminal equipment, For example running on a personal computer. However, the program product of the present application is not limited thereto. In this document, a readable storage medium may be any tangible medium containing or storing a program, and the program may be used by or in combination with an instruction execution system, device, or device.

A computer readable signal medium may include a data signal carrying readable program code in baseband or as part of a carrier wave. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium other than a readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program codes for performing the operations of the present application may be written in any combination of one or more programming languages, including object-oriented programming languages—such as Java, C++, etc., as well as conventional procedural programming languages. Programming language - such as "C" or a similar programming language. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server to execute. In cases involving a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., using an Internet service provider). business to connect via the Internet).

It should be noted that although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. Actually, according to the embodiment of the present application, the features and functions of two or more modules or units described above may be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided to be embodied by a plurality of modules or units.

In addition, although the steps of the methods of the present application are described in a specific order in the drawings, this does not require or imply that the steps must be performed in that specific order, or that all illustrated steps must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step for execution, and/or one step may be decomposed into multiple steps for execution, etc.

Through the description of the above implementations, those skilled in the art can easily understand that the example implementations described here can be implemented by software, or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of the present application can be embodied in the form of software products, which can be stored in a non-volatile storage medium (which can be CD-ROM, U disk, mobile hard disk, etc.) or on the network , including several instructions to make a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) execute the method according to the embodiment of the present application.

Other embodiments of the present application will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any modification, use or adaptation of the application, these modifications, uses or adaptations follow the general principles of the application and include common knowledge or conventional technical means in the technical field not disclosed in the application . The specification and examples are to be considered exemplary only, with a true scope and spirit of the application indicated by the appended claims.

Claims

A method for invoking microservices, applied to microservice nodes, characterized in that it includes:

In response to the invocation request of the target microservice sent by the microservice calling end, obtain a list of microservice instances matching the invocation request, the microservice list is used to record the microservice information of all nodes on the microservice instance chain, the The microservice instance chain includes at least one microservice node;

The microservice instance list is sent to the microservice calling end, that is, the calling end invokes the target microservice based on the microservice instance list.
The method for invoking microservices according to claim 1, wherein, before obtaining a list of microservice instances matching the invocation request in response to the invocation request of the target microservice sent by the microservice invocation end, further comprising: :

Constructing at least one of said microservice nodes as said microservice instance chain based on an IP segment scanning operation; and

The microservice instance list is generated based on the transfer operation of the microservice information of the microservice node along the microservice instance chain.
The method for invoking microservices according to claim 2, wherein the scanning operation based on the IP segment constructs at least one microservice node as the microservice instance chain, specifically comprising:

When receiving the registration information of the node to be registered, extracting the IP segment information of the node to be registered from the registration information, the node to be registered is the microservice node to be registered;

When the microservice instance chain is an empty chain, sort the nodes to be registered based on the IP segment information to construct the microservice instance chain;

When the microservice instance chain is a non-empty chain, the IP segment scan is performed on the microservice instance chain of the non-empty chain to determine the original front node and the original post node of the node to be registered, and the The node to be registered is inserted between the original front node and the original rear node, which is recorded as an inserted node,

Wherein, the first IP segment information of the original former node is the largest IP segment in the microservice instance chain smaller than the IP segment information, and the second IP segment information of the original post node is the microservice instance The smallest IP segment in the chain that is larger than the IP segment information.
The microservice calling method according to claim 3, further comprising:

Return registration success information to the node to be registered.
The microservice calling method according to claim 3, wherein the microservice instance chain is a ring instance chain.
The microservice invocation method according to claim 5, wherein the microservice instance list is generated based on the transfer operation of the microservice information of the microservice node along the microservice instance chain, specifically include:

When the microservice instance chain is an empty chain, keep the microservice information of the node to be registered in the microservice instance list;

When the microservice instance chain is a non-empty chain, the microservice information of the inserted node is transferred to the original post node, so that the original post node updates the microservice instance list, and the updated The microservice instance list is passed along the ring instance chain until it is passed to the insertion node,

Wherein, the microservice information includes at least one of node IP segment information, node port, microservice name, instance name and instance detection interface.
The microservice invocation method according to any one of claims 3 to 6, further comprising:

The state of the nodes in the microservice instance chain is detected based on a preset detection frequency.
The method for invoking microservices according to claim 7, wherein the detection of the node status in the microservice instance chain based on the preset detection frequency specifically includes:

When an abnormal heartbeat of the previous microservice node is detected, the previous microservice node is set to an unavailable state in the microservice instance list, and the microservice instance list is updated;

When it is detected that the number of abnormal heartbeats of the previous microservice node reaches the abnormal threshold, the previous microservice node is deleted from the microservice instance list, and the microservice instance list is updated, and all the microservice instances are reconstructed. The microservice instance chain described above.
A microservice invocation method applied to a microservice invocation end, characterized in that it includes:

Send the invocation request of the target microservice to the microservice node;

receiving the microservice instance list fed back by the microservice node based on the call request, the microservice list is used to record instance information of at least one microservice node, and the at least one microservice node forms a chain structure;

Selecting a target microservice node from the list of microservice instances based on a load balancing strategy;

Invoking the target microservice based on the access information of the target microservice node.
A microservice invocation device applied to a microservice node, characterized in that it includes:

The obtaining module is used to respond to the invocation request of the target microservice sent by the microservice caller, and obtain a list of microservice instances matching the invocation request, and the microservice list is used to record the microservices of all nodes on the microservice instance chain. Service information, the microservice instance chain includes at least one microservice node;

The first sending module is configured to send the microservice instance list to the microservice caller, that is, the caller calls the target microservice based on the microservice instance list.
A microservice invocation device applied to a microservice invocation end, characterized in that it includes:

The second sending module is used to send the invocation request of the target microservice to the microservice node;

A receiving module, configured to receive a microservice instance list fed back by the microservice node based on the call request, the microservice list is used to record instance information of at least one microservice node, and the at least one microservice node forms a chain structure;

A selection module, configured to select a target microservice node from the list of microservice instances based on a load balancing strategy;

A calling module, configured to call the target microservice based on the access information of the target microservice node.
An electronic device, characterized in that it comprises:

processor; and

a memory for storing executable instructions of the processor;

Wherein, the processor is configured to execute the microservice invocation method described in any one of claims 1 to 8 by executing the executable instructions.
An electronic device, characterized in that it comprises:

processor; and

a memory for storing executable instructions of the processor;

Wherein, the processor is configured to execute the microservice calling method of claim 9 by executing the executable instructions.
A computer-readable storage medium, on which a computer program is stored, wherein, when the computer program is executed by a processor, the method for invoking a microservice according to any one of claims 1 to 9 is implemented.