CN106657354A - Load balancing device and method - Google Patents

Load balancing device and method Download PDF

Info

Publication number
CN106657354A
CN106657354A CN201611245253.0A CN201611245253A CN106657354A CN 106657354 A CN106657354 A CN 106657354A CN 201611245253 A CN201611245253 A CN 201611245253A CN 106657354 A CN106657354 A CN 106657354A
Authority
CN
China
Prior art keywords
server
client
cluster
service
service framework
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
Application number
CN201611245253.0A
Other languages
Chinese (zh)
Inventor
林伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nubia Technology Co Ltd
Original Assignee
Nubia Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Nubia Technology Co Ltd filed Critical Nubia Technology Co Ltd
Priority to CN201611245253.0A priority Critical patent/CN106657354A/en
Publication of CN106657354A publication Critical patent/CN106657354A/en
Pending legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1001Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1001Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004Server selection for load balancing
    • H04L67/1014Server selection for load balancing based on the content of a request

Abstract

The invention provides a load balancing device and method. The method comprises the following steps: monitoring each server through a distributed service framework cluster, receiving an access request of a client, sending a server list of corresponding servers to the client according to the access request, and accessing the server list to the corresponding servers according to the server list. By implementation of the load balancing device and method provided by the invention, single-point faults can be reduced by the distributed service framework cluster, the cost necessary for maintenance is also reduced, in addition, the distributed service framework cluster requires no dynamic configuration of related information, and thus saving a lot of time.

Description

A kind of load balancing apparatus and method
Technical field
The present invention relates to communication technical field, more particularly, it relates to a kind of load balancing apparatus and method.
Background technology
What is commercially commonly used is to carry out the load balancing on software by NGNIX, larger when website When, the fractionation for often being serviced, the independent deployment of each service, and carrying out collaborative work by way of far call. As the continuation expansion and evolution of system, the quantity of server can increase, the quantity of corresponding NGNIX softwares also can increase, Its corresponding NGNIX deployment also can increase with configuration work, and this can cause maintenance cost to uprise, and the risk of Single Point of Faliure is also therewith Increase.
The content of the invention
The technical problem to be solved in the present invention is how to avoid carrying out bearing on software in prior art by NGNIX Carry balanced and caused maintenance cost height, the big problem of failure risk;For the technical problem, there is provided a kind of load balancing dress Put, including:
Monitoring module, for by each server of distributed service framework cluster monitoring;
Receiver module, for receiving the access request from client;
Sending module, for being sent the service list of the corresponding server according to the access request of the client To the client;
AM access module, for client to be accessed into the corresponding server according to the service list.
Optionally, also including Registering modules, for writing the registration of distributed service framework in each described server Code, and registered to distributed service framework cluster based on the registration code;After succeeding in registration, receive described distributed The monitoring of service framework cluster.
Optionally, the Registering modules are additionally operable to:In the startup of server, distribution is called by the registration code Formula service framework cluster, directly registers the server info of the server to the distributed service framework cluster.
Optionally, the monitoring module is additionally operable to:
The connection of each server and the distributed service framework cluster is monitored, and by described in connection failure Server is removed from the service list.
Optionally, also including cache module, for the service list to be cached into the client.
The present invention also provides a kind of load-balancing method, including:
By each server of distributed service framework cluster monitoring;
The access request from client is received, and will the corresponding server according to the access request of the client Service list send to the client;
The client is accessed by the corresponding server according to the service list.
Optionally, before described each server by distributed service framework cluster monitoring, also include:Each institute The registration code that distributed service framework is write in server is stated, and based on the registration code to distributed service framework cluster Registered;After succeeding in registration, receive the monitoring of the distributed service framework cluster.
Optionally, it is described registration is carried out to distributed service framework cluster based on the registration code to include:In the clothes When business device starts, distributed service framework cluster is called by the registration code, directly to the distributed service framework collection The server info of group's registration server.
Optionally, described each server by distributed service framework cluster monitoring includes:
The connection of each server and the distributed service framework cluster is monitored, and by described in connection failure Server is removed from the service list.
Optionally, the service list of the corresponding server is sent in the access request according to the client To the client, also include:The service list is cached into the client.
Beneficial effect
The invention provides a kind of load balancing apparatus and method, by each service of distributed service framework cluster monitoring Device, receives the access request from client, and the service list of corresponding server is sent to into client according to access request End, then accesses corresponding server according to service list by client.By the enforcement of the present invention, by Distributed Services frame Frame cluster can reduce Single Point of Faliure, while the cost needed for safeguarding is also reduced, additionally, distributed service framework cluster is not required to Relevant information is dynamically configured, the substantial amounts of time has been saved.
Description of the drawings
Below in conjunction with drawings and Examples, the invention will be further described, in accompanying drawing:
The load balancing apparatus composition schematic diagram that Fig. 1 is provided for first embodiment of the invention;
The schematic diagram by each server of zookeeper cluster monitorings that Fig. 2 is provided for first embodiment of the invention;
The load-balancing method flow chart that Fig. 3 is provided for second embodiment of the invention;
The load-balancing method flow chart that Fig. 4 is provided for third embodiment of the invention.
Specific embodiment
It should be appreciated that specific embodiment described herein is not intended to limit the present invention only to explain the present invention.
Embodiment one
Fig. 1 is a kind of load balancing apparatus composition schematic diagram that the present embodiment one is provided, and is specifically included:
Monitoring module 101, for by each server of distributed service framework (zookeeper) cluster monitoring;
Receiver module 102, for receiving the access request from client;
Sending module 103, for the service list of corresponding server to be sent into client according to the access request of client End;
AM access module 104, for client to be accessed into corresponding server according to service list.
Zookeeper is one distributed, the distributed application program coordination service of open source code, and it is one to divide Cloth application provide Consistency service device software, there is provided function include but is not limited to:Configuring maintenance, domain name service, distribution Formula is synchronous, organize service etc..By taking configuring maintenance as an example, when one group of code is applied to multiple servers, due to each server Ip addresses, interface etc. difference, actual disposition file is not quite similar, then can direct root by zookeeper clusters Configuration file is write according to different servers, without the need for the corresponding configuration file of another one write.
In the present embodiment, by each server of zookeeper cluster monitorings, i.e., using zookeeper and each clothes Business device is connected, and monitors the current state of each server, including ruuning situation, ip addresses, the port information of server etc., Wherein, the ruuning situation of server includes normal operation and connection failure etc., when between certain server and zookeeper not Reachable, deadlock or other reasonses cannot be connected, then may think that the service fault that the server occurs.
In the present embodiment, in order that zookeeper clusters can monitor each server, optionally, can also include Module 105 is built, for building the relevant environment of zookeeper clusters, and the kit of correlation is downloaded.That is, first, Zookeeper clusters are set up, related hardware information are set, and write the information such as corresponding software code, it is ensured that Zookeeper clusters being successfully established and normally run.
In addition, it can include Registering modules 106, for writing the registration code of zookeeper in each server, And registered to zookeeper clusters based on registration code;After succeeding in registration, the monitoring of zookeeper clusters is received.In order to Make zookeeper monitor corresponding server, need to be registered each server to zookeeper;Registration process can be with By user manually carrying out, it is also possible to by writing registration code in each server, i.e., in the application of each server Registration code is write in program, is allowed after program self-starting and is called the registration code automatically to carry out correlation to zookeeper clusters Registration action, i.e. Registering modules 106 can be also used for:In startup of server, zookeeper collection is called by registration code Group, directly to the server info of zookeeper cluster registrar.Server info can include the ip ground of server Location, port etc. information.
After succeeding in registration, it is meant that connection is had built up between server and zookeeper, while also implying that server Under monitoring already at zookeeper clusters, zookeeper clusters with real-time monitoring and can judge connected server State, the ip addresses and the corresponding service list of port information generation according to server.Fig. 2 is refer to, Fig. 2 shows and passes through The schematic diagram of zookeeper cluster monitorings each servers.
Service list can at least provide the ip address informations of corresponding server, can also include other additional letters Breath, such as priority information of ip addresses of the server etc., when client access server the priority is may be referred to Information is come the server needed for accessing.
Corresponding server should be the server of normal work in service list, in the present embodiment, monitoring module 101 Can be also used for:The connection of each server and zookeeper clusters is monitored, and by the server of connection failure from service Remove in list.When certain server because unreachable, deadlock or a variety of other reasonses cause the connection and zookeeper between to be lost Lose, now the server is considered failed server, can be by the relevant information of the server in service list Remove.Service list now comprises only the information of other normal servers of connection, so that client is receiving service Required server can be normally accessed after list, without there is having accessed the server of failure and caused other problemses.
Then, there is inaccessible situation between server and zookeeper, also have between zookeeper and server Recover the situation of connection;When connection is recovered between server and zookeeper clusters, then the server can be continued to add Into service list.
In the present embodiment, cache module 107 can also be included, for service list to be cached into client.Client End for the convenience of subsequent treatment, service list is cached, then be subsequently intended to access after service list is received During corresponding server, without the need for initiating access request, directly corresponding server can be accessed according to the service list of caching.And If service list there occurs change, such as certain server deadlock is offline, or has newly increased server, zookeeper collection Group can automatically notify that the client reacquires again service list, at the same time, then can move the service list of caching Remove.
Present embodiments provide a kind of load balancing apparatus, including monitoring module, receiver module, sending module, access mould Block, by each server of zookeeper cluster monitorings, receives the access request from client, and will according to access request The service list of corresponding server is sent to client, then client is accessed into corresponding server according to service list. By the enforcement of the present embodiment, Single Point of Faliure can be reduced by zookeeper clusters, at the same also reduce safeguard needed for into This, additionally, zookeeper clusters need not dynamically configure relevant information, has saved the substantial amounts of time.
Embodiment two
Fig. 3 is a kind of load-balancing method flow chart that the present embodiment two is provided, and is specifically included:
S301, by each server of zookeeper cluster monitorings;
S302, access request from client is received, and according to the access request of client by corresponding server Service list sends client;
S303, client is accessed by corresponding server according to service list.
Zookeeper is one distributed, the distributed application program coordination service of open source code, and it is one to divide Cloth application provide Consistency service device software, there is provided function include but is not limited to:Configuring maintenance, domain name service, distribution Formula is synchronous, organize service etc..By taking configuring maintenance as an example, when one group of code is applied to multiple servers, due to each server Ip addresses, interface etc. difference, actual disposition file is not quite similar, then can direct root by zookeeper clusters Configuration file is write according to different servers, without the need for the corresponding configuration file of another one write.
In the present embodiment, by each server of zookeeper cluster monitorings, i.e., using zookeeper and each clothes Business device is connected, and monitors the current state of each server, including ruuning situation, ip addresses, the port information of server etc., Wherein, the ruuning situation of server includes normal operation and connection failure etc., when between certain server and zookeeper not Reachable, deadlock or other reasonses cannot be connected, then may think that the service fault that the server occurs.
In the present embodiment, in order that zookeeper clusters can monitor each server, optionally, passing through Before zookeeper cluster monitorings each servers, can also include:The relevant environment of zookeeper clusters is built, and is downloaded Related kit.That is, first, zookeeper clusters are set up, related hardware information is set, and write The information such as corresponding software code, it is ensured that zookeeper clusters being successfully established and normally running.
Additionally, in the present embodiment, by before zookeeper cluster monitorings each servers, including:Each The registration code of zookeeper is write in individual server, and is registered to zookeeper clusters based on registration code;Registration After success, the monitoring of zookeeper clusters is received.In order that zookeeper monitors corresponding server, need to service each Device to zookeeper is registered;Registration process can manually be carried out by user, it is also possible to by each server Registration code is write, i.e., writes registration code in the application program of each server, allowed after program self-starting and call this automatically Registration code come to zookeeper clusters carry out correlation registration action, i.e.,:Entered to zookeeper clusters based on registration code Row registration includes:In startup of server, zookeeper clusters are called by registration code, directly noted to zookeeper clusters The server info of volume server.
After succeeding in registration, it is meant that connection is had built up between server and zookeeper, while also implying that server Under monitoring already at zookeeper clusters, zookeeper clusters with real-time monitoring and can judge connected server State, the ip addresses and the corresponding service list of port information generation according to server.
Service list can at least provide the ip address informations of corresponding server, can also include other additional letters Breath, such as priority information of ip addresses of the server etc., when client access server the priority is may be referred to Information is come the server needed for accessing.
Corresponding server should be the server of normal work in service list, in the present embodiment, pass through Zookeeper cluster monitorings each servers can also include:Monitor the connection feelings of each server and zookeeper clusters Condition, and the server of connection failure is removed from service list.When certain server due to it is unreachable, crash or it is a variety of other Reason causes the connection failure and zookeeper between, and now the server is considered failed server, can be by clothes The relevant information of the server in business list is removed.Service list now comprises only the letter of other normal servers of connection Breath, so that client can normally access required server after service list is received, without there is having accessed event The server of barrier and caused other problemses.
Then, there is inaccessible situation between server and zookeeper, also have between zookeeper and server Recover the situation of connection;When connection is recovered between server and zookeeper clusters, then the server can be continued to add Into service list.
In the present embodiment, the service list of corresponding server is sent to client in the access request according to client After end, can also include:Service list is cached into client.Client after service list is received, in order to rear The continuous convenience for processing, service list is cached, then when subsequently being intended to access corresponding server, is asked without the need for initiating to access Ask, directly corresponding server can be accessed according to the service list of caching.And if service list there occurs change, such as certain The deadlock of platform server is offline, or has newly increased server, and zookeeper clusters can automatically notify the client again again Service list is obtained, at the same time, then the service list of caching can be removed.
A kind of load-balancing method is present embodiments provided, by each server of zookeeper cluster monitorings, is received and From the access request of client, and the service list of corresponding server is sent to by client, Ran Hougen according to access request Client is accessed into corresponding server according to service list.By the enforcement of the present embodiment, can be subtracted by zookeeper clusters Few Single Point of Faliure, while the cost needed for safeguarding is also reduced, additionally, zookeeper clusters need not dynamically configure correlation Information, has saved the substantial amounts of time.
3rd embodiment
Fig. 4 is a kind of load-balancing method flow chart that the present embodiment three is provided, and is specifically included:
S401, the relevant environment of zookeeper clusters is built, and download the kit of correlation;
This is the initialization procedure of zookeeper, including creates the related hardware of zookeeper, and soft needed for writing The information such as part code.
S402, the registration code for writing in each server zookeeper;
S403, startup server, by registration code zookeeper clusters are called, and are directly registered to zookeeper clusters The server info of server;
By writing registration code in the server, server can be allowed just to directly invoke zookeeper collection on startup Group is registered;In addition, registration process can also manually be carried out by user.
S404, succeed in registration after, each server receives the monitoring of zookeeper clusters;
After succeeding in registration, it is meant that connection is had built up between server and zookeeper, while also implying that server Under monitoring already at zookeeper clusters, zookeeper clusters with real-time monitoring and can judge connected server State, the ip addresses and the corresponding service list of port information generation according to server;Service list at least can be provided accordingly Server ip address informations, other additional informations, such as the priority letter of the ip addresses of the server can also be included Breath etc., the priority information is may be referred to when client access server to access required server.
S405, zookeeper cluster receives the access request from client, and is sent out service list according to access request Give client;
During each server of zookeeper cluster monitorings, when certain server of discovery is due to unreachable, deadlock or a variety of Other reasonses cause the connection failure and zookeeper between, and now the server is considered failed server, can be by The relevant information of the server in service list is removed.Service list now comprises only other normal servers of connection Information so that client can normally access required server after service list is received, without occurring accessing The server of failure and caused other problemses;When connection is recovered between server and zookeeper clusters, then can be by The server continues to add into service list.
S406, client is accessed by corresponding server according to service list.
Client, for the convenience of subsequent treatment, service list is cached after service list is received, then When subsequently being intended to access corresponding server, without the need for initiating access request, directly phase can be accessed according to the service list of caching The server answered.And if service list there occurs change, such as certain server deadlock is offline, or service is newly increased Device, zookeeper clusters can automatically notify that the client reacquires again service list, at the same time, then can delay The service list deposited is removed.
Through the above description of the embodiments, those skilled in the art can be understood that above-described embodiment side Method can add the mode of required general hardware platform to realize by software, naturally it is also possible to by hardware, but in many cases The former is more preferably embodiment.Based on such understanding, technical scheme is substantially done to prior art in other words Going out the part of contribution can be embodied in the form of software product, and the computer software product is stored in a storage medium In (such as ROM/RAM, magnetic disc, CD), including some instructions are used so that a station terminal equipment (can be mobile phone, computer takes Business device, air-conditioner, or network equipment etc.) perform method described in each embodiment of the invention.
Embodiments of the invention are described above in conjunction with accompanying drawing, but be the invention is not limited in above-mentioned concrete Embodiment, above-mentioned specific embodiment is only schematic, rather than restricted, one of ordinary skill in the art Under the enlightenment of the present invention, in the case of without departing from present inventive concept and scope of the claimed protection, can also make a lot Form, these are belonged within the protection of the present invention.

Claims (10)

1. a kind of load balancing apparatus, it is characterised in that include:
Monitoring module, for by each server of distributed service framework cluster monitoring;
Receiver module, for receiving the access request from client;
Sending module, for the service list of the corresponding server being sent to institute according to the access request of the client State client;
AM access module, for client to be accessed into the corresponding server according to the service list.
2. load balancing apparatus as claimed in claim 1, it is characterised in that also including Registering modules, for described in each The registration code of distributed service framework is write in server, and is entered to distributed service framework cluster based on the registration code Row registration;After succeeding in registration, the monitoring of the distributed service framework cluster is received.
3. load balancing apparatus as claimed in claim 2, it is characterised in that the Registering modules are additionally operable to:In the service When device starts, distributed service framework cluster is called by the registration code, directly to the distributed service framework cluster Register the server info of the server.
4. load balancing apparatus as described in any one of claim 1-3, it is characterised in that the monitoring module is additionally operable to:
Monitor the connection of each server and the distributed service framework cluster, and by the service of connection failure Device is removed from the service list.
5. load balancing apparatus as described in any one of claim 1-3, it is characterised in that also including cache module, for will The service list is cached into the client.
6. a kind of load-balancing method, it is characterised in that include:
By each server of distributed service framework cluster monitoring;
Receive the access request from client, and according to the access request of the client by the clothes of the corresponding server Business list is sent to the client;
The client is accessed by the corresponding server according to the service list.
7. load-balancing method as claimed in claim 6, it is characterised in that supervised by distributed service framework cluster described Before controlling each server, also include:The registration code of distributed service framework is write in each described server, and is based on The registration code to distributed service framework cluster is registered;After succeeding in registration, receive the distributed service framework collection The monitoring of group.
8. load-balancing method as claimed in claim 7, it is characterised in that it is described based on the registration code to distributed clothes Business framework cluster carries out registration to be included:In the startup of server, distributed service framework is called by the registration code Cluster, directly registers the server info of the server to the distributed service framework cluster.
9. the load-balancing method as described in any one of claim 6-8, it is characterised in that described by distributed service framework Cluster monitoring each server includes:
Monitor the connection of each server and the distributed service framework cluster, and by the service of connection failure Device is removed from the service list.
10. the load-balancing method as described in any one of claim 6-8, it is characterised in that described according to the client Access request the service list of the corresponding server is sent to the client, also include:By the service List is cached into the client.
CN201611245253.0A 2016-12-29 2016-12-29 Load balancing device and method Pending CN106657354A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201611245253.0A CN106657354A (en) 2016-12-29 2016-12-29 Load balancing device and method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201611245253.0A CN106657354A (en) 2016-12-29 2016-12-29 Load balancing device and method

Publications (1)

Publication Number Publication Date
CN106657354A true CN106657354A (en) 2017-05-10

Family

ID=58837080

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201611245253.0A Pending CN106657354A (en) 2016-12-29 2016-12-29 Load balancing device and method

Country Status (1)

Country Link
CN (1) CN106657354A (en)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107172187A (en) * 2017-06-12 2017-09-15 北京明朝万达科技股份有限公司 A kind of SiteServer LBS and method
CN107547622A (en) * 2017-06-28 2018-01-05 新华三技术有限公司 A kind of resource adjusting method and device
CN108366086A (en) * 2017-12-25 2018-08-03 聚好看科技股份有限公司 A kind of method and device of control business processing
CN110071975A (en) * 2019-04-23 2019-07-30 深圳易帆互动科技有限公司 The asynchronous dynamic state server management system reported
CN110278227A (en) * 2018-03-15 2019-09-24 阿里巴巴集团控股有限公司 Service processing method, device and electronic equipment
CN110365517A (en) * 2019-05-31 2019-10-22 浙江口碑网络技术有限公司 Data processing method, device, storage medium and computer equipment
CN111354124A (en) * 2020-03-11 2020-06-30 北京创联云睿科技有限公司 Intelligent Internet of things vending system, service equipment and vending machine
CN111385324A (en) * 2018-12-28 2020-07-07 广州市百果园信息技术有限公司 Data communication method, device, equipment and storage medium
CN111522665A (en) * 2020-04-24 2020-08-11 北京思特奇信息技术股份有限公司 Zookeeper-based method for realizing high availability and load balancing of Influxdb-proxy
CN111935296A (en) * 2020-08-18 2020-11-13 成都长虹网络科技有限责任公司 System for high-availability infinite MQTT message service capacity expansion
CN112118291A (en) * 2020-08-13 2020-12-22 北京思特奇信息技术股份有限公司 Load balancing system and method for service flow
WO2022188509A1 (en) * 2021-03-12 2022-09-15 天翼云科技有限公司 Method and apparatus for task processing in distributed environment, and electronic device and medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102710554A (en) * 2012-06-25 2012-10-03 深圳中兴网信科技有限公司 Distributed message system and service status detection method thereof
CN103118142A (en) * 2013-03-14 2013-05-22 曙光信息产业(北京)有限公司 Load balancing method and system
CN103795805A (en) * 2014-02-27 2014-05-14 中国科学技术大学苏州研究院 Distributed server load balancing method based on SDN
CN104486108A (en) * 2014-12-08 2015-04-01 畅捷通信息技术股份有限公司 Node configuration method base on Zookeeper and node configuration system based on Zookeeper
CN105681463A (en) * 2016-03-14 2016-06-15 浪潮软件股份有限公司 Distributed service framework and distributed service calling system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102710554A (en) * 2012-06-25 2012-10-03 深圳中兴网信科技有限公司 Distributed message system and service status detection method thereof
CN103118142A (en) * 2013-03-14 2013-05-22 曙光信息产业(北京)有限公司 Load balancing method and system
CN103795805A (en) * 2014-02-27 2014-05-14 中国科学技术大学苏州研究院 Distributed server load balancing method based on SDN
CN104486108A (en) * 2014-12-08 2015-04-01 畅捷通信息技术股份有限公司 Node configuration method base on Zookeeper and node configuration system based on Zookeeper
CN105681463A (en) * 2016-03-14 2016-06-15 浪潮软件股份有限公司 Distributed service framework and distributed service calling system

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107172187B (en) * 2017-06-12 2019-02-22 北京明朝万达科技股份有限公司 A kind of SiteServer LBS and method
CN107172187A (en) * 2017-06-12 2017-09-15 北京明朝万达科技股份有限公司 A kind of SiteServer LBS and method
CN107547622A (en) * 2017-06-28 2018-01-05 新华三技术有限公司 A kind of resource adjusting method and device
CN108366086A (en) * 2017-12-25 2018-08-03 聚好看科技股份有限公司 A kind of method and device of control business processing
CN110278227A (en) * 2018-03-15 2019-09-24 阿里巴巴集团控股有限公司 Service processing method, device and electronic equipment
CN111385324A (en) * 2018-12-28 2020-07-07 广州市百果园信息技术有限公司 Data communication method, device, equipment and storage medium
CN110071975A (en) * 2019-04-23 2019-07-30 深圳易帆互动科技有限公司 The asynchronous dynamic state server management system reported
CN110365517A (en) * 2019-05-31 2019-10-22 浙江口碑网络技术有限公司 Data processing method, device, storage medium and computer equipment
CN110365517B (en) * 2019-05-31 2022-06-24 浙江口碑网络技术有限公司 Data processing method, data processing device, storage medium and computer equipment
CN111354124A (en) * 2020-03-11 2020-06-30 北京创联云睿科技有限公司 Intelligent Internet of things vending system, service equipment and vending machine
CN111522665A (en) * 2020-04-24 2020-08-11 北京思特奇信息技术股份有限公司 Zookeeper-based method for realizing high availability and load balancing of Influxdb-proxy
CN112118291A (en) * 2020-08-13 2020-12-22 北京思特奇信息技术股份有限公司 Load balancing system and method for service flow
CN112118291B (en) * 2020-08-13 2022-11-18 北京思特奇信息技术股份有限公司 Load balancing system and method for service flow
CN111935296A (en) * 2020-08-18 2020-11-13 成都长虹网络科技有限责任公司 System for high-availability infinite MQTT message service capacity expansion
WO2022188509A1 (en) * 2021-03-12 2022-09-15 天翼云科技有限公司 Method and apparatus for task processing in distributed environment, and electronic device and medium

Similar Documents

Publication Publication Date Title
CN106657354A (en) Load balancing device and method
CN110855633B (en) DDOS attack protection method, device, system, communication equipment and storage medium
CN105610632B (en) Virtual network equipment and related method
CN109104483B (en) Micro-service dynamic load balancing method and device based on event notification
CN104935672B (en) Load balancing service high availability implementation method and equipment
CN103581276B (en) Cluster management device, system, service customer end and correlation method
US7518983B2 (en) Proxy response apparatus
US10771318B1 (en) High availability on a distributed networking platform
JP2014534492A (en) System and method for providing load balancing and data compression flexibility in a traffic director environment
CN113347037B (en) Data center access method and device
CN111970362B (en) LVS-based vehicle networking gateway clustering method and system
CN112637332B (en) Service registration discovery method and system
CN107682172A (en) Control centre's device, the method and medium of operation system processing
CN110493337A (en) Data access method, gateway, system, storage medium and device
CN105939267A (en) Out-of-band management method and device
CN106850747B (en) Transcoding node management system and method of distributed real-time transcoding system
CN112543150B (en) Dynamic load balancing method based on server control
CN106878117B (en) Data processing method and device
CN104378449A (en) Virtual IP realization method
CN107547674A (en) Address distribution method and device
CN114745413B (en) Access control method and device for server, computer equipment and storage medium
CN103118115B (en) Facing cloud calculates virtual machine management method and the device of user
CN105373477B (en) Capacity testing method
CN109510864B (en) Forwarding method, transmission method and related device of cache request
CN109451074B (en) Server load balancing processing method based on portal protocol

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
RJ01 Rejection of invention patent application after publication

Application publication date: 20170510