Request forwarding method, device, equipment and readable storage medium
By setting up a proxy server in the kubernetes cluster, forwarding the requests from the local server to the microservices within the cluster, the problems of low request forwarding efficiency and large resource utilization in the existing technology are solved, and efficient request forwarding and cost reduction are achieved.
Patent Information
- Application Number
- CN202111277174.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-10-29
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2041-10-29
AI Technical Summary
The prior art cannot effectively forward requests directly from local servers to microservices within the kubernetes cluster, resulting in large system resource usage, low request forwarding efficiency and high cost.
Set up a proxy server in the kubernetes cluster to obtain the forwarding direction when the request is to be forwarded is detected. If it is the local server to the cluster direction, the request will be forwarded to the proxy server, and the proxy server will parse and forward it to the corresponding microservice to avoid local The environment starts all microservices and changes the cluster network.
It realizes request forwarding from the local server to the kubernetes cluster, saves system resources, simplifies the request forwarding process, reduces costs, and improves efficiency.
Smart Images

Figure CN113923204B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of communication technology, and in particular to a request forwarding method, device, equipment and computer-readable storage medium. Background Art
[0002] Internet enterprise information systems contain multiple microservice programs, such as spring cloud framework microservices. The execution of each request task requires multiple microservice programs to work together to provide support. The multiple microservices required for task execution may be distributed on local servers and kubernetes clusters. However, due to the kubernetes cluster network, it is impossible to directly link the local server microservice to the microservice in the kubernetes cluster for request forwarding.
[0003] Since it is impossible to directly link the microservices in the kubernetes cluster from the local server microservices to forward requests, the existing method is for developers to start all related microservice programs in the local environment or modify the kubernetes cluster network. However, both of the above methods have certain disadvantages. First, starting all related microservice programs in the local environment requires time to wait during the startup process, occupies a large amount of local system resources, and has low request forwarding efficiency. Secondly, by modifying the kubernetes cluster network, the modification cost is large, the process is complicated, and the cost is high.
[0004] In summary, how to effectively solve the existing method of forwarding requests from local server microservices to kubernetes cluster microservices, large system resource usage, low request forwarding efficiency, high cost and other problems, is an urgent problem that technicians in this field need to solve. Summary of the invention
[0005] The purpose of the present invention is to provide a request forwarding method, which greatly saves system resources, simplifies the request forwarding process, and reduces costs; another purpose of the present invention is to provide a request forwarding device, equipment and computer-readable storage medium.
[0006] In order to solve the above technical problems, the present invention provides the following technical solutions:
[0007] A request forwarding method, comprising:
[0008] When a request to be forwarded is detected, a forwarding direction corresponding to the request to be forwarded is obtained;
[0009] Determine whether the forwarding direction is from the local server to the kubernetes cluster;
[0010] If yes, forward the request to be forwarded to the proxy server in the kubernetes cluster;
[0011] The proxy server is used to parse the request to be forwarded to obtain a first microservice, and the request to be forwarded is forwarded to the first microservice.
[0012] In a specific implementation of the present invention, forwarding the request to be forwarded to a proxy server in the kubernetes cluster includes:
[0013] The request to be forwarded is forwarded to the proxy server via a preset http proxy server port.
[0014] In a specific implementation of the present invention, the proxy server is used to parse the request to be forwarded to obtain a first microservice, including:
[0015] Using the proxy server to resolve the request to be forwarded according to a preset domain name resolution rule to obtain a first microservice name;
[0016] The first microservice is searched and obtained according to the first microservice name.
[0017] In a specific implementation of the present invention, when it is determined that the forwarding direction is not from the local server to the kubernetes cluster, it also includes:
[0018] Determine whether the forwarding direction is from the kubernetes cluster to the local server;
[0019] If yes, parse the request header of the request to be forwarded to obtain the second microservice name;
[0020] Find the intranet IP address corresponding to the second microservice name;
[0021] The request to be forwarded is forwarded to the intranet IP address, so as to forward the request to be forwarded to the second microservice in the local server.
[0022] A request forwarding device, comprising:
[0023] A forwarding direction acquisition module, used for acquiring a forwarding direction corresponding to a request to be forwarded when a request to be forwarded is detected;
[0024] The first judgment module is used to judge whether the forwarding direction is from the local server to the kubernetes cluster;
[0025] A first request forwarding module, configured to forward the request to be forwarded to a proxy server in the Kubernetes cluster when it is determined that the forwarding direction is from a local server to a Kubernetes cluster;
[0026] The second request forwarding module is used to use the proxy server to parse the request to be forwarded, obtain the first microservice, and forward the request to be forwarded to the first microservice.
[0027] In a specific implementation of the present invention, the first request forwarding module is specifically a module that forwards the request to be forwarded to the proxy server through a preset http proxy server port.
[0028] In a specific implementation of the present invention, the second request forwarding module includes:
[0029] A request resolution submodule, configured to use the proxy server to resolve the request to be forwarded according to a preset domain name resolution rule to obtain a first microservice name;
[0030] The microservice search submodule is used to search for the first microservice according to the name of the first microservice.
[0031] In a specific embodiment of the present invention, it also includes:
[0032] A second judgment module is used to judge whether the forwarding direction is from the Kubernetes cluster to the local server when it is determined that the forwarding direction is not from the local server to the Kubernetes cluster;
[0033] A request header parsing module, configured to parse the request header of the request to be forwarded to obtain a second microservice name when it is determined that the forwarding direction is from the kubernetes cluster to the local server;
[0034] An address search module, used to search for the intranet IP address corresponding to the second microservice name;
[0035] The third request forwarding module is used to forward the request to be forwarded to the intranet IP address, so as to forward the request to be forwarded to the second microservice in the local server.
[0036] A request forwarding device, comprising:
[0037] Memory for storing computer programs;
[0038] A processor is used to implement the steps of the request forwarding method as described above when executing the computer program.
[0039] A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the request forwarding method described above are implemented.
[0040] The request forwarding method provided by the present invention obtains the forwarding direction corresponding to the request to be forwarded when a request to be forwarded is monitored; determines whether the forwarding direction is from the local server to the Kubernetes cluster; if so, forwards the request to be forwarded to the proxy server in the Kubernetes cluster; uses the proxy server to parse the request to be forwarded to obtain the first microservice, and forwards the request to be forwarded to the first microservice.
[0041] It can be seen from the above technical solution that by pre-setting a proxy server in the kubernetes cluster, when it is determined that the request forwarding direction is from the local server to the kubernetes cluster, the request to be forwarded is first forwarded to the proxy server, and then the proxy server is used to forward the request to be forwarded to the corresponding microservice in the kubernetes cluster. In this way, request forwarding from the microservice in the local server to the microservice in the kubernetes cluster is realized, and all related microservices do not need to be started in the local environment, which greatly saves system resources, does not need to change the kubernetes cluster network, simplifies the request forwarding process, and reduces costs.
[0042] Correspondingly, the present invention also provides a request forwarding device, equipment and computer-readable storage medium corresponding to the above-mentioned request forwarding method, which have the above-mentioned technical effects and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0043] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0044] Figure 1 A flowchart of an implementation of a request forwarding method in an embodiment of the present invention;
[0045] Figure 2 Another implementation flow chart of the request forwarding method in an embodiment of the present invention;
[0046] Figure 3 is a structural block diagram of a request forwarding device in an embodiment of the present invention;
[0047] Figure 4 A structural block diagram of a request forwarding device in an embodiment of the present invention;
[0048] Figure 5 A schematic diagram of the specific structure of a request forwarding device provided in this embodiment. DETAILED DESCRIPTION
[0049] In order to enable those skilled in the art to better understand the scheme of the present invention, the present invention is further described in detail below in conjunction with the accompanying drawings and specific implementation methods. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.
[0050] See also Figure 1 , Figure 1 This is a flowchart of an implementation of a request forwarding method in an embodiment of the present invention. The method may include the following steps:
[0051] S101: When a request to be forwarded is detected, a forwarding direction corresponding to the request to be forwarded is obtained.
[0052] When request forwarding between microservices is required, a request to be forwarded is generated, which contains the forwarding direction of the request, that is, from which microservice in the local server or kubernetes cluster the request to be forwarded is forwarded to which microservice in the local server or kubernetes cluster. The request forwarding center monitors the request, and when a request to be forwarded is detected, the forwarding direction corresponding to the request to be forwarded is obtained.
[0053] S102: Determine whether the forwarding direction is from the local server to the kubernetes cluster. If not, execute step S103; if yes, execute step S104.
[0054] After obtaining the forwarding direction corresponding to the request to be forwarded, determine whether the forwarding direction is from the local server to the kubernetes cluster. If not, it means that there is no situation where it is impossible to directly connect to the microservice in the kubernetes cluster, and execute step S103. If so, it means that the current situation is that it is impossible to directly connect to the microservice in the kubernetes cluster, and execute step S104.
[0055] S103: forwarding the request according to a preset request forwarding rule corresponding to the forwarding direction.
[0056] The request forwarding rules whose forwarding direction is not from the local server to the kubernetes cluster are pre-set. For example, when the forwarding direction is from the microservice in the local server to the microservice in the local server, the request can be directly forwarded; when the forwarding direction is from the microservice in the kubernetes cluster to the microservice in the kubernetes cluster, the request can also be directly forwarded; when the forwarding direction is from the microservice in the kubernetes cluster to the microservice in the local server, the request can also be directly forwarded according to the pre-set request forwarding rules.
[0057] When it is determined that the forwarding direction is not from the local server to the kubernetes cluster, it means that there is no situation where it is impossible to directly connect to the microservice in the kubernetes cluster, and the request is forwarded according to the preset request forwarding rules corresponding to the forwarding direction. For example, the microservice to be forwarded can be identified according to the microservice identification information, so that the corresponding microservice can be identified by the identification information, and then the forwarding operation of the forwarded request can be realized.
[0058] S104: Forward the request to be forwarded to the proxy server in the kubernetes cluster.
[0059] A proxy server is set up in the kubernetes cluster in advance, and local requests can be connected to the proxy server. When the forwarding direction is determined to be from the local server to the kubernetes cluster, it means that the current situation is that it is impossible to directly connect to the microservice in the kubernetes cluster, and the request to be forwarded is forwarded to the proxy server in the kubernetes cluster.
[0060] S105: Utilize the proxy server to parse the request to be forwarded, obtain the first microservice, and forward the request to be forwarded to the first microservice.
[0061] After forwarding the request to be forwarded to the proxy server in the kubernetes cluster, the proxy server is used to parse the request to be forwarded to obtain the first microservice. Since the proxy server and the first microservice belong to the same internal network, the proxy server can forward the request to be forwarded to the first microservice, thereby realizing the forwarding of the request to be forwarded initiated by the microservice in the local server to the microservice in the kubernetes cluster. The present invention only needs to set up a proxy server in the kubernetes cluster, and does not need to start all related microservices in the local environment, which greatly saves system resources, does not need to change the kubernetes cluster network, simplifies the request forwarding process, and avoids excessive microservice joint debugging costs.
[0062] It should be noted that the first in the first microservice is only an identifier of the microservice to be forwarded to.
[0063] It can be seen from the above technical solution that by pre-setting a proxy server in the kubernetes cluster, when it is determined that the request forwarding direction is from the local server to the kubernetes cluster, the request to be forwarded is first forwarded to the proxy server, and then the proxy server is used to forward the request to be forwarded to the corresponding microservice in the kubernetes cluster. In this way, request forwarding from the microservice in the local server to the microservice in the kubernetes cluster is realized, and all related microservices do not need to be started in the local environment, which greatly saves system resources, does not need to change the kubernetes cluster network, simplifies the request forwarding process, and reduces costs.
[0064] It should be noted that, based on the above embodiment, the embodiment of the present invention also provides corresponding improved solutions. In the subsequent embodiments, the same steps or corresponding steps as those in the above embodiment can be referenced to each other, and the corresponding beneficial effects can also be referenced to each other, which will not be repeated one by one in the following improved embodiments.
[0065] See also Figure 2 , Figure 2 Another implementation flow chart of the request forwarding method in an embodiment of the present invention, the method may include the following steps:
[0066] S201: When a request to be forwarded is detected, a forwarding direction corresponding to the request to be forwarded is obtained.
[0067] S202: Determine whether the forwarding direction is from the local server to the kubernetes cluster. If so, execute step S203; if not, execute step S206.
[0068] S203: forwarding the request to be forwarded to the proxy server via a preset http proxy server port.
[0069] The http proxy server port is pre-set in the proxy server, and the http proxy server port is exposed to the forwarding request on the local server. When the forwarding direction is determined to be from the local server to the kubernetes cluster, the forwarding request is forwarded to the proxy server through the preset http proxy server port. By setting the http proxy server port exposed to the forwarding request, it is convenient to forward the forwarding request of the local server microservice to the proxy server in the kubernetes cluster.
[0070] S204: Using a proxy server to resolve the request to be forwarded according to a preset domain name resolution rule to obtain a first microservice name.
[0071] The kubernetes cluster is pre-set with a domain name resolution rule, and the proxy server can resolve the request to be forwarded according to the domain name resolution rule to obtain the name of the microservice to which the request to be forwarded is to be forwarded. After forwarding the request to be forwarded to the proxy server through the preset http proxy server port, the proxy server is used to resolve the request to be forwarded according to the preset domain name resolution rule to obtain the first microservice name.
[0072] S205: Find the first microservice according to the name of the first microservice, and forward the request to be forwarded to the first microservice.
[0073] After parsing and obtaining the first microservice name, the first microservice corresponding to the first microservice name is searched, and the request to be forwarded is forwarded to the first microservice. The corresponding relationship between the microservice name and the microservice is fully utilized, the accuracy of request forwarding is greatly improved, and the efficiency of request forwarding is improved.
[0074] S206: Determine whether the forwarding direction is from the kubernetes cluster to the local server. If not, execute step S207; if yes, execute step S208.
[0075] When it is determined that the forwarding direction is not from the local server to the Kubernetes cluster, it is further determined whether the forwarding direction is from the Kubernetes cluster to the local server. If not, it means that the forwarding direction is from the microservice in the local server to the microservice in the local server, or from the microservice in the Kubernetes cluster to the microservice in the Kubernetes cluster, and step S207 is executed. If yes, step S208 is executed.
[0076] S207: forwarding the request according to a preset request forwarding rule corresponding to the forwarding direction.
[0077] When it is determined that the forwarding direction is neither from the local server to the Kubernetes cluster nor from the Kubernetes cluster to the local server, it means that the forwarding direction is from the microservice in the local server to the microservice in the local server, or from the microservice in the Kubernetes cluster to the microservice in the Kubernetes cluster. Request forwarding rules between microservices in the local server and between microservices in the Kubernetes cluster are pre-set, and requests are forwarded according to the preset request forwarding rules corresponding to the forwarding direction.
[0078] S208: Parse the request header of the request to be forwarded to obtain the second microservice name.
[0079] The request header of the request to be forwarded includes the name of the second microservice to which the request to be forwarded needs to be forwarded. When the forwarding direction is determined to be from the kubernetes cluster to the local server, the request header of the request to be forwarded is parsed to obtain the second microservice name.
[0080] S209: Find the intranet IP address corresponding to the second microservice name.
[0081] The correspondence between each microservice name and each intranet IP address is preset. After parsing and obtaining the second microservice name of the microservice to which the request to be forwarded needs to be forwarded, the intranet IP address corresponding to the second microservice name is searched.
[0082] It should be noted that the first and second in the first microservice name and the second microservice name are only used to distinguish the microservices to which the forwarding request needs to be forwarded when the forwarding direction is from the local server to the Kubernetes cluster and the forwarding direction is from the Kubernetes cluster to the local server, and there is no distinction between size or order.
[0083] S210: Forward the request to be forwarded to the intranet IP address, so as to forward the request to be forwarded to the second microservice in the local server.
[0084] After finding the intranet IP address corresponding to the second microservice name, the request to be forwarded is forwarded to the intranet IP address, thereby forwarding the request to be forwarded to the second microservice in the local server.
[0085] This embodiment is different from the embodiment 1 corresponding to the technical solution claimed for protection by the independent claim 1, and further adds the technical solution claimed for protection by the dependent claims 2 to 4. Of course, according to different actual conditions and requirements, the technical solutions claimed for protection by the dependent claims can be flexibly combined without affecting the integrity of the solutions, so as to better meet the requirements of different usage scenarios. This embodiment only provides one of the solutions with the most solutions and the best effects. Due to the complexity of the situation, it is impossible to list all possible solutions one by one. Those skilled in the art should be able to realize that there can be many examples based on the basic method principles provided by this application in combination with actual conditions, and they should all be within the scope of protection of this application without sufficient creative work.
[0086] Corresponding to the above method embodiment, the present invention further provides a request forwarding device. The request forwarding device described below and the request forwarding method described above can refer to each other.
[0087] See also Figure 3 , Figure 3 This is a structural block diagram of a request forwarding device in an embodiment of the present invention, and the device may include:
[0088] A forwarding direction acquisition module 31 is used to acquire a forwarding direction corresponding to a request to be forwarded when a request to be forwarded is detected;
[0089] The first determination module 32 is used to determine whether the forwarding direction is from the local server to the kubernetes cluster;
[0090] A first request forwarding module 33 is used to forward the request to be forwarded to the proxy server in the Kubernetes cluster when it is determined that the forwarding direction is from the local server to the Kubernetes cluster;
[0091] The second request forwarding module 34 is used to use the proxy server to parse the request to be forwarded, obtain the first microservice, and forward the request to be forwarded to the first microservice.
[0092] It can be seen from the above technical solution that by pre-setting a proxy server in the kubernetes cluster, when it is determined that the request forwarding direction is from the local server to the kubernetes cluster, the request to be forwarded is first forwarded to the proxy server, and then the proxy server is used to forward the request to be forwarded to the corresponding microservice in the kubernetes cluster. In this way, request forwarding from the microservice in the local server to the microservice in the kubernetes cluster is realized, and all related microservices do not need to be started in the local environment, which greatly saves system resources, does not need to change the kubernetes cluster network, simplifies the request forwarding process, and reduces costs.
[0093] In a specific implementation of the present invention, the first request forwarding module 33 is specifically a module that forwards the request to be forwarded to the proxy server through a preset http proxy server port.
[0094] In a specific implementation of the present invention, the second request forwarding module 34 includes:
[0095] A request resolution submodule, used to use a proxy server to resolve the forwarding request according to a preset domain name resolution rule to obtain the first microservice name;
[0096] The microservice search submodule is used to search for the first microservice according to the name of the first microservice.
[0097] In a specific embodiment of the present invention, it also includes:
[0098] The second judgment module is used to judge whether the forwarding direction is from the kubernetes cluster to the local server when it is determined that the forwarding direction is not from the local server to the kubernetes cluster;
[0099] A request header parsing module is used to parse the request header of the forwarded request to obtain the name of the second microservice when the forwarding direction is determined to be from the kubernetes cluster to the local server;
[0100] An address search module is used to search for the intranet IP address corresponding to the second microservice name;
[0101] The third request forwarding module is used to forward the request to be forwarded to the intranet IP address, so as to forward the request to be forwarded to the second microservice in the local server.
[0102] Corresponding to the above method embodiment, see Figure 4 , Figure 4 This is a schematic diagram of a request forwarding device provided by the present invention, and the device may include:
[0103] A memory 332, for storing computer programs;
[0104] The processor 322 is configured to implement the steps of the request forwarding method of the above method embodiment when executing a computer program.
[0105] For details, please refer to Figure 5 , Figure 5 A specific structural diagram of a request forwarding device provided for this embodiment, the request forwarding device may have relatively large differences due to different configurations or performances, and may include a processor (central processing units, CPU) 322 (for example, one or more processors) and a memory 332, and the memory 332 stores one or more computer applications 342 or data 344. Among them, the memory 332 can be a temporary storage or a permanent storage. The program stored in the memory 332 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations in the data processing device. Furthermore, the processor 322 can be configured to communicate with the memory 332 to execute a series of instruction operations in the memory 332 on the request forwarding device 301.
[0106] The request forwarding device 301 may further include one or more power supplies 326 , one or more wired or wireless network interfaces 350 , one or more input and output interfaces 358 , and / or one or more operating systems 341 .
[0107] The steps in the request forwarding method described above can be implemented by the structure of the request forwarding device.
[0108] Corresponding to the above method embodiment, the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the following steps can be implemented:
[0109] When a request to be forwarded is detected, the forwarding direction corresponding to the request to be forwarded is obtained; it is determined whether the forwarding direction is from the local server to the kubernetes cluster; if so, the request to be forwarded is forwarded to the proxy server in the kubernetes cluster; the proxy server is used to parse the request to be forwarded, obtain the first microservice, and forward the request to be forwarded to the first microservice.
[0110] The computer-readable storage medium may include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.
[0111] For an introduction to the computer-readable storage medium provided by the present invention, please refer to the above method embodiment, and the present invention will not be elaborated here.
[0112] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the devices, equipment and computer-readable storage media disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the method part description.
[0113] The principles and implementation methods of the present invention are described in this article using specific examples. The description of the above embodiments is only used to help understand the technical solution and core ideas of the present invention. It should be pointed out that for ordinary technicians in this technical field, the present invention can also be improved and modified without departing from the principles of the present invention, and these improvements and modifications also fall within the scope of protection of the claims of the present invention.
Claims
1. A request forwarding method, characterized in that: include: When a request to be forwarded is detected, a forwarding direction corresponding to the request to be forwarded is obtained; Determine whether the forwarding direction is from the local server to the kubernetes cluster; If yes, forward the request to be forwarded to the proxy server in the kubernetes cluster; Using the proxy server to resolve the request to be forwarded according to a preset domain name resolution rule to obtain a first microservice name; Finding the first microservice according to the name of the first microservice, and forwarding the request to be forwarded to the first microservice; wherein the proxy server and the first microservice belong to the same internal network; If not, determine whether the forwarding direction is from the kubernetes cluster to the local server; If yes, parse the request header of the request to be forwarded to obtain the second microservice name; Find the intranet IP address corresponding to the second microservice name; The request to be forwarded is forwarded to the intranet IP address, so as to forward the request to be forwarded to the second microservice in the local server.
2. The request forwarding method according to claim 1, characterized in that: Forwarding the request to be forwarded to a proxy server in the kubernetes cluster, including: The request to be forwarded is forwarded to the proxy server via a preset http proxy server port.
3. A request forwarding device, characterized in that: include: A forwarding direction acquisition module, used for acquiring a forwarding direction corresponding to a request to be forwarded when a request to be forwarded is detected; The first judgment module is used to judge whether the forwarding direction is from the local server to the kubernetes cluster; A first request forwarding module, configured to forward the request to be forwarded to a proxy server in the Kubernetes cluster when it is determined that the forwarding direction is from a local server to a Kubernetes cluster; A second request forwarding module, wherein the second request forwarding module comprises: A request resolution submodule, configured to use the proxy server to resolve the request to be forwarded according to a preset domain name resolution rule to obtain a first microservice name; A microservice search submodule, configured to search for a first microservice according to the name of the first microservice; wherein the proxy server and the first microservice belong to the same internal network; A second judgment module is used to judge whether the forwarding direction is from the Kubernetes cluster to the local server when it is determined that the forwarding direction is not from the local server to the Kubernetes cluster; A request header parsing module, configured to parse the request header of the request to be forwarded to obtain a second microservice name when it is determined that the forwarding direction is from the kubernetes cluster to the local server; An address search module, used to search for the intranet IP address corresponding to the second microservice name; The third request forwarding module is used to forward the request to be forwarded to the intranet IP address, so as to forward the request to be forwarded to the second microservice in the local server.
4. The request forwarding device according to claim 3, characterized in that: The first request forwarding module is specifically a module that forwards the request to be forwarded to the proxy server through a preset http proxy server port.
5. A request forwarding device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the request forwarding method as claimed in any one of claims 1 to 2 when executing the computer program.
6. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the request forwarding method according to any one of claims 1 to 2 are implemented.
