CN110868465A - Load balancing system and method for container cloud - Google Patents
Load balancing system and method for container cloud Download PDFInfo
- Publication number
- CN110868465A CN110868465A CN201911107718.XA CN201911107718A CN110868465A CN 110868465 A CN110868465 A CN 110868465A CN 201911107718 A CN201911107718 A CN 201911107718A CN 110868465 A CN110868465 A CN 110868465A
- Authority
- CN
- China
- Prior art keywords
- algorithm
- load balancing
- access request
- service module
- address information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1023—Server selection for load balancing based on a hash applied to IP addresses or costs
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Abstract
The invention discloses a load balancing system and method of a container cloud, wherein the system comprises the following steps: the system comprises a request service module, an algorithm service module and a headless service module, wherein the headless service module is used for being connected with each container application instance Pod in a container application cluster, and a plurality of load balancing algorithms are preset in the algorithm service module; the algorithm service module is used for acquiring IP address information of each Pod in the container application cluster through the headless server after receiving the access request, and sending the access request to the pods corresponding to the IP address information according to a target load balancing algorithm, wherein the target load balancing algorithm is determined from various load balancing algorithms according to algorithm selection information; in the using process, a corresponding load balancing algorithm can be selected according to the needs of a user, the use is more flexible, and the user requirements can be met.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a load balancing system and method of a container cloud.
Background
The container technology is a key product of cloud computing development in recent years and has a good development trend. At present, container cloud platforms are mostly built on the basis of docker and kubernets, and kubernets are the open source technology which focuses most and uses most currently. Kubernetes is also called K8s as an application-centric enterprise-level application cluster full-life-cycle management system based on docker technology, native micro-service support, deep engagement with DevOps engineering concept, and K8s provides functions of service registration, load balancing, service deployment and operation, service rolling upgrade, online capacity expansion and contraction, resource scheduling, resource quota management, and the like for container application.
Load balancing refers to distributing an external access request to a certain server running an application according to a certain algorithm, so that the capability of rapidly acquiring data is provided, and the problem of massive concurrent access service is solved. Although K8s provides rich functions, it is not selectable for load balancing, and only uses the default Round Robin method, so that the user's options are limited.
Therefore, how to provide a system and a method for load balancing of a container cloud to solve the above technical problems is a problem that needs to be solved by those skilled in the art.
Disclosure of Invention
The embodiment of the invention aims to provide a load balancing system and method of a container cloud, which can select a corresponding load balancing algorithm according to the needs of a user in the using process, are more flexible to use and are beneficial to meeting the needs of the user.
In order to solve the above technical problem, an embodiment of the present invention provides a load balancing system for a container cloud, including: the system comprises a request service module, an algorithm service module and a headless service module, wherein the headless service module is used for being connected with each container application instance Pod in a container application cluster, and a plurality of load balancing algorithms are preset in the algorithm service module, wherein:
the request service module is used for receiving an access request and sending the access request to the algorithm service module;
the algorithm service module is used for acquiring IP address information of each Pod in the container application cluster through the headless service module after receiving the access request, and sending the access request to the pods corresponding to the IP address information according to a target load balancing algorithm, wherein the target load balancing algorithm is determined from various load balancing algorithms according to algorithm selection information.
Optionally, the request service module includes an external service unit, and the access request includes an external access request;
and the external service unit is used for receiving an external access request sent by an external terminal and sending the external access request to the algorithm service module.
Optionally, the request service module further includes an internal service unit, and the access request further includes an external access request;
the internal service unit is used for receiving an internal access request sent by a Pod in the system and sending the internal access request to the algorithm service module.
Optionally, the IP address information of each Pod is presented in a form of a list.
Optionally, the algorithm service module is configured to determine the target load balancing algorithm from the load balancing algorithms according to algorithm type information input by a user.
Optionally, any two or more of a polling algorithm, a random algorithm, a ring hash algorithm and a minimum request algorithm are preset in the algorithm service module;
when the target load balancing algorithm polls the algorithm, the process of sending the access request to the Pod corresponding to each piece of the IP address information according to the target load balancing algorithm is as follows:
sending the access request to the Pod corresponding to each IP address information in turn;
when the target load balancing algorithm is a random algorithm, the process of sending the access request to the Pod corresponding to each piece of the IP address information according to the target load balancing algorithm is as follows:
randomly selecting one piece of IP address information from the IP address information, and sending the access request to a Pod corresponding to the selected IP address information;
when the target load balancing algorithm is a ring hash algorithm, the access request comprises a sending source IP address; the process of sending the access request to the Pod corresponding to each piece of the IP address information according to the target load balancing algorithm is as follows:
calculating a hash value corresponding to the IP address of the sending source through a hash function, matching corresponding target IP address information from a hash ring according to the hash value, and sending the access request to a Pod corresponding to the target IP address information;
when the target load balancing algorithm is the minimum request algorithm, the process of sending the access request to the Pod corresponding to each piece of the IP address information according to the target load balancing algorithm is as follows:
and selecting a target Pod with the minimum number of received access requests in a preset time length from the pods corresponding to the IP address information, and sending the access requests to the target pods according to the IP address information corresponding to the target pods.
Optionally, the headless service module is established in the following process:
establishing service, and setting a corresponding label selector to establish connection with each Pod in the container application cluster;
and setting the cluster IP of the service to be None to form a headless service module.
The embodiment of the invention also correspondingly provides a load balancing method of the container cloud, which comprises the following steps:
receiving an access request sent by an access service, and acquiring IP address information of each Pod in a container application cluster;
determining a target load balancing algorithm from preset load balancing algorithms according to algorithm selection information;
and sending the access request to the Pod corresponding to each IP address information by adopting the target load balancing algorithm.
The embodiment of the invention provides a load balancing system and method of a container cloud, wherein the system comprises the following steps: the method comprises a request service module, an algorithm service module and a headless service module, wherein a plurality of load balancing algorithms are preset in the algorithm service module, after the algorithm service module receives an access request through the request service module, the headless service module can acquire IP address information of each Pod in a container application cluster connected with the headless service module, and then the target load balancing algorithm selected according to algorithm selection information is adopted to send the access request to the pods corresponding to the IP address information, so that load balancing is achieved. The method and the device can select the corresponding load balancing algorithm according to the user requirements in the using process, are more flexible to use, and are beneficial to meeting the user requirements.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed in the prior art and the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
Fig. 1 is a block diagram of a load balancing system of a container cloud according to an embodiment of the present invention;
fig. 2 is a block diagram of a load balancing system of another container cloud according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a load balancing system of a container cloud according to an embodiment of the present invention;
fig. 4 is a schematic flowchart of a load balancing method for a container cloud according to an embodiment of the present invention.
Detailed Description
The embodiment of the invention provides a load balancing system and method of a container cloud, which can select a corresponding load balancing algorithm according to the needs of a user in the using process, are more flexible to use and are beneficial to meeting the requirements of the user.
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, fig. 1 is a block diagram of a load balancing system of a container cloud according to an embodiment of the present invention.
In order to solve the above technical problem, an embodiment of the present invention provides a load balancing system for a container cloud, including: the system comprises a request service module 1, an algorithm service module 2 and a headless service module 3, wherein the headless service module 3 is used for being connected with each container application instance Pod in a container application cluster, and a plurality of load balancing algorithms are preset in the algorithm service module 2, wherein:
the request service module 1 is used for receiving the access request and sending the access request to the algorithm service module 2;
and the algorithm service module 2 is used for acquiring the IP address information of each Pod in the container application cluster through the headless service module 3 after receiving the access request, and sending the access request to the Pod corresponding to each IP address information according to a target load balancing algorithm, wherein the target load balancing algorithm is determined from various load balancing algorithms according to algorithm selection information.
Specifically, a headless service module 3 (hedlemessservice) is arranged in the container cloud load balancing system in this embodiment, and the headless service module 3 is connected to each Pod in the container application cluster at the rear end, and can acquire IP address information of each Pod in the container application cluster; the algorithm service module 2(Custom Proxy service) is provided with a plurality of load balancing algorithms in advance, a user can select the algorithms according to needs, the request service module 1 can access the algorithm service module 2, that is, when the request service module 1 receives an access request, the access request can be sent to the algorithm service module 2, after receiving the access request, the algorithm service module 2 can obtain the IP address information of each Pod in the rear-end container application cluster through the headless service module 3, and can determine a target load balancing algorithm meeting the requirements from each preset load balancing algorithm according to algorithm selection information, and then send the access request to the Pod corresponding to each IP address information according to the specific implementation mode of the target load balancing algorithm, so that load balancing is achieved. The algorithm selection information may be preset and written into the algorithm service module 2 according to user requirements, and may specifically be determined according to actual needs, which is not particularly limited in the present application.
In addition, it should be further described that, during setting, the headless service module 3 in this embodiment establishes a service and sets a corresponding tag selector (selector) to establish a connection with each Pod in the container application cluster; the cluster IP of the service is set to None to form a headless service module.
Specifically, Service is a core concept of K8s, a uniform entry address can be provided for a group of container applications with the same function by creating Service, a relationship can be established between a tag selector of Service and each Pod in a container application cluster at the back end by setting the ClusterIP of Service to None, that is, without setting ClusterIP, the Service is a headless Service, so that a headless Service module is formed, and the headless Service module 3 can return IP address information of each Pod in the container application cluster at the back end to a calling end (that is, to the algorithm Service module 2) through labelselection.
In addition, it should be further noted that the IP address information of each Pod in this embodiment may be specifically presented in a form of a list, that is, the algorithm service module 2 may obtain, through the headless service module 3, a Pod list of the container application cluster, where the list includes the IP address information of each relevant Pod.
Further, referring to fig. 2 and fig. 3, the request service module 1 in the present embodiment includes an external service unit 11, and the access request includes an external access request;
and the external service unit 11 is used for receiving an external access request sent by an external terminal and sending the external access request to the algorithm service module 2.
Specifically, the request service module 1 includes an external service unit 11 (such as external service in fig. 3), and the external service unit 11 can receive an external access request sent by an external terminal and send the external access request to the algorithm service module 2, where the algorithm service module 2 can allow the external service unit 11 to access the algorithm service module 2 by creating a node port/load balance service or by defining an ingress policy. After receiving the external access request, the algorithm service module 2 obtains IP address information of each Pod (e.g., Pod-1, Pod-2 … Pod-n, etc. in fig. 3) in the container application cluster through the headless server 3, and then sends the external access request to the Pod corresponding to each IP address information according to the specific implementation manner of the target load balancing algorithm, thereby implementing load balancing of the external access request.
Furthermore, the request service module 1 may further include an internal service unit 12, and the access request further includes an external access request;
and the internal service unit 12 is configured to receive an internal access request sent by a Pod inside the system, and send the internal access request to the algorithm service module 2.
Specifically, the internal service unit 12 (e.g., the ClusterIP service in fig. 3) in this embodiment is configured to receive an internal access request sent by an internal Pod (e.g., PodA, PodB, and PodC in fig. 3), and send the internal access request to the algorithm service module 2, and after receiving the internal access request, the algorithm service module 2 also obtains, through the headless service module 3, IP address information of each Pod in the container application cluster, and sends the internal access request to the Pod corresponding to each IP address information according to a specific implementation manner of the target load balancing algorithm.
Optionally, the algorithm service module 2 is configured to determine a target load balancing algorithm from the load balancing algorithms according to algorithm type information input by the user.
That is, the algorithm type information in this embodiment may be input by a user, that is, each load balancing algorithm preset in the algorithm service module 2 has its own type, so that the user may input corresponding algorithm type information according to its own requirement, specifically, the user may input parameter information, and determine corresponding algorithm type information according to the parameter information input by the user, and the algorithm service module 2 may determine a target load balancing algorithm from each load balancing algorithm according to the algorithm type information, so as to send a received external request or internal request to the Pod corresponding to each IP address information according to the target load balancing algorithm. Of course, in practical application, not only the algorithm type information but also other identification information corresponding to each load balancing algorithm may be input, which implementation manner is specifically adopted.
The load balancing algorithm preset in the algorithm service module 2 may include any two or more of a polling algorithm, a random algorithm, a ring hash algorithm and a minimum request algorithm; for example, the container application cluster includes X, Y, Z three Pod, and when the algorithm service module 2 receives five access requests a, b, c, d, and e in sequence, the specific implementation process of using different target load balancing algorithms is as follows:
when the target load balancing algorithm polls the algorithm, the process of sending the access request to the Pod corresponding to each IP address information according to the target load balancing algorithm is as follows:
sending the access request to the Pod corresponding to each IP address information in turn;
specifically, the algorithm service module 2 sends five access requests a, b, c, d and e to X, Y, Z Pod in turn according to the polling algorithm, that is, the access request a is sent to X through the IP address information corresponding to X in sequence, the access request b is sent to Y through the IP address information corresponding to Y, the access request c is sent to Z through the IP address information corresponding to Z, the access request d is sent to X through the IP address information corresponding to X, and the access request e is sent to Y through the IP address information corresponding to Y.
When the target load balancing algorithm is a random algorithm, the process of sending the access request to the Pod corresponding to each piece of IP address information according to the target load balancing algorithm is as follows:
randomly selecting one piece of IP address information from the IP address information, and sending an access request to a Pod corresponding to the selected IP address information;
specifically, for each currently received access request, one piece of IP address information is randomly selected, and then the access request is sent to the corresponding Pod according to the IP address information.
When the target load balancing algorithm is a ring hash algorithm, the access request comprises a sending source IP address; the process of sending the access request to the Pod corresponding to each IP address information according to the target load balancing algorithm is as follows:
calculating a hash value corresponding to the IP address of the sending source through a hash function, matching corresponding target IP address information from a hash ring according to the hash value, and sending an access request to a Pod corresponding to the target IP address information;
specifically, the access information includes a transmission source IP address, that is, an IP address of a terminal or an internal Pod that transmits the access information, and a hash function is used to calculate a corresponding hash value according to the transmission source IP address, because the IP address information of each Pod in each container application cluster corresponds to a position, that is, a value, on a hash ring, corresponding destination IP address information can be matched from the hash ring according to the calculated hash value, if there is no corresponding IP address information, one can be randomly assigned as destination IP address information, and then the access request is sent to the Pod corresponding to the destination IP address information. That is, for the same transmission source (i.e., the same access terminal), the corresponding access request is always sent to the same Pod.
When the target load balancing algorithm is the minimum request algorithm, the process of sending the access request to the Pod corresponding to each IP address information according to the target load balancing algorithm is as follows:
and selecting a target Pod with the least number of received access requests in a preset time length from the pods corresponding to the IP address information, and sending the access requests to the target pods according to the IP address information corresponding to the target pods.
Specifically, the number of access requests received by each Pod within a preset time period (for example, 12 hours) may be counted, and the currently received access request is sent to the Pod with the smallest number of currently received access requests. If the number of the access requests received by each Pod is the same, one Pod can be randomly selected to send the access request.
It can be seen that, a plurality of load balancing algorithms are preset in the algorithm service module in the application, and after the algorithm service module receives an access request through the request service module, the headless service module can acquire the IP address information of each Pod in the container application cluster connected with the headless service module, and then the target load balancing algorithm selected according to the algorithm selection information is adopted to send the access request to the Pod corresponding to each IP address information, thereby realizing load balancing. The method and the device can select the corresponding load balancing algorithm according to the user requirements in the using process, are more flexible to use, and are beneficial to meeting the user requirements.
On the basis of the above embodiments, the embodiments of the present invention further provide a load balancing method for a container cloud, where the method includes:
s110: receiving an access request sent by an access service, and acquiring IP address information of each Pod in a container application cluster;
s120: determining a target load balancing algorithm from preset load balancing algorithms according to algorithm selection information;
s130: and sending the access request to the Pod corresponding to each IP address information by adopting a target load balancing algorithm.
It should be noted that the method for load balancing of a container cloud in this embodiment has the same beneficial effects as the load balancing system of a container cloud provided in the above embodiment.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (8)
1. A load balancing system for a container cloud, comprising: the system comprises a request service module, an algorithm service module and a headless service module, wherein the headless service module is used for being connected with each container application instance Pod in a container application cluster, and a plurality of load balancing algorithms are preset in the algorithm service module, wherein:
the request service module is used for receiving an access request and sending the access request to the algorithm service module;
the algorithm service module is used for acquiring IP address information of each Pod in the container application cluster through the headless service module after receiving the access request, and sending the access request to the pods corresponding to the IP address information according to a target load balancing algorithm, wherein the target load balancing algorithm is determined from various load balancing algorithms according to algorithm selection information.
2. The load balancing system of a container cloud according to claim 1, wherein the request service module includes an external service unit, and the access request includes an external access request;
and the external service unit is used for receiving an external access request sent by an external terminal and sending the external access request to the algorithm service module.
3. The load balancing system of a container cloud according to claim 2, wherein the request service module further comprises an internal service unit, and the access request further comprises an internal access request;
the internal service unit is used for receiving an internal access request sent by a Pod in the system and sending the internal access request to the algorithm service module.
4. The load balancing system of a container cloud according to claim 1, wherein the IP address information of each Pod is presented in a list.
5. The load balancing system of the container cloud according to claim 1, wherein the algorithm service module is configured to determine the target load balancing algorithm from the load balancing algorithms according to algorithm type information input by a user.
6. The load balancing system of the container cloud according to any one of claims 1 to 4, wherein any two or more of a polling algorithm, a random algorithm, a ring hash algorithm, and a minimum request algorithm are preset in the algorithm service module;
when the target load balancing algorithm polls the algorithm, the process of sending the access request to the Pod corresponding to each piece of the IP address information according to the target load balancing algorithm is as follows:
sending the access request to the Pod corresponding to each IP address information in turn;
when the target load balancing algorithm is a random algorithm, the process of sending the access request to the Pod corresponding to each piece of the IP address information according to the target load balancing algorithm is as follows:
randomly selecting one piece of IP address information from the IP address information, and sending the access request to a Pod corresponding to the selected IP address information;
when the target load balancing algorithm is a ring hash algorithm, the access request comprises a sending source IP address; the process of sending the access request to the Pod corresponding to each piece of the IP address information according to the target load balancing algorithm is as follows:
calculating a hash value corresponding to the IP address of the sending source through a hash function, matching corresponding target IP address information from a hash ring according to the hash value, and sending the access request to a Pod corresponding to the target IP address information;
when the target load balancing algorithm is the minimum request algorithm, the process of sending the access request to the Pod corresponding to each piece of the IP address information according to the target load balancing algorithm is as follows:
and selecting a target Pod with the minimum number of received access requests in a preset time length from the pods corresponding to the IP address information, and sending the access requests to the target pods according to the IP address information corresponding to the target pods.
7. The load balancing system of the container cloud according to claim 1, wherein the headless service module is established by:
establishing service, and setting a corresponding label selector to establish connection with each Pod in the container application cluster;
and setting the cluster IP of the service to be None to form a headless service module.
8. A load balancing method of a container cloud is characterized by comprising the following steps:
receiving an access request sent by an access service, and acquiring IP address information of each Pod in a container application cluster;
determining a target load balancing algorithm from preset load balancing algorithms according to algorithm selection information;
and sending the access request to the Pod corresponding to each IP address information by adopting the target load balancing algorithm.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911107718.XA CN110868465A (en) | 2019-11-13 | 2019-11-13 | Load balancing system and method for container cloud |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911107718.XA CN110868465A (en) | 2019-11-13 | 2019-11-13 | Load balancing system and method for container cloud |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110868465A true CN110868465A (en) | 2020-03-06 |
Family
ID=69654578
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911107718.XA Pending CN110868465A (en) | 2019-11-13 | 2019-11-13 | Load balancing system and method for container cloud |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110868465A (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111431740A (en) * | 2020-03-16 | 2020-07-17 | 深信服科技股份有限公司 | Data transmission method, device, equipment and computer readable storage medium |
| CN111475289A (en) * | 2020-03-26 | 2020-07-31 | 北京世纪家天下科技发展有限公司 | Load balancing method and device |
| CN112256425A (en) * | 2020-10-19 | 2021-01-22 | 聚好看科技股份有限公司 | Load balancing method and system, computer cluster, information editing method and terminal |
| CN112822257A (en) * | 2020-12-31 | 2021-05-18 | 北京中交兴路信息科技有限公司 | Web service management system, method and storage medium |
| CN113079207A (en) * | 2021-03-26 | 2021-07-06 | 重庆紫光华山智安科技有限公司 | Method, system, terminal and medium for realizing high availability of port or network |
| CN113572838A (en) * | 2021-07-22 | 2021-10-29 | 北京金山云网络技术有限公司 | Network access method, device, equipment and medium based on Kubernetes |
| CN114338832A (en) * | 2021-12-17 | 2022-04-12 | 上海道客网络科技有限公司 | Network protocol conversion method and system of container cloud platform |
| CN114374696A (en) * | 2021-12-15 | 2022-04-19 | 深圳前海微众银行股份有限公司 | Container load balancing method, device, equipment and storage medium |
| CN114461303A (en) * | 2022-02-10 | 2022-05-10 | 京东科技信息技术有限公司 | Method and device for accessing cluster internal service |
| CN114500545A (en) * | 2022-01-24 | 2022-05-13 | 杭州博盾习言科技有限公司 | Network load balancing method and device suitable for container and electronic equipment |
| CN117395316A (en) * | 2023-12-11 | 2024-01-12 | 深圳万物安全科技有限公司 | Outlet flow management method, device and readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103929365A (en) * | 2014-03-25 | 2014-07-16 | 上海格尔软件股份有限公司 | Load balancing system and method suitable for a plurality of UDP services |
| CN103945000A (en) * | 2014-05-05 | 2014-07-23 | 安徽科大讯飞信息科技股份有限公司 | Load balance method and load balancer |
| CN104579996A (en) * | 2013-10-17 | 2015-04-29 | 中国电信股份有限公司 | Cluster load balancing method and system |
| CN105141541A (en) * | 2015-09-23 | 2015-12-09 | 浪潮(北京)电子信息产业有限公司 | Task-based dynamic load balancing scheduling method and device |
| CN107590001A (en) * | 2017-09-08 | 2018-01-16 | 北京京东尚科信息技术有限公司 | Load-balancing method and device, storage medium, electronic equipment |
-
2019
- 2019-11-13 CN CN201911107718.XA patent/CN110868465A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104579996A (en) * | 2013-10-17 | 2015-04-29 | 中国电信股份有限公司 | Cluster load balancing method and system |
| CN103929365A (en) * | 2014-03-25 | 2014-07-16 | 上海格尔软件股份有限公司 | Load balancing system and method suitable for a plurality of UDP services |
| CN103945000A (en) * | 2014-05-05 | 2014-07-23 | 安徽科大讯飞信息科技股份有限公司 | Load balance method and load balancer |
| CN105141541A (en) * | 2015-09-23 | 2015-12-09 | 浪潮(北京)电子信息产业有限公司 | Task-based dynamic load balancing scheduling method and device |
| CN107590001A (en) * | 2017-09-08 | 2018-01-16 | 北京京东尚科信息技术有限公司 | Load-balancing method and device, storage medium, electronic equipment |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111431740B (en) * | 2020-03-16 | 2023-07-14 | 深信服科技股份有限公司 | Data transmission method, device, equipment and computer readable storage medium |
| CN111431740A (en) * | 2020-03-16 | 2020-07-17 | 深信服科技股份有限公司 | Data transmission method, device, equipment and computer readable storage medium |
| CN111475289A (en) * | 2020-03-26 | 2020-07-31 | 北京世纪家天下科技发展有限公司 | Load balancing method and device |
| CN111475289B (en) * | 2020-03-26 | 2024-04-12 | 北京世纪家天下科技发展有限公司 | Load balancing method and device |
| CN112256425A (en) * | 2020-10-19 | 2021-01-22 | 聚好看科技股份有限公司 | Load balancing method and system, computer cluster, information editing method and terminal |
| WO2021120976A3 (en) * | 2020-10-19 | 2021-08-19 | 聚好看科技股份有限公司 | Load balance control method and server |
| CN112256425B (en) * | 2020-10-19 | 2023-10-20 | 聚好看科技股份有限公司 | Load balancing method and system, computer cluster, information editing method and terminal |
| CN112822257A (en) * | 2020-12-31 | 2021-05-18 | 北京中交兴路信息科技有限公司 | Web service management system, method and storage medium |
| CN112822257B (en) * | 2020-12-31 | 2023-07-25 | 北京中交兴路信息科技有限公司 | Web service management system, method and storage medium |
| CN113079207A (en) * | 2021-03-26 | 2021-07-06 | 重庆紫光华山智安科技有限公司 | Method, system, terminal and medium for realizing high availability of port or network |
| CN113572838A (en) * | 2021-07-22 | 2021-10-29 | 北京金山云网络技术有限公司 | Network access method, device, equipment and medium based on Kubernetes |
| CN114374696A (en) * | 2021-12-15 | 2022-04-19 | 深圳前海微众银行股份有限公司 | Container load balancing method, device, equipment and storage medium |
| CN114338832B (en) * | 2021-12-17 | 2023-08-18 | 上海道客网络科技有限公司 | Network protocol conversion method and system of container cloud platform |
| CN114338832A (en) * | 2021-12-17 | 2022-04-12 | 上海道客网络科技有限公司 | Network protocol conversion method and system of container cloud platform |
| CN114500545A (en) * | 2022-01-24 | 2022-05-13 | 杭州博盾习言科技有限公司 | Network load balancing method and device suitable for container and electronic equipment |
| CN114461303A (en) * | 2022-02-10 | 2022-05-10 | 京东科技信息技术有限公司 | Method and device for accessing cluster internal service |
| CN117395316A (en) * | 2023-12-11 | 2024-01-12 | 深圳万物安全科技有限公司 | Outlet flow management method, device and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110868465A (en) | Load balancing system and method for container cloud | |
| CN110049130B (en) | Service deployment and task scheduling method and device based on edge computing | |
| CN109246229B (en) | Method and device for distributing resource acquisition request | |
| CN107404541B (en) | Method and system for selecting neighbor node in peer-to-peer network transmission | |
| CN111163130B (en) | Network service system and data transmission method thereof | |
| CN106375471B (en) | Edge node determination method and device | |
| CN110519183B (en) | Node speed limiting method and device, electronic equipment and storage medium | |
| CN104601702B (en) | Cluster remote procedure calling (PRC) method and system | |
| CN106936925A (en) | Load-balancing method and system | |
| CN110336848B (en) | Scheduling method, scheduling system and scheduling equipment for access request | |
| CN110781015A (en) | Message queue distribution method, device, equipment and computer readable storage medium | |
| CN110933136A (en) | Service node selection method, device, equipment and readable storage medium | |
| CN113159910A (en) | Method, device and system for notification | |
| CN104796561A (en) | Agent distribution method, CTI (Computer Telephony Integration) equipment, terminal and agent distribution system | |
| EP2514173B1 (en) | Localization of peer to peer traffic | |
| CN110392119B (en) | Data transmission method and base station | |
| CN114338063A (en) | Message queue system, service processing method, and computer-readable storage medium | |
| CN111506443A (en) | Service calling method, device, equipment and storage medium | |
| CN109413117B (en) | Distributed data calculation method, device, server and computer storage medium | |
| CN114003337A (en) | Access request distribution method and device | |
| CN113014422B (en) | Method, device and equipment for scheduling content distribution network bandwidth | |
| CN114077483A (en) | Data resource scheduling method, server, system and storage medium | |
| CN109582829B (en) | Processing method, device, equipment and readable storage medium | |
| CN112087401A (en) | Method and device for realizing service quality in distributed storage | |
| CN116173495A (en) | Game progress distribution control method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200306 |
|
| RJ01 | Rejection of invention patent application after publication |