Resource management method, system, proxy server and storage medium
By introducing load balancing servers and proxy servers into the micro server system, using global resource information for load balancing, the problem of global load imbalance caused by independent load balancing of micro servers is solved, and the accuracy of load balancing and the reliability of resource management is improved. .
Patent Information
- Application Number
- CN202010549774.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-06-16
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2040-06-16
AI Technical Summary
In micro server systems, when load balancing is performed independently by each micro server, global load imbalance may result, reducing the accuracy of load balancing.
By introducing a load balancing server, the micro-server's proxy server reports resource update information to the load balancing server, the load balancing server broadcasts to each proxy server, and the proxy server updates the local resource usage status based on global resource information and performs load balancing operations.
Load balancing based on global resource information is realized, the accuracy of load balancing and the reliability of resource management are improved, and the equal distribution of system resources is ensured.
Smart Images

Figure CN113810443B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a resource management method, system, proxy server and storage medium. Background Art
[0002] Load balancing refers to balancing or distributing the load (work tasks) to multiple operating units for operation, such as distributing the load to File Transfer Protocol (FTP) servers, Web servers, enterprise core application servers, and other major task servers, so as to collaboratively complete work tasks. In a microserver system, each microserver can initiate requests to other microservers. In the scenario of multiple requesters, each microserver of the requester obtains its own local resource information and independently performs load balancing based on its own local resource information, which may cause load imbalance. Therefore, the mechanism of implementing load balancing through the microserver as the requester will result in an unbalanced global load and reduce the accuracy of load balancing. Summary of the invention
[0003] The embodiments of the present application provide a resource management method, system, proxy server and storage medium, which can improve the accuracy of implementing load balancing, and improve the reliability and accuracy of resource management.
[0004] In a first aspect, an embodiment of the present application provides a resource management method, which is applied to a resource management system, wherein the resource management system includes a plurality of micro servers, a proxy server corresponding to each micro server, and a load balancing server, and the resource management method includes:
[0005] When there is resource update information of the micro server, the resource update information is reported to the load balancing server through the proxy server of the micro server;
[0006] Broadcasting the resource update information to the proxy servers corresponding to each micro server through the load balancing server;
[0007] The proxy server corresponding to each micro-server updates the resource usage status of each micro-server pre-stored locally based on the resource update information, so as to perform a load balancing operation based on the resource usage status.
[0008] In a second aspect, an embodiment of the present application further provides a resource management method, the resource management method is applied to a proxy server, the proxy server is a proxy server corresponding to the micro server of the requester, and the resource management method includes:
[0009] When monitoring the existence of resource update information of the micro server, the resource update information is reported to the load balancing server, and the resource usage status of each micro server pre-stored locally is updated based on the resource update information;
[0010] A load balancing operation is performed according to the resource usage status.
[0011] On the third aspect, an embodiment of the present application also provides a resource management system, which includes multiple microservers, a proxy server corresponding to each microserver, and a load balancing server, and the load balancing server is communicatively connected with each proxy server. The resource management system is used to execute any resource management method applied to the resource management system provided in the embodiment of the present application.
[0012] In a fourth aspect, an embodiment of the present application further provides a proxy server, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor calls the computer program in the memory, it executes any resource management method applied to the proxy server provided in the embodiment of the present application.
[0013] In a fifth aspect, an embodiment of the present application further provides a storage medium for computer-readable storage, wherein the storage medium is used to store a computer program, and the computer program is loaded by a processor to execute any resource management method provided in the embodiment of the present application.
[0014] In the embodiment of the present application, when there is resource update information of a microserver, the resource update information can be reported to the load balancing server through the proxy server of the microserver, and then the resource update information can be broadcast to the proxy servers corresponding to each microserver through the load balancing server, so that each proxy server can obtain the global resource information of each microserver. At this time, the proxy server corresponding to each microserver can update the resource usage status of each microserver pre-stored locally based on the resource update information, so that each proxy server can timely and accurately maintain the resource usage status of each microserver, and perform load balancing operations based on the resource usage status, thereby realizing global load balancing based on global resource information, improving the accuracy of implementing load balancing, and improving the reliability and accuracy of resource management. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Figure 1 This is a schematic diagram of the structure of a resource management system provided by an embodiment of the present application.
[0016] Figure 2 It is a flowchart of a resource management method provided by an embodiment of the present application;
[0017] Figure 3is a flowchart of a resource management method provided by another embodiment of the present application;
[0018] Figure 4 is a flowchart of a resource management method provided by another embodiment of the present application;
[0019] Figure 5 is a flowchart of a resource management method provided by another embodiment of the present application;
[0020] Figure 6 is a flowchart of a resource management method provided by another embodiment of the present application;
[0021] Figure 7 It is a schematic diagram of the structure of a proxy server provided by an embodiment of the present application. DETAILED DESCRIPTION
[0022] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.
[0023] The flowcharts shown in the accompanying drawings are only examples and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may also be decomposed, combined or partially merged, so the actual execution order may change according to actual conditions.
[0024] In conjunction with the accompanying drawings, some embodiments of the present application are described in detail below. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.
[0025] Embodiments of the present application provide a resource management method, system, proxy server, and storage medium.
[0026] See also Figure 1 , Figure 1 is a schematic diagram of a structure of a resource management system provided by an embodiment of the present application, such as Figure 1As shown, the resource management system may include multiple micro servers, proxy servers corresponding to each micro server, and a load balancing server, wherein each micro server is connected to its corresponding proxy server, and each proxy server is connected to the load balancing server. For example, the proxy server of each micro server may send a registration request to the load balancing server, and the load balancing server returns a registration response to each proxy server after receiving the registration request, and establishes a connection relationship between the load balancing server and the proxy server of each micro server based on the registration response. Among them, the types of micro servers, proxy servers, and load balancing servers can be flexibly set according to actual needs, and the specific types are not limited here.
[0027] Among them, the load balancing server can be used to: 1) receive the resource usage (i.e., resource usage status) of each microserver instance reported by each proxy server in the resource management system, such as the number of connections and the number of requests, and store the resource occupancy of all microserver instances in the resource management system; 2) after receiving the reported resource usage update event, broadcast it to all proxy servers in the resource management system.
[0028] All proxy servers can be used to: 1) register with the load balancing server and listen to notifications of changes in resource occupancy (i.e., resource usage updates) of each microserver in the resource management system; 2) upon receiving notifications of changes in resource occupancy, save the new resource occupancy in local memory.
[0029] The proxy server as the receiver can be used for: 1) After receiving the request, the proxy server of the receiver reports the current resource occupancy of the instance of the microserver to the load balancing server before forwarding the request to the microserver (also called the local server) connected to it, and then forwards the request to the instance of the microserver, or reports the current resource occupancy of the instance of the microserver to the load balancing server and forwards the request to the instance of the microserver at the same time; 2) When the local server completes processing the request and returns a response, the proxy server of the receiver reports the current resource occupancy to the load balancing server, and then returns a response to the requester; 3) In addition to the start and end time of request processing, during the service processing process, the local server can also call the interface of the proxy server to update the resource occupancy of the local server. The proxy server saves the latest resource occupancy locally and reports it to the load balancing server.
[0030] The proxy server as the requester can be used for: after the requester's microserver sends a request, the requester's proxy server receives the request, obtains the resource occupancy of all instances of the requested microserver from the local memory, combines the load balancing strategy, selects an instance of the receiver's server, and then forwards the request to the instance of the receiver's server, thereby realizing global load balancing including the gateway and all microserver instances.
[0031] Resource usage may include: 1) resource consumption that the proxy server can obtain, such as the current number of connections. This type of information can be automatically obtained and reported by the proxy server; 2) resource consumption that the proxy server cannot obtain, such as resource consumption that can only be estimated by the microserver for a certain type of query. This type of information needs to be sent by the microserver to the proxy server and then reported by the proxy server.
[0032] It should be noted that after the monolithic application evolved into a resource management system (some people may call it a microservice system), the calls within the process became remote calls between processes, and the management and monitoring of a large number of network connections and requests became a difficult problem in the development of resource management systems. In order to free microservers from complex network issues (including load balancing) and focus on business development, service grids were introduced into the resource management system to take on the management and control of the network communications of microservers.
[0033] like Figure 1 In the service grid, the service grid can be logically divided into a data plane and a control plane. The data plane consists of a group of network intelligent proxies, which are deployed together with each microserver instance. The proxy server intercepts the network requests sent and received by the microserver, so these proxy servers can take over the network communication between microservers, and are responsible for microserver forwarding, load balancing, and reporting performance indicators of microserver instances. The control plane is responsible for managing and configuring the proxy server, sending the microserver's load balancing strategy, fuse limiting rules, and collecting performance indicators to the proxy server. Since the proxy server is an enhancement of the microserver, similar to the relationship between a motorcycle and a sidecar, the proxy server in the service grid can also be called a sidecar.
[0034] When the resource management system introduces the service grid, each microserver instance will be deployed together with a proxy server (for example, the microserver instance and the proxy server are deployed in the same pod of k8s). All requests sent by the microserver (i.e. network requests) are forwarded through the proxy server. The load balancing in the resource management system is implemented by the proxy server, which can be specifically as follows: the proxy server obtains the information of all microserver instances through the server discovery component of the control plane; when a microserver initiates a request, the proxy server deployed locally on the microserver can select an instance of the recipient's microserver according to the load balancing strategy and send the request to this instance.
[0035] Specifically, in order to achieve the purpose of distributing requests to multiple microserver instances as evenly as possible in the resource management system, each microserver instance in the resource management system is provided with a proxy server. The microservers do not communicate directly with each other, but are all proxied by the proxy server. All proxy servers constitute the service grid data plane. The control plane of the service grid contains components of the management data plane, such as secure network communication and performance indicator collection. A global load balancing server is newly added to the control plane, which is responsible for storing and broadcasting the resource usage of all microservers, such as the number of connections, CPU, and memory usage. All proxy servers report the resource usage of the microserver instances they represent to the load balancing server, and all proxy servers can also obtain the resource usage of other microserver instances from the load balancing server, so as to achieve global load balancing based on the resource usage of each microserver instance. By introducing a global load balancing server in the resource management system, which is responsible for storing and broadcasting the resource usage status of all microserver instances, the proxy server can report and share the resource usage status of all microserver instances, and the microservice as the recipient can also update its own resource usage status through the proxy server. This enables all requesters to obtain the resource load status of all microserver instances globally, implement load balancing more accurately, and achieve the goal of evenly distributing resources across the entire system.
[0036] In a resource management system composed of multiple microservers, each microserver undertakes its own business, each microserver is an independent process, and multiple microservers are accessed through remote calls. For example, in a network management system, there are microservers such as topology, alarm, and resources. Topology and alarm can call the resource server interface to query the information of resource objects.
[0037] In a resource management system (also known as a microservice system), load balancing occurs not only at the gateway, but also between each microserver. For example, the resource server has three instances. When the alarm calls the resource server interface, it is necessary to select an instance of a microserver through a load balancing algorithm. For a single application, all externally initiated requests will pass through the gateway, so a simple load balancing strategy can basically achieve the purpose of evenly distributing the load of external requests on multiple service instances. In a resource management system, load balancing will occur in many places. For example, in a network management system, topology and alarms will send requests to the resource server, and topology and alarms themselves may also have multiple instances. Since there are multiple sources of requests, if load balancing is done independently at multiple request sources, the purpose of evenly distributing the load cannot be achieved well. Therefore, the embodiment of the present application can collect global resource information for all microserver instances in the resource management system, and use this as the basis for the load balancing strategy to achieve the optimal selection of microserver instances, and achieve the purpose of global average distribution. Multiple requesters share request information, which can avoid the consequence of extremely unbalanced loads on multiple instances of the receiving party.
[0038] For example, assuming that a polling load balancing strategy is adopted, there are two instances of alarms and resources. After a period of time, the following situation occurs: Alarm instance 1 has 5 requests being processed, resource instance 1 has 2, and resource instance 2 has 3; Alarm instance 2 has 6 requests being processed, resource instance 1 has 5, and resource instance 2 has 1; If the alarm instance wants to send a new request, the existing local load balancing considers that the new request should be sent to resource instance 1 based on its own recorded data, and the embodiment of the present application can determine to send to resource instance 2 from the resource information of the global micro-server instance. From this example, it can be seen that when multiple requesters do not share request information, it may cause the load of the receiver to be extremely unbalanced. The embodiment of the present application solves this problem, that is, based on the global resource information of all micro-server instances as the basis of the load balancing strategy, the optimal selection of the micro-server instance can be achieved. Even in the special case where there are many requester instances and few receiver instances, or when the request consumes a lot of resources on the receiver, the embodiment of the present application can achieve the effect of load balancing.
[0039] For example, a certain microserver provides an interface that can query a certain type of data, such as all network element information belonging to a certain region. Based on the resource management method of the embodiment of the present application, the requester can correctly estimate the resource consumption of the receiver: the number of network elements in each region varies greatly, and the resource consumption varies greatly when querying the same region. Load balancing can introduce weights, and the requester can accurately estimate resource consumption. After receiving the request, the receiver can first check the total number of resources in the region, and then estimate how many resources are needed to collect all resource data. For another example, the resource consumption of the receiver is not a fixed value: when querying information, the resource consumption may be relatively large at the beginning, and in the subsequent processing, the consumed resources are reduced a lot. Although the request has not been processed at this time, a large amount of resources have actually been released. At this time, the requester's proxy server can obtain the resource usage of the receiver's microserver from the load balancing server, which can better distribute the requests evenly.
[0040] In a scenario with multiple requesters, if each requester performs load balancing independently, since each requester only obtains local information, the global load may be extremely unbalanced. By introducing a load balancing server, all proxy servers can report and share the resource usage of all microserver instances, share global information, and the requester can obtain the real resource usage of all microserver instances, so that all requesters can implement load balancing more accurately, achieve the goal of evenly distributing resources in the entire system, and achieve global load balancing.
[0041] In the embodiment of the present application, when there is resource update information of a microserver, the resource update information can be reported to the load balancing server through the proxy server of the microserver, and then the resource update information can be broadcast to the proxy servers corresponding to each microserver through the load balancing server, so that each proxy server can obtain the global resource information of each microserver, and at this time, the resource usage status of each microserver pre-stored locally can be updated based on the resource update information through the proxy server corresponding to each microserver, so that each proxy server can timely and accurately maintain the resource usage status of each microserver. For example, a request is initiated through the microserver of the requester, and the resource occupancy information of the request is obtained; the resource occupancy information is reported to the load balancing server through the proxy server of the requester; the resource occupancy information is broadcast to the proxy servers corresponding to each microserver through the load balancing server; the resource occupancy information is updated based on the resource occupancy information through the proxy server corresponding to each microserver; the resource usage status of each microserver pre-stored locally is updated based on the resource occupancy information through the proxy server corresponding to each microserver. For another example, when the microserver of the receiving party completes processing of the request initiated by the requesting party, the resource release information of the request is obtained through the proxy server of the receiving party, and the resource release information is reported to the load balancing server; the resource release information is broadcasted to the proxy servers corresponding to each microserver through the load balancing server; the resource usage status of each microserver pre-stored locally is updated based on the resource release information by the proxy servers corresponding to each microserver. At this time, the proxy server can perform load balancing operations based on the resource usage status, for example, the microserver of the receiving party corresponding to the request is determined based on the resource usage status of each microserver pre-stored locally and the preset load balancing strategy through the proxy server of the requesting party; the request is sent to the proxy server of the receiving party through the proxy server of the requesting party, and the request is forwarded to the microserver of the receiving party through the proxy server of the receiving party. In this way, global load balancing based on global resource information is realized, the accuracy of load balancing is improved, and the reliability and accuracy of resource management are improved.
[0042] In the above embodiments, the description of each embodiment has its own focus. For the part that is not described in detail in a certain embodiment, please refer to the detailed description of the resource management method below, which will not be repeated here.
[0043] It should be noted that Figure 1 The structure of the resource management system does not constitute a limitation on the application scenario of the resource management method. The resource management method will be described in detail below.
[0044] See also Figure 2 , Figure 21 is a flow chart of a resource management method provided by an embodiment of the present application. The resource management method can be applied to a resource management system, and the resource management method may include but is not limited to steps S10 to S30, etc., and may be specifically as follows:
[0045] S10: When there is resource update information of the micro server, the resource update information is reported to the load balancing server through the proxy server of the micro server.
[0046] Among them, resource update information may include resource occupancy information and resource release information, etc., resource occupancy information may include information such as occupied memory resources and occupied CPU resources, and resource release information may include information such as released memory resources and released CPU resources. For example, the resource occupancy information can be reported to the load balancing server through the proxy server of the microserver, or the resource release information can be reported to the load balancing server through the proxy server of the microserver.
[0047] S20. Broadcast resource update information to proxy servers corresponding to each micro server through the load balancing server.
[0048] After receiving the resource update information, the load balancing server can broadcast the resource update information to the proxy servers corresponding to each micro server.
[0049] S30. The proxy server corresponding to each micro-server updates the locally pre-stored resource usage status of each micro-server based on the resource update information, so as to perform a load balancing operation based on the resource usage status.
[0050] Among them, each proxy server maintains the resource usage status of each micro server in the resource management system. After receiving the resource update information broadcast by the load balancing server, each proxy server can update the resource usage status of each micro server in the local pre-stored resource management system based on the resource update information. Subsequently, each proxy server can perform load balancing operations based on the resource usage status.
[0051] It should be noted that when there is resource update information of a microserver, the proxy server corresponding to the microserver can update the resource usage status of each microserver in the locally pre-stored resource management system, and report the resource update information to the load balancing server through the proxy server of the microserver. At this time, the load balancing server can broadcast the resource update information to other proxy servers in the resource management system, so that other proxy servers update the resource usage status of each microserver in the locally pre-stored resource management system based on the resource update information. The other proxy servers are all proxy servers in the resource management system except the proxy server that reports the resource update information. Alternatively, when there is resource update information of a microserver, the resource update information can be reported to the load balancing server through the proxy server of the microserver. At this time, the load balancing server can broadcast the resource update information to all proxy servers in the resource management system (including the proxy server that reports the resource update information), so that all proxy servers update the resource usage status of each microserver in the locally pre-stored resource management system based on the resource update information.
[0052] In one embodiment, the resource management method may also include: configuring a corresponding proxy server for each microserver in the resource management system, and configuring a load balancing server; sending a registration request to the load balancing server through the proxy server of each microserver; and establishing a connection relationship between the load balancing server and the proxy server of each microserver according to the registration request.
[0053] In order to improve the reliability of data interaction and the accuracy of load balancing, in the resource management system, a corresponding proxy server is configured for each microserver, as well as a load balancing server. Then, a registration request is sent to the load balancing server through the proxy server of each microserver. Each proxy server can receive a registration response returned by the load balancing server, and establish a connection relationship between the load balancing server and the proxy server of each microserver based on the registration response, so that data interaction can be performed between the load balancing server and the proxy server.
[0054] Reference Figure 3 In one embodiment, when there is a resource update of a microserver, the resource update information is reported to the load balancing server through the proxy server of the microserver, the resource update information is broadcast to the proxy servers corresponding to each microserver through the load balancing server, and the proxy servers corresponding to each microserver update the resource usage status of each microserver pre-stored locally based on the resource update information, which may include but is not limited to steps S11 and S14, etc., and may be specifically as follows:
[0055] Step S11: Initiate a request through the micro server of the requesting party, and obtain resource occupancy information of the request;
[0056] Step S12: Report resource occupancy information to the load balancing server through the requester's proxy server;
[0057] Step S13: broadcast resource occupancy information to proxy servers corresponding to each micro server through the load balancing server;
[0058] Step S14: The proxy server corresponding to each micro-server updates the locally stored resource usage status of each micro-server based on the resource occupancy information.
[0059] In order to improve the timeliness and convenience of updating the resource usage status, the resource usage status can be updated when a request is initiated. Specifically, in the resource management system, any microserver can be used as a requester's microserver or a receiver's microserver, wherein the requester's microserver can initiate a request and obtain the resource occupancy information of the request, such as the amount of resource A occupied by the request and the amount of resource B occupied. Then the requester's proxy server can report the resource occupancy information to the load balancing server. After receiving the resource occupancy information, the load balancing server can update the resource usage status of each microserver in the locally pre-stored resource management system according to the resource occupancy information, and broadcast the resource occupancy information to the proxy servers corresponding to each microserver. At this time, the proxy servers corresponding to each microserver can update the resource usage status of each microserver in the locally pre-stored resource management system based on the received resource occupancy information. For example, based on the resource occupancy information of instance 1 of microserver A, the resource occupancy of instance 1 of microserver A stored locally can be updated.
[0060] Reference Figure 4 In one embodiment, the load balancing operation performed based on the resource usage status may include but is not limited to step S21 and step S22, etc., and may be specifically as follows:
[0061] Step S21: The requesting party's proxy server determines the receiving party's micro server corresponding to the request based on the locally stored resource usage status of each micro server and a preset load balancing strategy;
[0062] Step S22: Send the request to the recipient's proxy server through the requester's proxy server, and forward the request to the recipient's micro server through the recipient's proxy server.
[0063] Among them, the load balancing strategy can be flexibly set according to actual needs. For example, the load balancing strategy can include weighted polling, random, minimum number of connections priority, and response speed priority. The purpose of load balancing is to distribute the load to each microserver instance as evenly as possible. For example, the minimum number of connections priority is based on an assumption that the microserver resources consumed by each connection are basically the same, so the number of connections can be used to estimate the resources occupied by the microserver. Because the microserver with the least connections has the most remaining available resources, the request can be distributed to the microserver with the least connections first, so the purpose of even distribution can be achieved.
[0064] In order to improve the accuracy and flexibility of request distribution, requests can be distributed based on load balancing strategies. For example, the requester's proxy server can determine the recipient's microserver corresponding to the request based on the resource usage status of each microserver in the local pre-stored resource management system and the preset load balancing strategy. Then, the requester's proxy server can send the request to the recipient's proxy server, and at this time, the recipient's proxy server can forward the request to the recipient's microserver.
[0065] In one embodiment, the load balancing strategy is the minimum number of connections first, and the requester's proxy server determines the recipient's microserver corresponding to the request based on the resource usage status of each microserver pre-stored locally and the preset load balancing strategy, including: the requester's proxy server sets the instance of the microserver corresponding to the minimum number of connections among multiple microservers as the instance of the recipient's microserver corresponding to the request based on the resource usage status of each microserver instance pre-stored locally and the load balancing strategy of the minimum number of connections first. Forwarding the request to the recipient's microserver through the recipient's proxy server includes: forwarding the request to the recipient's microserver instance through the recipient's proxy server.
[0066] In order to improve the accuracy and convenience of load balancing, requests can be distributed based on a load balancing strategy that prioritizes the minimum number of connections. Specifically, after the requester's microserver initiates a request, the requester's proxy server can filter out the instance of the microserver corresponding to the minimum number of connections from multiple microservers based on the resource usage status of each microserver instance pre-stored locally and the load balancing strategy that prioritizes the minimum number of connections, and set the instance of the microserver corresponding to the minimum number of connections as the instance of the recipient's microserver corresponding to the request. Then, the requester's proxy server can send the request to the instance of the recipient's microserver, and at this time, the request is received by the recipient's proxy server, and the recipient's proxy server can forward the request to the instance of the recipient's microserver.
[0067] For example, the requester's microserver sets the load balancing policy to prioritize the minimum number of connections. The requester's microserver sends request 1 to the receiver's proxy server through the requester's proxy server. After receiving request 1, the receiver's proxy server increases the number of connections of this instance by 1, reports it to the load balancing server, and then sends request 1 to the local service instance (i.e., the receiver's microserver instance). After receiving the information reporting the number of connections +1, the load balancing server updates the number of connections of the receiver's microserver instance, and then broadcasts it to all proxy servers in the resource management system. All proxy servers (except the proxy server that reports the information) update the number of connections of this instance of the receiver's microserver. Then, the proxy server that initiates the new request can find the resource occupancy information of all instances of all microservers in the local memory, find the instance with the least number of connections, and send the request to this instance. After receiving the response to request 1, the receiver's proxy server decreases the number of connections of this instance by 1, closes the connection, and reports it to the load balancing server. After receiving the information of reporting the number of connections -1, the load balancing server updates the number of connections of the receiving proxy server for this instance, and then broadcasts it to all proxy servers. All proxy servers (except the proxy server that reports the information) update the number of connections of this instance.
[0068] In one embodiment, the load balancing strategy is response speed priority, and the requester's proxy server determines the recipient's microserver corresponding to the request based on the resource usage status of each microserver pre-stored locally and the preset load balancing strategy, including: the requester's proxy server sets the instance of the microserver corresponding to the fastest response speed among multiple microservers as the instance of the recipient's microserver corresponding to the request based on the resource usage status of each microserver instance pre-stored locally and the load balancing strategy of response speed priority. Forwarding the request to the recipient's microserver through the recipient's proxy server includes: forwarding the request to the recipient's microserver instance through the recipient's proxy server.
[0069] In order to improve the accuracy and flexibility of load balancing, requests can be distributed based on a load balancing strategy that prioritizes response speed. Specifically, after the requester's microserver initiates a request, the requester's proxy server can filter out the instance of the microserver corresponding to the fastest response speed from multiple microservers based on the resource usage status of each microserver instance in the locally pre-stored resource management system and the load balancing strategy that prioritizes response speed, and set the instance of the microserver corresponding to the fastest response speed among the multiple microservers as the instance of the recipient's microserver corresponding to the request. Then, the requester's proxy server can send the request to the instance of the recipient's microserver, and the request is received by the recipient's proxy server, which forwards the request to the instance of the recipient's microserver.
[0070] For example, some microservers need a period of warm-up before they can handle a large number of requests. When a fixed weight is used, if a large number of requests are sent to a newly started service instance, the node will be overloaded. Therefore, the distribution of requests can be adjusted dynamically. The requesting microserver sets the load balancing policy to prioritize response speed. When this microserver A is just started, it can only process 10 requests / s. After sufficient warm-up, it can process 200 requests / s. Therefore, the default weight of the instance of microserver A is configured to be 10, and after sufficient warm-up, the authority is 1K. When the instance of microserver A is just started, the proxy server that initiates the request allocates requests to this instance according to the weight of 10. After a period of warm-up, microserver A can process 200 requests / s. At this time, the weight of the instance of microserver A can be updated to 200 and reported to the load balancing server. After receiving the report information, the load balancing server updates the weight of this instance and then broadcasts it to all proxy servers. All proxy servers (except the proxy server that reports information) update the weight of this instance of microserver A. The larger the weight, the faster the response speed, and the smaller the weight, the slower the response speed. The proxy server that initiates a new request finds the weights of all microserver instances in the local memory and allocates requests to all microserver instances according to the weights. For example, if there is a newly started instance and two fully preheated instances, then the ratio of the number of requests allocated in the same time can be 1:20:20.
[0071] In one embodiment, the load balancing strategy is weighted polling, and the requester's proxy server determines the recipient's microserver corresponding to the request based on the resource usage status of each microserver pre-stored locally and the preset load balancing strategy, including: the requester's proxy server sets the instance of the microserver corresponding to the smallest weight among multiple microservers as the instance of the recipient's microserver corresponding to the request based on the resource usage status of each microserver instance pre-stored locally and the weighted polling load balancing strategy; the weight is the weight of the resources consumed in processing the request. Forwarding the request to the recipient's microserver through the recipient's proxy server includes: forwarding the request to the recipient's microserver instance through the recipient's proxy server.
[0072] In order to improve the accuracy and reliability of load balancing, requests can be distributed based on a weighted round-robin load balancing strategy. Specifically, after the requester's microserver initiates a request, the requester's proxy server can filter out the instance of the microserver corresponding to the smallest weight from multiple microservers based on the resource usage status of each microserver instance pre-stored locally and the weighted round-robin load balancing strategy, and set the instance of the microserver corresponding to the smallest weight among the multiple microservers as the instance of the recipient's microserver corresponding to the request, with the weight being the weight of the resources consumed to process the request. Then, the requester's proxy server can send the request to the instance of the recipient's microserver, and at this time, the request is received by the recipient's proxy server, and the recipient's proxy server can forward the request to the instance of the recipient's microserver.
[0073] For example, the microserver of the requester sets the load balancing strategy to poll by weight. The microserver of the requester sets the weight value for the processing resource consumption of each type of request, such as the weight values of small, medium and large are 1, 2, and 4. After receiving the request, the proxy server of the receiver calculates the weight value, increases the total weight of this instance, reports it to the load balancing server, and then sends the request to the local service instance. After receiving the information of the reported total weight, the load balancing server updates the weight of this instance of the microserver of the receiver, and then broadcasts it to all proxy servers in the resource management system. All proxy servers (except the proxy server that reports the information) update the weight of this instance of the microserver of the receiver. Then, the proxy server that initiates the new request can find the resource occupation information of all instances of all microservers in the local memory, find the instance with the lowest weight, and send the request to this instance. After receiving the response to the request, the proxy server of the receiver subtracts the weight corresponding to the request and reports it to the load balancing server. After receiving the reported information, the load balancing server updates the weight of this instance and then broadcasts it to all proxy servers. All proxy servers (except the proxy server that reported the information) update the weight value of this instance.
[0074] Reference Figure 5 In one embodiment, when there is a resource update of a microserver, the resource update information is reported to the load balancing server through the proxy server of the microserver, and the resource update information is broadcast to the proxy servers corresponding to each microserver through the load balancing server. The proxy servers corresponding to each microserver update the resource usage status of each microserver pre-stored locally based on the resource update information, which may include but is not limited to steps 31 to S33, etc., and may be specifically as follows:
[0075] Step S31: After the micro server of the receiving party completes processing the request initiated by the requesting party, it obtains the resource release information of the request through the proxy server of the receiving party, and reports the resource release information to the load balancing server;
[0076] Step S32: broadcast resource release information to proxy servers corresponding to each micro server through the load balancing server;
[0077] Step S33: The proxy server corresponding to each micro-server updates the locally pre-stored resource usage status of each micro-server based on the resource release information.
[0078] In order to improve the timeliness and accuracy of updating the resource usage status, the resource usage status can be updated when the request processing is completed. Specifically, in the resource management system, any microserver can be used as a microserver of the requester or a microserver of the receiver, wherein the microserver of the receiver can receive the request initiated by the requester and process the request. When the microserver of the receiver completes the processing of the request initiated by the requester, the proxy server of the receiver can obtain the resource release information of the request that has been processed, such as the amount of resource A released by the request and the amount of resource B released, and report the resource release information to the load balancing server. After receiving the resource release information, the load balancing server can update the resource usage status of each microserver in the locally pre-stored resource management system according to the resource release information, and broadcast the resource release information to the proxy servers corresponding to each microserver. At this time, the proxy servers corresponding to each microserver can update the resource usage status of each locally pre-stored microserver based on the resource release information.
[0079] In the embodiment of the present application, when there is resource update information of a microserver, the resource update information can be reported to the load balancing server through the proxy server of the microserver, and then the resource update information can be broadcast to the proxy servers corresponding to each microserver through the load balancing server, so that each proxy server can obtain the global resource information of each microserver. At this time, the proxy server corresponding to each microserver can update the resource usage status of each microserver pre-stored locally based on the resource update information, so that each proxy server can timely and accurately maintain the resource usage status of each microserver, and perform load balancing operations based on the resource usage status, thereby realizing global load balancing based on global resource information, improving the accuracy of implementing load balancing, and improving the reliability and accuracy of resource management.
[0080] See also Figure 6 , Figure 61 is a flow chart of a resource management method provided by an embodiment of the present application. The resource management method can be applied to a proxy server, and the resource management method may include but is not limited to steps S101 to S102, and may be specifically as follows:
[0081] S101. When it is detected that a micro server has resource update information, the resource update information is reported to the load balancing server, and the resource usage status of each micro server pre-stored locally is updated based on the resource update information.
[0082] S102: Perform load balancing operations according to resource usage status.
[0083] In one embodiment, when resource update information of a microserver is monitored, the resource update information is reported to the load balancing server, and the resource usage status of each locally stored microserver is updated based on the resource update information, which may include: obtaining resource occupancy information of the request initiated by the requesting microserver; reporting the resource occupancy information to the load balancing server; and, updating the resource usage status of each locally stored microserver based on the resource occupancy information.
[0084] In one embodiment, performing a load balancing operation based on resource usage status may include: according to the resource usage status and a load balancing strategy that prioritizes the minimum number of connections, setting the instance of a microserver corresponding to the smallest number of connections among multiple microservers as the instance of the microserver of the recipient corresponding to the request; sending the request to the proxy server of the recipient so that the proxy server of the recipient forwards the request to the instance of the microserver of the recipient.
[0085] In one embodiment, performing a load balancing operation based on resource usage status may include: according to the resource usage status and a load balancing strategy that prioritizes response speed, setting the instance of a microserver corresponding to the fastest response speed among multiple microservers as the instance of the microserver of the recipient corresponding to the request; sending the request to the proxy server of the recipient, so that the proxy server of the recipient forwards the request to the instance of the microserver of the recipient.
[0086] In one embodiment, performing a load balancing operation according to resource usage status may include: according to the resource usage status and a load balancing strategy of weight polling, setting the instance of a microserver corresponding to the smallest weight among multiple microservers as the instance of the microserver of the recipient corresponding to the request; the weight is the weight of the resources consumed in processing the request; and sending the request to the proxy server of the recipient so that the proxy server of the recipient forwards the request to the instance of the microserver of the recipient.
[0087] In one embodiment, performing a load balancing operation according to resource usage status may include: receiving resource release information broadcast by a load balancing server, where the resource release information is reported to the load balancing server through the recipient's proxy server after the recipient's microserver completes processing of the request initiated by the requester; and updating the resource usage status of each locally pre-stored microserver instance according to the resource release information.
[0088] In one embodiment, the resource management method may further include: sending a registration request to the load balancing server, and establishing a connection relationship with the load balancing server according to the registration request; or, sending a deregistration request to the load balancing server, and deregistering the connection relationship with the load balancing server according to the deregistration request.
[0089] In the above embodiments, the description of each embodiment has its own focus. For the part that is not described in detail in a certain embodiment, please refer to the detailed description of the resource management method above, and will not be repeated here.
[0090] In the embodiment of the present application, when the resource update information of the microserver is detected, the proxy server can report the resource update information to the load balancing server, so that the load balancing server timely broadcasts the resource update information to the proxy servers corresponding to each microserver, so that each proxy server can obtain the global resource information of each microserver, and the proxy server corresponding to each microserver updates the resource usage status of each microserver pre-stored locally based on the resource update information, so that each proxy server can timely and accurately maintain the resource usage status of each microserver, and update the resource usage status of each microserver pre-stored locally based on the resource update information, so that the resource usage status of each microserver can be accurately maintained. The proxy server can perform load balancing operations according to the resource usage status, thereby realizing global load balancing based on global resource information, improving the accuracy of implementing load balancing, and improving the reliability and accuracy of resource management.
[0091] See also Figure 7 , Figure 7 It is a schematic block diagram of the structure of a proxy server provided in an embodiment of the present application.
[0092] like Figure 7 As shown, the proxy server 300 may include a processor 302 , a memory 303 , and a communication interface 304 connected via a system bus 301 , wherein the memory 303 may include a non-volatile computer-readable storage medium and an internal memory.
[0093] The non-volatile computer-readable storage medium can store a computer program. The computer program includes program instructions, and when the program instructions are executed, the processor can execute any resource management method.
[0094] The processor 302 is used to provide computing and control capabilities to support the operation of the entire proxy server.
[0095] The memory 303 provides an environment for the operation of a computer program in a non-volatile computer-readable storage medium. When the computer program is executed by the processor 302, the processor 302 can execute any resource management method.
[0096] The communication interface 304 is used for communication. Those skilled in the art will appreciate that Figure 7 The structure shown in the figure is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the proxy server 300 to which the solution of the present application is applied. The specific proxy server 300 may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.
[0097] It should be understood that the bus 301 is, for example, an I2C (Inter-integrated Circuit) bus, the memory 303 may be a Flash chip, a read-only memory (ROM) disk, an optical disk, a USB flash drive or a mobile hard disk, etc., the processor 302 may be a central processing unit (CPU), and the processor 302 may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.
[0098] In one embodiment, the processor 302 is used to run a computer program stored in the memory 303 to perform the following steps:
[0099] When resource update information of a micro server is detected, the resource update information is reported to the load balancing server, and the resource usage status of each micro server pre-stored locally is updated based on the resource update information; and the load balancing operation is performed according to the resource usage status.
[0100] In one embodiment, when reporting resource update information to the load balancing server and updating the resource usage status of each micro server stored locally based on the resource update information, the processor 302 also executes: obtaining resource occupancy information of the request initiated by the micro server of the requesting party; reporting the resource occupancy information to the load balancing server; and, updating the resource usage status of each micro server stored locally based on the resource occupancy information.
[0101] In one embodiment, when performing a load balancing operation according to the resource usage status, the processor 302 also executes: according to the resource usage status and the load balancing strategy with the minimum number of connections first, setting the instance of the microserver corresponding to the smallest number of connections among multiple microservers as the instance of the microserver of the recipient corresponding to the request; sending the request to the proxy server of the recipient, so that the proxy server of the recipient forwards the request to the instance of the microserver of the recipient.
[0102] In one embodiment, when performing a load balancing operation according to the resource usage status, the processor 302 also executes: according to the resource usage status and the load balancing strategy that prioritizes response speed, setting the instance of the microserver corresponding to the fastest response speed among multiple microservers as the instance of the microserver of the recipient corresponding to the request; sending the request to the proxy server of the recipient, so that the proxy server of the recipient forwards the request to the instance of the microserver of the recipient.
[0103] In one embodiment, when performing a load balancing operation according to the resource usage status, the processor 302 also executes: according to the resource usage status and the load balancing strategy of weight polling, the instance of the microserver corresponding to the smallest weight among multiple microservers is set as the instance of the microserver of the recipient corresponding to the request; the weight is the weight of the resources consumed by processing the request; the request is sent to the proxy server of the recipient, so that the proxy server of the recipient forwards the request to the instance of the microserver of the recipient.
[0104] In one embodiment, when performing a load balancing operation according to the resource usage status, the processor 302 further executes: receiving resource release information broadcast by the load balancing server, the resource release information being reported to the load balancing server through the receiving party's proxy server after the receiving party's micro-server completes processing of the request initiated by the requester; and updating the resource usage status of each locally pre-stored micro-server instance according to the resource release information.
[0105] In one embodiment, the processor 302 further executes: sending a registration request to the load balancing server, and establishing a connection relationship with the load balancing server according to the registration request; or sending a deregistration request to the load balancing server, and deregistering the connection relationship with the load balancing server according to the deregistration request.
[0106] In the above embodiments, the description of each embodiment has its own focus. For the part that is not described in detail in a certain embodiment, please refer to the detailed description of the resource management method above, and will not be repeated here.
[0107] The embodiment of the present application also provides a computer-readable storage medium, which stores a computer program, which includes program instructions, and the processor executes the program instructions to implement any resource management method provided in the embodiment of the present application. The specific implementation of each of the above operations can be referred to the previous embodiment, which will not be repeated here.
[0108] The computer-readable storage medium may be an internal storage unit of the mobile terminal of the aforementioned embodiment, such as a hard disk or memory of the mobile terminal. The computer-readable storage medium may also be an external storage device of the mobile terminal, such as a plug-in hard disk, a smart memory card (SmartMediaCard, SMC), a secure digital (SecureDigital, SD) card, a flash card (FlashCard), etc. equipped on the mobile terminal.
[0109] Since the computer program stored in the computer-readable storage medium can execute any one of the resource management methods provided in the embodiments of the present application, the beneficial effects that can be achieved by any one of the resource management methods provided in the embodiments of the present application can be achieved. Please refer to the previous embodiments for details and will not be repeated here.
[0110] It should be understood that the terms used in this application specification are only for the purpose of describing specific embodiments and are not intended to limit the application. As used in this application specification and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include plural forms.
[0111] It should also be understood that the term "and / or" used in the specification of this application and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, including these combinations. It should be noted that, in this article, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "including a..." does not exclude the presence of other identical elements in the process, method, article or system including the element.
[0112] The serial numbers of the embodiments of the present application are for description only and do not represent the advantages and disadvantages of the embodiments. The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present application, and these modifications or replacements should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.
Claims
1. A resource management method, It is characterized in that The resource management method is applied to a resource management system, the resource management system includes a plurality of micro servers, a proxy server corresponding to each micro server, and a load balancing server, and the resource management method includes: When there is resource update information of the micro server, the resource update information is reported to the load balancing server through the proxy server of the micro server; Broadcasting the resource update information to the proxy servers corresponding to each micro server through the load balancing server; The proxy server corresponding to each micro-server updates the resource usage status of each micro-server pre-stored locally based on the resource update information, so as to perform a load balancing operation based on the resource usage status; The proxy server is used to intercept network requests sent and received by the corresponding micro server, and monitor the resource usage status of the corresponding micro server instance, wherein the resource usage status includes: the number of connections and the number of requests.
2. The resource management method according to claim 1, It is characterized in that When there is a resource update of the microserver, the resource update information is reported to the load balancing server through the proxy server of the microserver, the resource update information is broadcast to the proxy servers corresponding to each microserver through the load balancing server, and the resource usage status of each microserver pre-stored locally is updated based on the resource update information through the proxy servers corresponding to each microserver. The method includes: Initiate a request through the micro server of the requester, and obtain resource occupancy information of the request; Reporting the resource occupancy information to the load balancing server through the proxy server of the requester; Broadcasting the resource occupancy information to the proxy servers corresponding to each micro-server through the load balancing server; The proxy server corresponding to each micro server updates the resource usage status of each micro server pre-stored locally based on the resource occupancy information.
3. The resource management method according to claim 2, It is characterized in that The performing of a load balancing operation based on the resource usage status comprises: Determine the micro server of the recipient corresponding to the request through the proxy server of the requester based on the resource usage status of each micro server pre-stored locally and a preset load balancing strategy; The request is sent to the proxy server of the recipient through the proxy server of the requester, and the request is forwarded to the micro server of the recipient through the proxy server of the recipient.
4. The resource management method according to claim 3, It is characterized in that The load balancing strategy is that the minimum number of connections is given priority, and the proxy server of the requester determines the micro server of the recipient corresponding to the request based on the resource usage status of each micro server pre-stored locally and the preset load balancing strategy, including: The proxy server of the requester sets the instance of the microserver corresponding to the smallest number of connections among the multiple microservers as the instance of the microserver of the recipient corresponding to the request based on the resource usage status of each microserver instance pre-stored locally and the load balancing strategy with the smallest number of connections first; The step of forwarding the request to the micro server of the recipient through the proxy server of the recipient includes: The request is forwarded to the instance of the micro server of the recipient through the proxy server of the recipient.
5. The resource management method according to claim 3, It is characterized in that The load balancing strategy is response speed priority, and the proxy server of the requester determines the micro server of the recipient corresponding to the request based on the resource usage status of each micro server pre-stored locally and the preset load balancing strategy, including: The proxy server of the requester sets the instance of the microserver corresponding to the fastest response speed among the multiple microservers as the instance of the microserver of the recipient corresponding to the request based on the resource usage status of each microserver instance pre-stored locally and the load balancing strategy with response speed priority; The step of forwarding the request to the micro server of the recipient through the proxy server of the recipient includes: The request is forwarded to the instance of the micro server of the recipient through the proxy server of the recipient.
6. The resource management method according to claim 3, It is characterized in that The load balancing strategy is weighted polling, and the proxy server of the requester determines the micro server of the recipient corresponding to the request based on the resource usage status of each micro server pre-stored locally and the preset load balancing strategy, including: The proxy server of the requester sets the instance of the microserver corresponding to the smallest weight among multiple microservers as the instance of the microserver of the recipient corresponding to the request based on the resource usage status of each microserver instance pre-stored locally and the load balancing strategy of weight polling; the weight is the weight of the resources consumed by processing the request; The step of forwarding the request to the micro server of the recipient through the proxy server of the recipient includes: The request is forwarded to the instance of the micro server of the recipient through the proxy server of the recipient.
7. The resource management method according to claim 1, It is characterized in that When there is a resource update of the microserver, the resource update information is reported to the load balancing server through the proxy server of the microserver, the resource update information is broadcast to the proxy servers corresponding to each microserver through the load balancing server, and the resource usage status of each microserver pre-stored locally is updated based on the resource update information through the proxy servers corresponding to each microserver. The method includes: When the micro server of the receiving party completes processing the request initiated by the requesting party, it obtains the resource release information of the request through the proxy server of the receiving party, and reports the resource release information to the load balancing server; Broadcasting the resource release information to the proxy servers corresponding to each micro server through the load balancing server; The proxy server corresponding to each micro server updates the resource usage status of each micro server pre-stored locally based on the resource release information.
8. The resource management method according to any one of claims 1 to 7, It is characterized in that The resource management method further includes: Configure a corresponding proxy server for each micro server in the resource management system, and configure a load balancing server; Sending a registration request to the load balancing server through the proxy server of each micro server; A connection relationship between the load balancing server and the proxy server of each micro server is established according to the registration request.
9. A resource management method, It is characterized in that The resource management method is applied to a proxy server, the proxy server being a proxy server corresponding to a micro server of a requesting party, and the resource management method comprises: When resource update information of a micro server is detected, the resource update information is reported to the load balancing server, and the resource usage status of each micro server pre-stored locally is updated based on the resource update information; Performing a load balancing operation according to the resource usage status; The proxy server is used to intercept network requests sent and received by the corresponding micro server, and monitor the resource usage status of the corresponding micro server instance, wherein the resource usage status includes: the number of connections and the number of requests.
10. The resource management method according to claim 9, It is characterized in that When monitoring that there is resource update information of the micro server, reporting the resource update information to the load balancing server, and updating the resource usage status of each micro server pre-stored locally based on the resource update information includes: Obtain resource occupancy information of the request initiated by the micro server of the requesting party; reporting the resource occupancy information to the load balancing server; and, The resource usage status of each micro-server pre-stored locally is updated based on the resource occupancy information.
11. The resource management method according to claim 9, It is characterized in that The performing of the load balancing operation according to the resource usage status comprises: According to the resource usage status and the load balancing strategy with the minimum number of connections first, the instance of the micro server corresponding to the minimum number of connections among the multiple micro servers is set as the instance of the micro server of the recipient corresponding to the request; The request is sent to the proxy server of the recipient, so that the proxy server of the recipient forwards the request to the instance of the micro server of the recipient.
12. The resource management method according to claim 9, It is characterized in that The performing of the load balancing operation according to the resource usage status comprises: According to the resource usage status and the response speed-prioritized load balancing strategy, the instance of the microserver corresponding to the fastest response speed among the multiple microservers is set as the instance of the microserver of the recipient corresponding to the request; The request is sent to the proxy server of the recipient, so that the proxy server of the recipient forwards the request to the instance of the micro server of the recipient.
13. The resource management method according to claim 9, It is characterized in that The performing of the load balancing operation according to the resource usage status comprises: According to the resource usage status and the load balancing strategy of weighted polling, the instance of the microserver corresponding to the smallest weight among the multiple microservers is set as the instance of the microserver of the recipient corresponding to the request; the weight is the weight of the resources consumed by processing the request; The request is sent to the proxy server of the recipient, so that the proxy server of the recipient forwards the request to the instance of the micro server of the recipient.
14. The resource management method according to claim 9, It is characterized in that The performing of the load balancing operation according to the resource usage status comprises: Receiving resource release information broadcasted by the load balancing server, wherein the resource release information is reported to the load balancing server through the proxy server of the receiver after the micro server of the receiver completes processing the request initiated by the requester; The resource usage status of each micro-server instance pre-stored locally is updated according to the resource release information.
15. The resource management method according to any one of claims 9 to 14, It is characterized in that The resource management method further includes: Sending a registration request to the load balancing server, and establishing a connection relationship with the load balancing server according to the registration request; or, A deregistration request is sent to the load balancing server, and the connection relationship with the load balancing server is deregistered according to the deregistration request.
16. A resource management system, It is characterized in that The resource management system includes multiple micro servers, proxy servers corresponding to each micro server, and a load balancing server. The load balancing server is communicatively connected with each proxy server. The resource management system is used to execute the resource management method described in any one of claims 1 to 8.
17. A proxy server, It is characterized in that The method comprises a memory and a processor, wherein the memory stores a computer program, and the processor executes the resource management method according to any one of claims 9 to 15 when calling the computer program in the memory.
18. A storage medium for computer-readable storage, It is characterized in that The storage medium is used to store a computer program, and the computer program is loaded by a processor to execute the resource management method described in any one of claims 1 to 8, or the computer program is loaded by a processor to execute the resource management method described in any one of claims 9 to 15.
