CN109104491A - A kind of micro services call method, device, server and storage medium - Google Patents

Abstract

The present invention discloses a microservice calling method, device, server and storage medium. The method includes: receiving the calling request corresponding to the current microservice sent by the current consumer through an interceptor; wherein, the calling request carries the The service level of the current microservice; in response to the call request corresponding to the current microservice, obtain the thread pool resource corresponding to the current microservice in the thread pool where the current microservice is located; use the thread corresponding to the current microservice The pool resource calls the current microservice within a preset calling time. It can not only improve the calling efficiency of microservices, but also ensure the stability of calling microservices.

Description

A microservice calling method, device, server and storage medium

technical field

The invention relates to the technical field of virtual machines, in particular to a microservice calling method, device, server and storage medium.

Background technique

With the development of information technology, cloud computing has gradually become a hot spot in the industry, and cloud computing service platforms of major manufacturers at home and abroad have also begun to invest in science, education, culture, health, government, high-performance computing, e-commerce, and the Internet of Things. used in many fields.

The Yunhai OS system provides tenants with virtual computing and storage network services. In the cloud operating system, a microservice architecture can be used to implement distributed deployment. There are multiple consumers in the entire system, and the consumers can call the microservices provided by the server. With the increase of system functions, the interaction between the consumer and the server becomes extremely frequent; in addition, there are batch operations, such as batch creation of thousands of virtual machines. Creating a virtual machine requires computing services, network services, storage services, logging services, etc. Under high concurrent access, the stability of these dependencies has a great impact on the system, but there are many uncontrollable problems in dependencies: Slow network connection, busy resource, temporarily unavailable, service offline, etc.

In the process of realizing the present invention, the inventor finds that there are at least the following problems in the prior art:

In the existing microservice invocation method, there is no isolation measure for highly concurrent microservice invocation, and the current microservice has the risk of being dragged down. For example: a system that depends on 30 SOA microservices, each microservice is 99.99% available. The 30th power of 99.99% ≈ 99.7%, 0.3% means that there will be 300,000 failures for 100 million requests. Converted to about 2 hours per month, microservices are unstable. As the number of dependencies increases, microservices will not The probability of stability increases exponentially.

Contents of the invention

In order to solve the above technical problems, the present invention provides a microservice calling method, device, server and storage medium, which can not only improve the calling efficiency of the microservice, but also ensure the stability of the calling of the microservice.

In order to achieve the purpose of the present invention, in the first aspect, the present invention provides a method for invoking microservices, the method comprising:

Receive the invocation request corresponding to the current microservice sent by the current consumer through the interceptor; wherein, the invocation request carries the service level of the current microservice;

In response to the call request corresponding to the current microservice, obtain the thread pool resource corresponding to the current microservice in the thread pool where the current microservice is located;

Using the thread pool resources corresponding to the current microservice to call the current microservice within a preset call time.

In the above embodiment, the method further includes:

If the thread pool resource corresponding to the current microservice is used to successfully call the current microservice within the preset call time, return a call success message to the current consumer;

If the thread pool resource corresponding to the current microservice fails to call the current microservice within the preset call time, return a call failure message to the current consumer.

In the above embodiment, the acquisition of the thread pool resource corresponding to the current microservice in the thread pool where the current microservice is located in response to the call request corresponding to the current microservice includes:

In response to the call request corresponding to the current microservice, determine whether the thread pool where the current microservice is located has reached saturation;

If the thread pool where the current microservice is located has reached saturation, then downgrade the service level of the current microservice; and obtain the current microservice in the thread pool where the current microservice is located according to the degraded call request The thread pool resource corresponding to the service;

If the thread pool where the current microservice is located is not saturated, then maintain the service level corresponding to the current microservice; and obtain the current microservice in the thread pool where the current microservice is located according to the call request The thread pool resource corresponding to the service.

In the above embodiment, the method further includes:

Obtain the running status of the current microservice through a fuse; wherein, the running status includes: success status, failure status, rejection status and timeout status;

Perform corresponding processing on the current microservice according to the running state of the current microservice.

In the second aspect, the present invention also provides a microservice calling device, which includes: a receiving module, an acquiring module, and a calling module; wherein,

The receiving module is configured to receive the invocation request corresponding to the current microservice sent by the current consumer through the interceptor; wherein, the invocation request carries the service level of the current microservice;

The acquiring module is configured to acquire the thread pool resource corresponding to the current microservice in the thread pool where the current microservice is located in response to the call request corresponding to the current microservice;

The calling module is configured to use the thread pool resource corresponding to the current microservice to call the current microservice within a preset calling time.

In the above embodiment, the invoking module is further configured to: if the invocation of the current microservice is successful within the preset invocation time using the thread pool resource corresponding to the current microservice, then send a message to the current consumer Return a call success message; if the thread pool resource corresponding to the current microservice fails to call the current microservice within the preset call time, return a call failure message to the current consumer.

In the above embodiment, the acquiring module includes: a judging submodule and an acquiring submodule; wherein,

The judging submodule is used to judge whether the thread pool where the current microservice is located has reached saturation in response to the call request corresponding to the current microservice;

The obtaining sub-module is used to downgrade the service level of the current microservice if the thread pool where the current microservice is located has reached saturation; Obtain the thread pool resources corresponding to the current microservice from the thread pool; if the thread pool where the current microservice is located is not saturated, then keep the service level corresponding to the current microservice; A thread pool resource corresponding to the current microservice is obtained from the thread pool where the current microservice is located.

In the above embodiment, the calling module is also used to obtain the running status of the current microservice through a fuse; wherein, the running status includes: success status, failure status, rejection status and timeout status; according to the The running state of the current microservice performs corresponding processing on the current microservice.

In a third aspect, an embodiment of the present invention provides a server, including:

one or more processors;

memory for storing one or more programs,

When the one or more programs are executed by the one or more processors, the one or more processors implement the microservice calling method described in any embodiment of the present invention.

In a fourth aspect, an embodiment of the present invention provides a storage medium on which a computer program is stored, and when the program is executed by a processor, the method for invoking a microservice described in any embodiment of the present invention is implemented.

The embodiment of the present invention proposes a microservice invocation method, device, server, and storage medium. First, the invocation request corresponding to the current microservice sent by the current consumer is received through an interceptor; wherein, the invocation request carries the service level of the current microservice ; Then in response to the call request corresponding to the current microservice, obtain the thread pool resource corresponding to the current microservice in the thread pool where the current microservice is located; finally use the thread pool resource corresponding to the current microservice to call the current microservice within the preset call time to make the call. That is to say, in the technical solution of the present invention, the thread pool resource corresponding to the current microservice can be obtained in the thread pool where the current microservice is located in response to the call request corresponding to the current microservice, so that the thread corresponding to the current microservice can be used The pool resource calls the current microservice within the preset call time. However, in the existing microservice calling methods, there is no isolation measure for highly concurrent microservice calls, and the current microservices are at risk of being dragged down. Therefore, compared with the prior art, the microservice invocation method, device, server, and storage medium proposed in the embodiments of the present invention can not only improve the invocation efficiency of microservices, but also ensure the invocation stability of microservices; and, the present invention The technical solution of the embodiment of the invention is simple and convenient to implement, easy to popularize, and has a wider application range.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Description of drawings

The accompanying drawings are used to provide a further understanding of the technical solution of the present invention, and constitute a part of the description, and are used together with the embodiments of the application to explain the technical solution of the present invention, and do not constitute a limitation to the technical solution of the present invention.

FIG. 1 is a schematic flow diagram of a microservice calling method provided in Embodiment 1 of the present invention;

FIG. 2 is a schematic flowchart of a microservice invocation method provided by Embodiment 2 of the present invention;

FIG. 3 is a schematic flowchart of a microservice invocation method provided by Embodiment 3 of the present invention;

FIG. 4 is a schematic diagram of a first structure of a microservice calling device provided in Embodiment 4 of the present invention;

FIG. 5 is a schematic diagram of a second structure of a microservice calling device provided in Embodiment 4 of the present invention;

FIG. 6 is a schematic structural diagram of a server provided in Embodiment 5 of the present invention.

Detailed ways

In order to make the purpose, technical solution and advantages of the present invention more clear, the embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined arbitrarily with each other.

Embodiment one

Fig. 1 is a schematic flow chart of a microservice invocation method provided by Embodiment 1 of the present invention. The method can be executed by a microservice invocation device or server, and the device or server can be implemented by software and/or hardware. The device or server Can be integrated in any smart device with network communication function. As shown in Figure 1, the microservice invocation method may include the following steps:

Step 101: Receive the invocation request corresponding to the current microservice sent by the current consumer through the interceptor; wherein, the invocation request carries the service level of the current microservice.

In a specific embodiment of the present invention, the server may receive the invocation request corresponding to the current microservice sent by the current consumer through the interceptor; wherein, the invocation request carries the service level of the current microservice. Specifically, all invocation requests sent by each consumer end to the server will pass through the interceptor, and the interceptor will process each invocation request accordingly after receiving the invocation request sent by each consumer end. Specifically, the interceptor can judge whether the call request received is a legal call request. If the interceptor judges that the call request is a legal call request, the interceptor will report the call request to the server; If the invocation request is an illegal invocation request, the interceptor will not report the invocation request to the server.

In a specific embodiment of the present invention, the service level of the current microservice can be carried in the call request sent by each consumer to the server, and the service level can be a predetermined priority of the current microservice, indicating the importance of the current microservice ; The higher the service level of the current microservice, the more important the current microservice is; the lower the service level of the current microservice, the less important the current microservice is.

Step 102 , in response to the call request corresponding to the current microservice, obtain the thread pool resource corresponding to the current microservice from the thread pool where the current microservice is located.

In a specific embodiment of the present invention, the server may obtain the thread pool resource corresponding to the current microservice from the thread pool where the current microservice is located in response to the call request corresponding to the current microservice. Specifically, the server may first determine the thread pool where the current microservice is located according to the call request corresponding to the current microservice, and then obtain the thread pool resources corresponding to the current microservice from the thread pool where the current microservice is located. If the server obtains the thread pool resources corresponding to the current microservice in the thread pool where the current microservice is located, the server can use the thread pool resources corresponding to the current microservice to call the current microservice within the preset call time; if the server is in If the thread pool resource corresponding to the current microservice is not obtained from the thread pool where the current microservice is located, the server can end the call to the current microservice. That is to say, in a specific embodiment of the present invention, the server obtains the thread pool resources corresponding to the current microservice in the thread pool where the current microservice is located, instead of obtaining the thread pool resources corresponding to the current microservice in all thread pools , therefore, the calling efficiency of the microservice can be improved, and the stability of the calling of the microservice can also be guaranteed.

Step 103, using the thread pool resources corresponding to the current microservice to call the current microservice within a preset call time.

In a specific embodiment of the present invention, the server may use the thread pool resources corresponding to the current microservice to call the current microservice within a preset call time. Specifically, if the server obtains the thread pool resource corresponding to the current microservice in the thread pool where the current microservice is located, the server can use the thread pool resource corresponding to the current microservice to call the current microservice within the preset call time; If the server does not obtain the thread pool resource corresponding to the current microservice in the thread pool where the current microservice is located, the server may end the call to the current microservice.

The microservice invocation method proposed by the embodiment of the present invention firstly receives the invocation request corresponding to the current microservice sent by the current consumer through the interceptor; wherein, the invocation request carries the service level of the current microservice; and then responds to the invocation request corresponding to the current microservice The call request obtains the thread pool resources corresponding to the current microservice in the thread pool where the current microservice is located; finally, use the thread pool resources corresponding to the current microservice to call the current microservice within the preset call time. That is to say, in the technical solution of the present invention, the thread pool resource corresponding to the current microservice can be obtained in the thread pool where the current microservice is located in response to the call request corresponding to the current microservice, so that the thread corresponding to the current microservice can be used The pool resource calls the current microservice within the preset call time. However, in the existing microservice calling methods, there is no isolation measure for highly concurrent microservice calls, and the current microservices are at risk of being dragged down. Therefore, compared with the prior art, the microservice calling method proposed by the embodiment of the present invention can not only improve the calling efficiency of the microservice, but also ensure the stability of the calling of the microservice; and, the technical solution of the embodiment of the present invention realizes Simple and convenient, easy to popularize, wider scope of application.

Embodiment two

FIG. 2 is a schematic flowchart of a method for invoking a microservice provided by Embodiment 2 of the present invention. As shown in Figure 2, the microservice invocation method may include the following steps:

Step 201: Receive the invocation request corresponding to the current microservice sent by the current consumer through the interceptor; wherein, the invocation request carries the service level of the current microservice.

In a specific embodiment of the present invention, the server may receive the invocation request corresponding to the current microservice sent by the current consumer through the interceptor; wherein, the invocation request carries the service level of the current microservice. Specifically, all invocation requests sent by each consumer end to the server will pass through the interceptor, and the interceptor will process each invocation request accordingly after receiving the invocation request sent by each consumer end. Specifically, the interceptor can judge whether the call request received is a legal call request. If the interceptor judges that the call request is a legal call request, the interceptor will report the call request to the server; If the invocation request is an illegal invocation request, the interceptor will not report the invocation request to the server.

In a specific embodiment of the present invention, the service level of the current microservice can be carried in the call request sent by each consumer to the server, and the service level can be a predetermined priority of the current microservice, indicating the importance of the current microservice ; The higher the service level of the current microservice, the more important the current microservice is; the lower the service level of the current microservice, the less important the current microservice is.

Step 202, in response to the calling request corresponding to the current microservice, obtain the thread pool resources corresponding to the current microservice from the thread pool where the current microservice is located.

In a specific embodiment of the present invention, the server may obtain the thread pool resource corresponding to the current microservice from the thread pool where the current microservice is located in response to the call request corresponding to the current microservice. Specifically, the server may first determine the thread pool where the current microservice is located according to the call request corresponding to the current microservice, and then obtain the thread pool resources corresponding to the current microservice from the thread pool where the current microservice is located. If the server obtains the thread pool resources corresponding to the current microservice in the thread pool where the current microservice is located, the server can use the thread pool resources corresponding to the current microservice to call the current microservice within the preset call time; if the server is in If the thread pool resource corresponding to the current microservice is not obtained from the thread pool where the current microservice is located, the server can end the call to the current microservice. That is to say, in a specific embodiment of the present invention, the server obtains the thread pool resources corresponding to the current microservice in the thread pool where the current microservice is located, instead of obtaining the thread pool resources corresponding to the current microservice in all thread pools , therefore, the calling efficiency of the microservice can be improved, and the stability of the calling of the microservice can also be guaranteed.

Preferably, in a specific embodiment of the present invention, the server can respond to the call request corresponding to the current microservice to determine whether the thread pool where the current microservice is located has reached saturation; if the thread pool where the current microservice is located has reached saturation, then The server can downgrade the service level of the current microservice; and obtain the thread pool resources corresponding to the current microservice in the thread pool where the current microservice is located according to the downgraded call request; if the thread pool where the current microservice is located is not saturated, Then the server can keep the service level corresponding to the current microservice; and obtain the thread pool resources corresponding to the current microservice in the thread pool where the current microservice is located according to the call request.

Step 203, using the thread pool resources corresponding to the current microservice to call the current microservice within a preset call time.

In a specific embodiment of the present invention, the server may use the thread pool resources corresponding to the current microservice to call the current microservice within a preset call time. Specifically, if the server obtains the thread pool resource corresponding to the current microservice in the thread pool where the current microservice is located, the server can use the thread pool resource corresponding to the current microservice to call the current microservice within the preset call time; If the server does not obtain the thread pool resources corresponding to the current microservice in the thread pool where the current microservice is located, the server may end the call to the current microservice.

Step 204: If the thread pool resource corresponding to the current microservice is used to successfully call the current microservice within the preset call time, a call success message is returned to the current consumer; if the thread pool resource corresponding to the current microservice is used within the preset call time If the call to the current microservice fails within the call time, a call failure message will be returned to the current consumer.

In a specific embodiment of the present invention, if the server uses the thread pool resource corresponding to the current microservice to successfully call the current microservice within the preset call time, the server can return a call success message to the current consumer; if the server uses the current If the thread pool resource corresponding to the microservice fails to call the current microservice within the preset call time, the server can return a call failure message to the current consumer.

The microservice invocation method proposed by the embodiment of the present invention firstly receives the invocation request corresponding to the current microservice sent by the current consumer through the interceptor; wherein, the invocation request carries the service level of the current microservice; and then responds to the invocation request corresponding to the current microservice The call request obtains the thread pool resources corresponding to the current microservice in the thread pool where the current microservice is located; finally, use the thread pool resources corresponding to the current microservice to call the current microservice within the preset call time. That is to say, in the technical solution of the present invention, the thread pool resource corresponding to the current microservice can be obtained in the thread pool where the current microservice is located in response to the call request corresponding to the current microservice, so that the thread corresponding to the current microservice can be used The pool resource calls the current microservice within the preset call time. However, in the existing microservice calling methods, there is no isolation measure for highly concurrent microservice calls, and the current microservices are at risk of being dragged down. Therefore, compared with the prior art, the microservice calling method proposed by the embodiment of the present invention can not only improve the calling efficiency of the microservice, but also ensure the stability of the calling of the microservice; and, the technical solution of the embodiment of the present invention realizes Simple and convenient, easy to popularize, wider scope of application.

Embodiment three

FIG. 3 is a schematic flowchart of a method for invoking a microservice provided by Embodiment 3 of the present invention. As shown in Figure 3, the microservice invocation method may include the following steps:

Step 301: Receive the invocation request corresponding to the current microservice sent by the current consumer through the interceptor; wherein, the invocation request carries the service level of the current microservice.

In a specific embodiment of the present invention, the server may receive the invocation request corresponding to the current microservice sent by the current consumer through the interceptor; wherein, the invocation request carries the service level of the current microservice. Specifically, all invocation requests sent by each consumer end to the server will pass through the interceptor, and the interceptor will process each invocation request accordingly after receiving the invocation request sent by each consumer end. Specifically, the interceptor can judge whether the call request received is a legal call request. If the interceptor judges that the call request is a legal call request, the interceptor will report the call request to the server; If the invocation request is an illegal invocation request, the interceptor will not report the invocation request to the server.

In a specific embodiment of the present invention, the service level of the current microservice can be carried in the call request sent by each consumer to the server, and the service level can be a predetermined priority of the current microservice, indicating the importance of the current microservice ; The higher the service level of the current microservice, the more important the current microservice is; the lower the service level of the current microservice, the less important the current microservice is.

Step 302 , in response to the call request corresponding to the current microservice, obtain the thread pool resource corresponding to the current microservice from the thread pool where the current microservice is located.

In a specific embodiment of the present invention, the server may obtain the thread pool resource corresponding to the current microservice from the thread pool where the current microservice is located in response to the call request corresponding to the current microservice. Specifically, the server may first determine the thread pool where the current microservice is located according to the call request corresponding to the current microservice, and then obtain the thread pool resources corresponding to the current microservice from the thread pool where the current microservice is located. If the server obtains the thread pool resources corresponding to the current microservice in the thread pool where the current microservice is located, the server can use the thread pool resources corresponding to the current microservice to call the current microservice within the preset call time; if the server is in If the thread pool resource corresponding to the current microservice is not obtained from the thread pool where the current microservice is located, the server can end the call to the current microservice. That is to say, in a specific embodiment of the present invention, the server obtains the thread pool resources corresponding to the current microservice in the thread pool where the current microservice is located, instead of obtaining the thread pool resources corresponding to the current microservice in all thread pools , therefore, the calling efficiency of the microservice can be improved, and the stability of the calling of the microservice can also be guaranteed.

Preferably, in a specific embodiment of the present invention, the server can respond to the call request corresponding to the current microservice to determine whether the thread pool where the current microservice is located has reached saturation; if the thread pool where the current microservice is located has reached saturation, then The server can downgrade the service level of the current microservice; and obtain the thread pool resources corresponding to the current microservice in the thread pool where the current microservice is located according to the downgraded call request; if the thread pool where the current microservice is located is not saturated, Then the server can keep the service level corresponding to the current microservice; and obtain the thread pool resources corresponding to the current microservice in the thread pool where the current microservice is located according to the call request.

Step 303, using the thread pool resources corresponding to the current microservice to call the current microservice within a preset call time.

In a specific embodiment of the present invention, the server may use the thread pool resources corresponding to the current microservice to call the current microservice within a preset call time. Specifically, if the server obtains the thread pool resource corresponding to the current microservice in the thread pool where the current microservice is located, the server can use the thread pool resource corresponding to the current microservice to call the current microservice within the preset call time; If the server does not obtain the thread pool resource corresponding to the current microservice in the thread pool where the current microservice is located, the server may end the call to the current microservice.

Step 304: If the thread pool resource corresponding to the current microservice is used to call the current microservice successfully within the preset call time, return a call success message to the current consumer; if the thread pool resource corresponding to the current microservice is used within the preset call time If the call to the current microservice fails within the call time, a call failure message will be returned to the current consumer.

In a specific embodiment of the present invention, if the server uses the thread pool resource corresponding to the current microservice to successfully call the current microservice within the preset call time, the server can return a call success message to the current consumer; if the server uses the current If the thread pool resource corresponding to the microservice fails to call the current microservice within the preset call time, the server can return a call failure message to the current consumer.

Step 305, obtain the running state of the current microservice through the fuse; wherein, the running state includes: success state, failure state, rejection state and timeout state.

In a specific embodiment of the present invention, the server can obtain the running status of the current microservice through the fuse; wherein, the running status includes: success status, failure status, rejection status and timeout status. Specifically, the server can obtain the current running status of the microservice through the fuse according to a preset period.

Step 306: Perform corresponding processing on the current microservice according to the running state of the current microservice.

In a specific embodiment of the present invention, the server may perform corresponding processing on the current microservice according to the running state of the current microservice. Specifically, if the running status of the current microservice is successful, the server can keep calling the current microservice; if the running status of the current microservice is failed, rejected or timed out, the server can end the call call.

The microservice invocation method proposed by the embodiment of the present invention firstly receives the invocation request corresponding to the current microservice sent by the current consumer through the interceptor; wherein, the invocation request carries the service level of the current microservice; and then responds to the invocation request corresponding to the current microservice The call request obtains the thread pool resources corresponding to the current microservice in the thread pool where the current microservice is located; finally, use the thread pool resources corresponding to the current microservice to call the current microservice within the preset call time. That is to say, in the technical solution of the present invention, the thread pool resource corresponding to the current microservice can be obtained in the thread pool where the current microservice is located in response to the call request corresponding to the current microservice, so that the thread corresponding to the current microservice can be used The pool resource calls the current microservice within the preset call time. However, in the existing microservice calling methods, there is no isolation measure for highly concurrent microservice calls, and the current microservices are at risk of being dragged down. Therefore, compared with the prior art, the microservice calling method proposed by the embodiment of the present invention can not only improve the calling efficiency of the microservice, but also ensure the stability of the calling of the microservice; and, the technical solution of the embodiment of the present invention realizes Simple and convenient, easy to popularize, wider scope of application.

Embodiment four

FIG. 4 is a schematic diagram of a first structure of a microservice invocation device provided in Embodiment 4 of the present invention. As shown in FIG. 4 , the microservice calling device described in the embodiment of the present invention may include: a receiving module 401, an obtaining module 402, and a calling module 403; wherein,

The receiving module 401 is configured to receive the invocation request corresponding to the current microservice sent by the current consumer through an interceptor; wherein, the invocation request carries the service level of the current microservice;

The acquisition module 402 is configured to acquire the thread pool resource corresponding to the current microservice in the thread pool where the current microservice is located in response to the call request corresponding to the current microservice;

The calling module 403 is configured to use the thread pool resources corresponding to the current microservice to call the current microservice within a preset calling time.

Further, the invoking module 403 is further configured to return a message to the current consumer if the invocation of the current microservice is successful within the preset invocation time using the thread pool resources corresponding to the current microservice. A call success message; if the thread pool resource corresponding to the current microservice fails to call the current microservice within the preset call time, return a call failure message to the current consumer.

FIG. 5 is a schematic diagram of a second structure of a microservice calling device provided in Embodiment 4 of the present invention. As shown in FIG. 5, the acquisition module 402 includes: a judgment submodule 4021 and an acquisition submodule 4022; wherein,

The judging sub-module 4021 is configured to judge whether the thread pool where the current microservice is located has reached saturation in response to the call request corresponding to the current microservice;

The acquisition sub-module 4022 is configured to downgrade the service level of the current microservice if the thread pool where the current microservice is located has reached saturation; Obtain the thread pool resources corresponding to the current microservice from the thread pool of the current microservice; if the thread pool where the current microservice is located is not saturated, keep the service level corresponding to the current microservice; and according to the call request Obtain the thread pool resources corresponding to the current microservice in the thread pool where the current microservice is located.

Further, the calling module 403 is also used to obtain the running status of the current micro-service through a fuse; wherein, the running status includes: success status, failure status, rejection status and timeout status; according to the current micro-service The running status of the service performs corresponding processing on the current microservice.

The above-mentioned microservice calling device can execute the method provided by any embodiment of the present invention, and has corresponding functional modules and beneficial effects for executing the method. For technical details not exhaustively described in this embodiment, refer to the method for invoking a microservice provided in any embodiment of the present invention.

Embodiment five

FIG. 6 is a schematic structural diagram of a server provided in Embodiment 5 of the present invention. Figure 6 shows a block diagram of an exemplary server suitable for use in implementing embodiments of the present invention. The server 12 shown in FIG. 6 is only an example, and should not limit the functions and scope of use of this embodiment of the present invention.

As shown in FIG. 6, server 12 takes the form of a general-purpose computing device. Components of server 12 may include, but are not limited to: one or more processors or processing units 16, system memory 28, bus 18 connecting various system components including system memory 28 and processing unit 16.

Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus structures. These architectures include, by way of example, but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect ( PCI) bus.

Server 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by server 12 and include both volatile and nonvolatile media, removable and non-removable media.

System memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and/or cache memory 32 . The server 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read and write to non-removable, non-volatile magnetic media (not shown in FIG. 6, commonly referred to as a "hard drive"). Although not shown in FIG. 6, a disk drive for reading and writing to removable nonvolatile disks (e.g., "floppy disks") may be provided, as well as for removable nonvolatile optical disks (e.g., CD-ROM, DVD-ROM). or other optical media) CD-ROM drive. In these cases, each drive may be connected to bus 18 via one or more data media interfaces. Memory 28 may include at least one program product having a set (eg, at least one) of program modules configured to perform the functions of various embodiments of the present invention.

A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory 28, such program modules 42 including but not limited to an operating system, one or more application programs, other program modules, and program data , each or some combination of these examples may include implementations of network environments. Program modules 42 generally perform the functions and/or methodologies of the described embodiments of the invention.

Server 12 may also communicate with one or more external devices 14 (e.g., keyboards, pointing devices, displays 24, etc.), and may also communicate with one or more devices that enable users to interact with Server 12 is capable of communicating with any device (eg, network card, modem, etc.) that communicates with one or more other computing devices. Such communication may occur through input/output (I/O) interface 22 . Moreover, the server 12 can also communicate with one or more networks (eg, a local area network (LAN), a wide area network (WAN) and/or a public network, such as the Internet) through the network adapter 20 . As shown, network adapter 20 communicates with other modules of server 12 via bus 18 . It should be appreciated that although not shown, other hardware and/or software modules may be used in conjunction with server 12, 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.

The processing unit 16 executes various functional applications and data processing by running the programs stored in the system memory 28 , such as realizing the microservice calling method provided by the embodiment of the present invention.

Embodiment six

Embodiment 6 of the present invention provides a computer storage medium.

The computer-readable storage medium in the embodiments of the present invention may use any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (non-exhaustive list) of computer readable storage media include: electrical connections with one or more leads, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), Erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a data signal carrying computer 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 computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. .

Program code embodied on a computer 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.

Computer program code for carrying out the operations of the present invention may be written in one or more programming languages, or combinations thereof, including object-oriented programming languages—such as Java, Smalltalk, C++, and conventional Procedural Programming Language - such as "C" or a similar programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In cases involving a remote computer, the remote computer can be connected to the user computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (such as through an Internet service provider). Internet connection).

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods or computer program products. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

Claims (10)

1. A microservice calling method, characterized in that the method comprises: Receive the invocation request corresponding to the current microservice sent by the current consumer through the interceptor; wherein, the invocation request carries the service level of the current microservice; In response to the call request corresponding to the current microservice, obtain the thread pool resource corresponding to the current microservice in the thread pool where the current microservice is located; Using the thread pool resources corresponding to the current microservice to call the current microservice within a preset call time. 2. The method according to claim 1, characterized in that the method further comprises: If the thread pool resource corresponding to the current microservice is used to successfully call the current microservice within the preset call time, return a call success message to the current consumer; If the thread pool resource corresponding to the current microservice fails to call the current microservice within the preset call time, return a call failure message to the current consumer. 3. The method according to claim 1, wherein in response to the call request corresponding to the current microservice, the thread pool resource corresponding to the current microservice is acquired in the thread pool where the current microservice is located ,include: In response to the call request corresponding to the current microservice, determine whether the thread pool where the current microservice is located has reached saturation; If the thread pool where the current microservice is located has reached saturation, then downgrade the service level of the current microservice; and obtain the current microservice in the thread pool where the current microservice is located according to the degraded call request The thread pool resource corresponding to the service; If the thread pool where the current microservice is located is not saturated, then maintain the service level corresponding to the current microservice; and obtain the current microservice in the thread pool where the current microservice is located according to the call request The thread pool resource corresponding to the service. 4. The method according to claim 1, wherein the method further comprises: Obtain the running status of the current microservice through a fuse; wherein, the running status includes: success status, failure status, rejection status and timeout status; Perform corresponding processing on the current microservice according to the running state of the current microservice. 5. A microservice invocation device, characterized in that the device comprises: a receiving module, an acquisition module and a calling module; wherein, The receiving module is configured to receive the invocation request corresponding to the current microservice sent by the current consumer through the interceptor; wherein, the invocation request carries the service level of the current microservice; The acquiring module is configured to acquire the thread pool resource corresponding to the current microservice in the thread pool where the current microservice is located in response to the call request corresponding to the current microservice; The calling module is configured to use the thread pool resource corresponding to the current microservice to call the current microservice within a preset calling time. 6. The device according to claim 5, wherein the calling module is further configured to call the current microservice within the preset calling time if the thread pool resource corresponding to the current microservice is used If successful, a call success message will be returned to the current consumer; if the call to the current microservice fails within the preset call time using the thread pool resources corresponding to the current microservice, then a call to the current consumer The terminal returns a call failure message. 7. The device according to claim 5, wherein the acquiring module comprises: a judging submodule and an acquiring submodule; wherein, The judging submodule is used to judge whether the thread pool where the current microservice is located has reached saturation in response to the call request corresponding to the current microservice; The obtaining sub-module is used to downgrade the service level of the current microservice if the thread pool where the current microservice is located has reached saturation; Obtain the thread pool resources corresponding to the current microservice from the thread pool; if the thread pool where the current microservice is located is not saturated, then keep the service level corresponding to the current microservice; A thread pool resource corresponding to the current microservice is obtained from the thread pool where the current microservice is located. 8. The device according to claim 5, wherein the calling module is further configured to obtain the running state of the current microservice through a fuse; wherein, the running state includes: success state, failure state, Rejection status and timeout status; perform corresponding processing on the current microservice according to the running status of the current microservice. 9. A server, characterized in that, comprising: one or more processors; memory for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the microservice calling method according to any one of claims 1-4. 10. A storage medium, on which a computer program is stored, wherein when the program is executed by a processor, the microservice calling method according to any one of claims 1 to 4 is implemented.