Proxy load balancing and flow limiting method based on visual configuration

Abstract

The invention discloses an agent load balancing and flow limiting method based on visual configuration, and relates to the technical field of flow limiting methods. The agent load balancing and flow limiting method based on visual configuration comprises the following steps: step 1, a research and development person can input corresponding information on an agent account information page by newly adding agent account basic information to complete maintenance work on the agent account basic information; 2, all current proxy account information is clearly checked through a proxy information list, and corresponding proxy account information can be quickly inquired through search conditions; 3, for the configured proxy account information, setting the binding relationship of heap use scenes through a proxy account strategy configuration page, and supporting the binding of a plurality of proxy account relationships in the same scene; 4, after the binding relation between the use scene and the proxy account is configured, query can be carried out through the search condition of the list page.

Description

Technical Field

[0001] The present invention relates to the technical field of current limiting methods, and in particular to a proxy load balancing and current limiting method based on visual configuration. Background Art

[0002] There are many types of proxy suppliers and self-built proxy pools currently on the market, but their actual use in actual scenarios generally involves the introduction of multiple suppliers or self-built proxy pools. The use and restrictions of proxies are not convenient and accurate enough, the internal management is not intuitive enough, the success rate when using proxy requests is not high, and the R&D rate is low. Summary of the invention

[0003] The purpose of the present invention is to solve at least one of the technical problems existing in the prior art, and to provide a method for proxy load balancing and current limiting based on visual configuration, which can solve the problem of low R&D efficiency.

[0004] To achieve the above object, the present invention provides the following technical solution: a method for proxy load balancing and current limiting based on visual configuration, step 1: R&D personnel can complete the maintenance of the basic information of the proxy account by adding basic information of the proxy account on the proxy account information page and entering corresponding information;

[0005] Step 2: Through the agent information list, you can clearly view all the current agent account information, and quickly query the corresponding agent account information through search conditions;

[0006] Step 3: For the configured proxy account information, you can use the proxy account policy configuration page to set the binding relationship for the heap usage scenario. Multiple proxy account relationships can be bound in the same scenario.

[0007] Step 4: After configuring the binding relationship between the usage scenario and the proxy account, you can search through the search conditions on the list page. If necessary, you can edit and adjust the bound policy relationship in the operation bar. The adjusted relationship takes effect immediately and can be obtained through the proxy account API.

[0008] Step 5: The user passes Figure 5 , 6 The API provided by the proxy center is used to obtain the corresponding proxy account for use. The core parameters on the API are: usage scenario number dimensionNo, distribution type distributeType, whether to use session isSession, session strategy (exclusive or not) strategyType, and session duration sessionSeconds.

[0009] Preferably, the corresponding information in step 1 includes account password, proxy URL, QPS, IP type, and validity date.

[0010] Preferably, in step 2, the proxy account information can be maintained by adding, deleting, modifying, checking, and activating / deactivating through the operation bar.

[0011] Preferably, in step 5, if the acquisition of the proxy at a certain moment exceeds the flow control and causes a failure, the user can initiate a retry as needed and call the API again to obtain it.

[0012] Preferably, the basic information of the proxy account is maintained through the proxy information page at the web layer, and the usage scenario and the binding policy of the proxy account are maintained through the proxy policy page; the basic information and policy information are stored inside the proxy center, and then the proxy account user is called by exposing the proxy acquisition API. In acquiring the proxy account, the proxy account load balancing, flow control restriction processing and session management are performed according to the binding policy; the proxy account user obtains the proxy account through the API and retries if the acquisition fails.

[0013] Preferably, the proxy center abstracts a total pool (the sum of Qps of all proxy accounts) at the upper layer, and builds a sub-pool mechanism for each proxy account in a one-to-one manner at the next layer to achieve the effect of load balancing; the proxy account is obtained by routing to the specified proxy pool through the binding strategy, and a second-based counter is added to each proxy account pool to control the obtained Qps rate to achieve the effect of flow control; if the user needs to use the same proxy account in the same requested session, the session persistence function is enabled when calling the API.

[0014] Compared with the prior art, the present invention has the following beneficial effects:

[0015] (1) The method of proxy load balancing and current limiting based on visual configuration, when using the proxy account, only the basic information of the proxy account including account password, URL, QPS concurrent number, etc. need to be manually configured on the page in advance to complete the maintenance of the proxy information. After the usage scenario and the corresponding proxy account are bound through the proxy policy page, the corresponding proxy account information can be obtained by calling the API when in use. This can greatly improve the management of the proxy account information. When it comes to the need to change the proxy account, only the policy adjustment and modification on the page can be made to quickly switch the proxy account to be used, which can greatly improve the R&D efficiency of R&D personnel, and can also more intuitively and clearly display the usage relationship between the usage scenario and the proxy account. In addition, the interval of automatically updating the underlying IP pool of the proxy account can be managed on the interface to improve the quality of the proxy account. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The present invention is further described below in conjunction with the accompanying drawings and embodiments:

[0017] Figure 1 This is a system functional architecture diagram of the proxy load balancing and current limiting method based on visual configuration of the present invention;

[0018] Figure 2 This is a core flow chart of the proxy load balancing and current limiting method based on visual configuration of the present invention;

[0019] Figure 3 A schematic diagram of newly added proxy account information of the proxy load balancing and current limiting method based on visual configuration of the present invention;

[0020] Figure 4 A schematic diagram of newly added proxy account information of the proxy load balancing and current limiting method based on visual configuration of the present invention;

[0021] Figure 5 It is a schematic diagram of the account information list interface of the proxy load balancing and current limiting method based on visual configuration of the present invention;

[0022] Figure 6 It is a schematic diagram of the proxy strategy interface of the new proxy load balancing and current limiting method based on visual configuration of the present invention;

[0023] Figure 7 A schematic diagram of a proxy strategy information list of a proxy load balancing and current limiting method based on visual configuration of the present invention;

[0024] Figure 8 It is a schematic diagram of the API code for obtaining proxy information of the method for proxy load balancing and current limiting based on visual configuration of the present invention;

[0025] Fig. 9 A schematic diagram of the code for setting a session strategy for obtaining an agent account API in the method for agent load balancing and current limiting based on visual configuration of the present invention. DETAILED DESCRIPTION

[0026] This section will describe in detail the specific embodiments of the present invention. The preferred embodiments of the present invention are shown in the accompanying drawings. The purpose of the accompanying drawings is to supplement the description of the text part of the specification with graphics, so that people can intuitively and vividly understand each technical feature and the overall technical solution of the present invention, but it cannot be understood as a limitation on the scope of protection of the present invention.

[0027] In the description of the present invention, it should be understood that descriptions involving orientations, such as up, down, front, back, left, right, etc., and orientations or positional relationships indicated are based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present invention.

[0028] In the description of the present invention, "greater than", "less than", "exceed" etc. are understood as not including the number itself, and "above", "below", "within" etc. are understood as including the number itself. If there is a description of "first" or "second", it is only used for the purpose of distinguishing technical features, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features.

[0029] In the description of the present invention, unless otherwise clearly defined, terms such as setting, installing, connecting, etc. should be understood in a broad sense, and technicians in the relevant technical field can reasonably determine the specific meanings of the above terms in the present invention based on the specific content of the technical solution.

[0030] See also Figure 3-9 The present invention provides a technical solution: a method for proxy load balancing and current limiting based on visual configuration:

[0031] Step 1: R&D personnel can complete the maintenance of the basic information of the proxy account by adding the basic information of the proxy account on the proxy account information page and entering the corresponding information: account password, proxy URL, QPS, IP type, expiration date, etc.;

[0032] Step 2: Through the proxy information list, you can clearly view all the current proxy account information. You can quickly query the corresponding proxy account information through the search conditions, and you can also add, delete, modify, maintain and activate / deactivate the proxy account information through the operation bar;

[0033] Step 3: For the configured proxy account information, you can use the proxy account policy configuration page to set the binding relationship for the heap usage scenario. Multiple proxy account relationships can be bound in the same scenario.

[0034] Step 4: After configuring the binding relationship between the usage scenario and the proxy account, you can search through the search conditions on the list page. If necessary, you can edit and adjust the bound policy relationship in the operation bar. The adjusted relationship takes effect immediately and can be obtained through the proxy account API.

[0035] Step 5: The user passes Figure 5 , 6The API provided by the proxy center is used to obtain the corresponding proxy account for use. The core parameters of the API are: usage scenario number dimensionNo, distribution type distributeType, whether to use session isSession, session strategy (exclusive or not) strategyType, and session duration sessionSeconds. If the proxy acquisition fails at a certain moment due to flow control, the user can initiate a retry as needed and call the API again to obtain it.

[0036] For further information, see Figure 1 In the web layer, the basic information of the proxy account is maintained through the proxy information page, and then the usage scenarios and binding policies of the proxy account are maintained through the proxy policy page; the basic information and policy information will be stored inside the proxy center, and then the proxy account user will be called by exposing the proxy acquisition API. In acquiring the proxy account, the proxy account will be load balanced, flow control and limit processing and session management will be performed according to the binding policy; the proxy account user obtains the proxy account through the API and retries if the acquisition fails.

[0037] For further information, see Figure 2 The proxy center abstracts a total pool (the sum of Qps of all proxy accounts) at the upper layer, and builds a sub-pool mechanism for each proxy account in a one-to-one manner at the next layer to achieve the effect of load balancing; the proxy account is obtained by routing to the specified proxy pool through the binding strategy, and a second-based counter is added to each proxy account pool to control the obtained Qps rate to achieve the effect of flow control; if the user needs to use the same proxy account in the same requested session, the session persistence function is enabled when calling the API.

[0038] Furthermore, when using a proxy account, you only need to manually configure the basic information of the proxy account on the page in advance, including the account password, URL, Qps concurrent number, etc., to complete the maintenance of the proxy information. After establishing a binding relationship between the usage scenario and the corresponding proxy account through the proxy policy page, you can get the corresponding proxy account information by calling the API when using it. This can greatly improve the management of proxy account information. When it comes to the need to change the proxy account, you only need to adjust and modify the policy on the page to quickly switch the proxy account to use, which can greatly improve the R&D efficiency of R&D personnel, and can also more intuitively and clearly display the relationship between the usage scenario and the proxy account. In addition, the interface can also manage the interval for the proxy account to automatically update the underlying IP pool to provide the quality of the proxy account.

[0039] The embodiments of the present invention are described in detail above with reference to the accompanying drawings. However, the present invention is not limited to the above embodiments. Various changes can be made within the knowledge scope of ordinary technicians in the technical field without departing from the purpose of the present invention.

Claims

1. A method for proxy load balancing and current limiting based on visual configuration, characterized in that: Step 1: R&D personnel can complete the maintenance of the basic information of the agent account by adding the basic information of the agent account on the agent account information page and entering the corresponding information; Step 2: Through the agent information list, you can clearly view all the current agent account information, and quickly query the corresponding agent account information through search conditions; Step 3: For the configured proxy account information, you can use the proxy account policy configuration page to set the binding relationship for the heap usage scenario. Multiple proxy account relationships can be bound in the same scenario. Step 4: After configuring the binding relationship between the usage scenario and the proxy account, you can search through the search conditions on the list page. If necessary, you can edit and adjust the bound policy relationship in the operation bar. The adjusted relationship takes effect immediately and can be obtained through the proxy account API. Step 5: The user obtains the corresponding proxy account through the API provided by the proxy center in Figures 5 and 6. The core parameters on the API are: usage scenario number dimensionNo, distribution type distributeType, whether to use session isSession, session strategy (exclusive or not) strategyType, and session duration sessionSeconds.

2. The method for proxy load balancing and current limiting based on visual configuration according to claim 1 is characterized in that: The corresponding information in step 1 includes account password, proxy URL, QPS, IP type, and validity date.

3. The method for proxy load balancing and current limiting based on visual configuration according to claim 1 is characterized in that: In step 2, the proxy account information can be added, deleted, modified, checked, maintained, and enabled / disabled through the operation bar.

4. The method for proxy load balancing and current limiting based on visual configuration according to claim 1 is characterized in that: In step 5, if the acquisition of the proxy exceeds the flow control at a certain moment and causes a failure, the user can initiate a retry as needed and call the API again to obtain it.

5. The method for proxy load balancing and current limiting based on visual configuration according to claim 1 is characterized in that: In the web layer, the basic information of the proxy account is maintained through the proxy information page, and the usage scenario and the binding policy of the proxy account are maintained through the proxy policy page; the basic information and policy information will be stored inside the proxy center, and then the proxy account user will be called by exposing the proxy acquisition API. In the proxy account acquisition, the proxy account will be loaded and balanced, flow control and restriction will be processed, and session management will be performed according to the binding policy; The user of the proxy account obtains the proxy account through the API and retries if the acquisition fails.

6. The method for proxy load balancing and current limiting based on visual configuration according to claim 1 is characterized in that: The proxy center abstracts a total pool (the sum of Qps of all proxy accounts) at the upper layer, and builds a sub-pool mechanism for each proxy account in a one-to-one manner at the next layer to achieve the effect of load balancing; the proxy account is obtained from the specified proxy pool through the routing of the binding strategy, and a second counter is added to each proxy account pool to control the Qps rate obtained to achieve the effect of flow control; If the user needs to use the same proxy account within the same request session, enable the session persistence function when calling the API.

Images