CN104079630A - Business server side load balancing method, client side, server side and system - Google Patents
Business server side load balancing method, client side, server side and system Download PDFInfo
- Publication number
- CN104079630A CN104079630A CN201410251491.7A CN201410251491A CN104079630A CN 104079630 A CN104079630 A CN 104079630A CN 201410251491 A CN201410251491 A CN 201410251491A CN 104079630 A CN104079630 A CN 104079630A
- Authority
- CN
- China
- Prior art keywords
- service
- physical address
- server
- service server
- customer end
- 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
Landscapes
- Computer And Data Communications (AREA)
Abstract
The embodiment of the invention discloses a business server side load balancing method, a client side, a server side and a system. The business server side load balancing method comprises the steps that the business client side obtains business identification corresponding to a business request currently submitted by a user, obtains at least one physical address, corresponding to the business identification, of a business server in a distributed cluster server, determines the target physical address in the physical address of the business server according to the preset load balancing algorithm and establishes communication connection with the business server corresponding to the target physical address. According to the business server side load balancing method, the client side, the server side and the system, distributed load dispatching based on business can be achieved through the business server side, so that the resource utilization rate is increased, the dispatching risk is reduced, and the cost is low.
Description
Technical field
The present invention relates to Internet technical field, relate in particular to a kind of business service end load-balancing method, client, service end and system.
Background technology
Each core of existing network is along with the raising of traffic carrying capacity, the rapid growth of visit capacity and data traffic, and its disposal ability and calculating strength also correspondingly increase, and make the single server apparatus cannot processing transactions.In the case, load-balancing technique arises at the historic moment, carry out balance, share on multiple operating units and carry out by load (affairs), for example Web (World Wide Web, World Wide Web (WWW)) server, FTP (File Transfer Protocol, file transfer protocol (FTP)) the crucial application server of server, enterprise and mission critical server etc., thus jointly complete affairs.Load-balancing technique is based upon on existing network infrastructure, it provide the effectively transparent method extended network equipment of a kind of cheapness and server bandwidth, increase throughput, Strengthens network data-handling capacity, improve flexibility and the availability of network.
Existing load-balancing technique can be realized load balancing by hardware load-balancing device F5 or middleware tuxedo.F5 is with the true address of the corresponding multiple servers of a virtual address of self, client connects by virtual address and the F5 of F5, F5 determines destination server by default load-balancing algorithm, and data retransmission client being sent according to the address of destination server is to destination server.Middleware Tuxedo is a kind of client/server " middleware " product, it regulates between client and server, to ensure correctly processing transactions, middleware tuxedo is actually middleware software, tuxedo end provides the ability of whole distributed end being carried out to global monitoring and management from a central point, the information that keeper can provide according to an integral end view (being not only individual node or unit), the selection of realize target server, and the data retransmission that client is sent is to destination server.
In prior art, F5 is single-point equipment, affect the design of whole aggregated structure, scheduling mode is single, and cost is higher, and middleware tuxedo is stronger to the dependence of middleware, middleware relates to extra-pay simultaneously, if F5 or middleware tuxedo break down, cannot realize load balancing, risk is higher.
Summary of the invention
Embodiment of the present invention technical problem to be solved is, a kind of business service end load-balancing method, client, service end and system are provided, and can improve resource utilization, reduce schedule risk, and cost is lower.
In order to solve the problems of the technologies described above, the embodiment of the present invention provides a kind of service server load-balancing method, comprising:
Service customer end obtains service identification corresponding to service request of user when submit;
Described service customer end obtains the physical address of at least one service server corresponding with described service identification in distributed type assemblies server;
Described service customer end, according to default load-balancing algorithm, is determined target physical address in the physical address of described at least one service server getting;
Between service server corresponding to described service customer end and described target physical address, establish a communications link.
Correspondingly, the embodiment of the present invention also provides a kind of service server load-balancing method, comprising:
Distributed Services termination is received the service identification that service customer end sends;
Described Distributed Services end is according to described service identification, send the physical address of at least one service server corresponding with described service identification in distributed type assemblies server to described service customer end, so that described service customer end is according to default load-balancing algorithm, in the physical address of described at least one service server, determine target physical address, between service server corresponding to described service customer end and described target physical address, establish a communications link.
Correspondingly, the embodiment of the present invention also provides a kind of service customer end, comprising:
Service identification acquiring unit, for obtaining service identification corresponding to service request of user when submit;
Physical address acquiring unit, for obtaining the physical address of at least one service server that the service identification that gets with described service identification acquiring unit is corresponding at distributed type assemblies server;
Physical address determining unit, for according to default load-balancing algorithm, determines target physical address in the physical address of at least one service server getting at described physical address acquiring unit;
Unit is set up in communication connection, for and service server corresponding to the definite target physical address of described physical address determining unit between establish a communications link.
Correspondingly, the embodiment of the present invention also provides a kind of Distributed Services end, comprising:
Service identification receiving element, the service identification sending for receiving service customer end;
Physical address transmitting element, be used for according to described service identification, send the physical address of at least one service server corresponding with described service identification in distributed type assemblies server to described service customer end, so that described service customer end is according to default load-balancing algorithm, in the physical address of described at least one service server, determine target physical address, between service server corresponding to described service customer end and described target physical address, establish a communications link.
Correspondingly, the embodiment of the present invention also provides a kind of service server SiteServer LBS, and described system comprises service customer end and service server, wherein:
Described service customer end, for obtaining service identification corresponding to service request of user when submit; In distributed type assemblies server, obtain the physical address of at least one service server corresponding with described service identification; According to default load-balancing algorithm, in the physical address of described at least one service server getting, determine target physical address; And establish a communications link between service server corresponding to described target physical address;
Described service server, for and described service customer end between establish a communications link.
Implement the embodiment of the present invention, there is following beneficial effect: service customer end obtains service identification corresponding to service request of user when submit, in distributed type assemblies server, obtain the physical address of at least one service server corresponding with service identification, according to default load-balancing algorithm, in the physical address of at least one service server getting, determine target physical address, and and service server corresponding to target physical address between establish a communications link, can realize the distributed terminator scheduling based on business by service customer end, improve resource utilization, reduce schedule risk, and cost is lower.
Brief description of the drawings
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, below the accompanying drawing of required use during embodiment is described is briefly described, apparently, accompanying drawing in the following describes is some embodiments of the present invention, for those of ordinary skill in the art, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.
Fig. 1 is the schematic flow sheet of a kind of service server load-balancing method that in the embodiment of the present invention, first aspect provides;
Fig. 2 is the schematic flow sheet of a kind of service server load-balancing method that in the embodiment of the present invention, second aspect provides;
Fig. 3 is the schematic flow sheet of a kind of service server load-balancing method that in the embodiment of the present invention, the third aspect provides;
Fig. 4 is the structural representation of a kind of service customer end of providing in the embodiment of the present invention;
Fig. 5 is the structural representation of the physical address acquiring unit of Fig. 4 in the embodiment of the present invention;
Fig. 6 is the structural representation of a kind of Distributed Services end of providing in the embodiment of the present invention;
Fig. 7 is a kind of structural representation of the updating block of Fig. 6 in the embodiment of the present invention;
Fig. 8 is the another kind of structural representation of the updating block of Fig. 6 in the embodiment of the present invention;
Fig. 9 is the structural representation of a kind of service server SiteServer LBS of providing in the embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is the present invention's part embodiment, instead of whole embodiment.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtaining under creative work prerequisite, belong to the scope of protection of the invention.
In the embodiment of the present invention, service customer end can be based on service identification addressing, and according to default load-balancing algorithm, realizes service server load balancing, improves resource utilization, reduce schedule risk, and cost is lower.In addition, Distributed Services end group in the embodiment of the present invention is realized in distributed application program coordination service zookeeper, be responsible for physical address and business information and the business addressing information thereof of each service server of store and management, wherein business information can comprise the information such as service identification and service priority, business addressing information can comprise business release, Service Component, the information such as the physical address of the service server that service identification is corresponding, zookeeper is the distributed service management framework based on Observer Pattern design, Distributed Services end can be realized by the informing mechanism of zookeeper the real-time of the physical address of the service server in the real-time of physical address and the default memory of service customer end of service server.In addition, service server in the embodiment of the present invention is supported clustering functionality, one group of separate service server shows as single system in network, and managed with the pattern of triangular web, in the time that a service server breaks down, application service will be restarted or be taken over by another service server.
Refer to Fig. 1, Fig. 1 is the schematic flow sheet of a kind of service server load-balancing method that in the embodiment of the present invention, first aspect provides, and the service server load-balancing method in the present embodiment can comprise as shown in the figure:
Step S101, obtains service identification corresponding to service request of user when submit.
Service customer end can obtain service identification corresponding to service request of user when submit, wherein service request can comprise the request for business such as deposit, loan, investment or advisory agents, service identification can comprise user work as submit for service identification corresponding to service request such as deposit, loan, investment or advisory agents.
Step S102 obtains the physical address of at least one service server corresponding with service identification in distributed type assemblies server.
Service customer end gets after service identification, can in distributed type assemblies server, obtain the physical address of at least one service server corresponding with this service identification.
Concrete, service customer end can pass through API (Application Program Interface, application programming interfaces) service identification getting is sent to Distributed Services end, so that Distributed Services end is searched the physical address of at least one service server corresponding with this service identification in distributed type assemblies server, the physical address of at least one service server finding is sent to service customer end by Distributed Services end, wherein API is by presetting Development Framework encapsulation, and realize concrete applied logic by default Development Framework, ensure the cutting of applied logic and Floor layer Technology logic, the addressing mode based on service codes is transparent to concrete application, performance is higher.
Optionally, the physical address of service customer end at least one service server corresponding with this service identification in also can obtaining distributed type assemblies server in default memory, can improve address acquisition efficiency.Wherein distributed type assemblies server can be realized based on zookeeper, can comprise multiple service servers, and distributed type assemblies server can be supported clustering functionality, and the multiple service servers in distributed type assemblies server are disposed with trunking mode.
Step S103 according to default load-balancing algorithm, determines target physical address in the physical address of at least one service server getting.
Service customer end gets after the physical address of at least one service server that this service identification is corresponding, can, according to default load-balancing algorithm, determine target physical address in the physical address of at least one service server getting.
Concrete, default load-balancing algorithm can comprise polling algorithm, minimum join algorithm, response time algorithm etc., for example, service customer end can be according to polling algorithm, in the physical address of at least one service server getting, determine the physical address of the service server connecting for the last service request, the physical address of wherein said at least one service server is arranged according to default putting in order, service customer end can be according to the physical address of the service server connecting for the last service request of determining, in the physical address of at least one service server of arranging, obtain target physical address, wherein polling algorithm is suitable for Servers-all in distributed type assemblies server the situation of identical software and hardware configuration and average service request relative equilibrium, minimum join algorithm is suitable for the situation of the load balancing of growing for the processing time of service request, response speed algorithm can reflect the current running status of each service server in distributed type assemblies server preferably.Prior art F5 realizes load balancing based on minimum join algorithm, scheduling mode is single, and in the embodiment of the present invention, service customer end can preset corresponding load-balancing algorithm according to different scenes, realizes distributed terminator scheduling, flexibility is higher, promotes load-balancing efficiency.
Step S104, and establish a communications link between service server corresponding to target physical address.
Service server determines after target physical address, can and service server corresponding to target physical address between establish a communications link, to realize the load balancing of service server.
In the service server load-balancing method shown in Fig. 1, service customer end obtains service identification corresponding to service request of user when submit, in distributed type assemblies server, obtain the physical address of at least one service server corresponding with this service identification, and according to default load-balancing algorithm, in the physical address of at least one service server getting, determine target physical address, and establish a communications link between service server corresponding to target physical address, can realize the distributed terminator scheduling based on business by service customer end, improve resource utilization, reduce schedule risk, and cost is lower.
Refer to Fig. 2, Fig. 2 is the schematic flow sheet of a kind of service server load-balancing method that in the embodiment of the present invention, second aspect provides, and the service server load-balancing method in the present embodiment can comprise as shown in the figure:
Step S201, Distributed Services end upgrades the address date of service server.
Distributed Services end can upgrade the address date of service server, optionally, the business information of the service server in the monitoring distributed cluster server of Distributed Services end and business addressing information thereof, wherein business information can comprise the information such as service identification and service priority, business addressing information can comprise business release, Service Component, the information such as the physical address of the service server that service identification is corresponding, if the business information of service server and business addressing information thereof are modified or delete, Distributed Services end can upgrade the address date of this service server, wherein address date can comprise physical address or the business information etc. of service server, the embodiment of the present invention can ensure the real-time of the address date of Distributed Services end storage.
Optionally, increase a service server in distributed type assemblies server time, Distributed Services end can receive the registration request that this service server sends, this registration request can carry the physical address of this service server, Distributed Services end can upgrade the address date of this service server, store the physical address for this service server of each service identification, the present embodiment dynamic expansion ability is higher, expansion that can holding load pattern.
Step S202, if the address date of the service server upgrading comprises the physical address of service server, announcement information is sent to service customer end by Distributed Services end.
If the address date of the service server upgrading comprises the physical address of service server, Distributed Services end can send to service customer end by announcement information, with the physical address of above-mentioned service server corresponding to the service identification in the default memory of the synchronous renewal of informing business client, can ensure the real-time of the physical address of the service server in default memory.
Step S203, service customer end is according to announcement information, upgrades the physical address of the service server that service identification in default memory is corresponding.
Service customer end receives after the announcement information that Distributed Services end sends, can be according to announcement information, upgrade the physical address of the above-mentioned service server that service identification in default memory is corresponding.
Step S204, service customer end obtains service identification corresponding to service request of user when submit.
Service customer end can obtain service identification corresponding to service request of user when submit, service request can comprise the request for business such as deposit, loan, investment or advisory agents, service identification can comprise user work as submit for service identification corresponding to service request such as deposit, loan, investment or advisory agents.
Step S205, the physical address of service customer end at least one service server corresponding with this service identification obtain distributed type assemblies server in default memory in.
Service customer end gets after service identification, the physical address of at least one service server corresponding with this service identification in can obtaining distributed type assemblies server in default memory, wherein, service customer end stores the physical address of at least one corresponding this service identification of Distributed Services end transmission service server in default memory in advance.
In the embodiment of the present invention, service customer end, default memory and Distributed Services end are undertaken alternately by interface, default memory surface operates to interface, not paying close attention to Distributed Services end is distributed caching assembly, database, file or online data passage etc., default memory provides interface to service customer end, service customer end obtains the physical address of service server in default memory, and how the physical address that need not pay close attention to service server obtains, default memory makes service customer end and Distributed Services end form the relation of loose coupling, can reduce the dependence between service customer end and Distributed Services end.
Step S206, service customer end, according to default load-balancing algorithm, is determined target physical address in the physical address of at least one service server getting.
Concrete, default load-balancing algorithm can comprise polling algorithm, minimum join algorithm, response time algorithm etc., for example, service customer end can be according to polling algorithm, in the physical address of at least one service server getting, determine the physical address of the service server connecting for the last service request, the physical address of wherein said at least one service server is arranged according to default putting in order, service customer end can be according to the physical address of the service server connecting for the last service request of determining, in the physical address of at least one service server of arranging, obtain target physical address, wherein polling algorithm is suitable for Servers-all in distributed type assemblies server the situation of identical software and hardware configuration and average service request relative equilibrium, minimum join algorithm is suitable for the situation of the load balancing of growing for the processing time of service request, response speed algorithm can reflect the current running status of each service server in distributed type assemblies server preferably.Prior art F5 realizes load balancing based on minimum join algorithm, scheduling mode is single, and in the embodiment of the present invention, service customer end can preset corresponding load-balancing algorithm according to different scenes, realizes distributed terminator scheduling, flexibility is higher, promotes load-balancing efficiency.
Step S207, establishes a communications link between service server corresponding to service customer end and target physical address.
Service server determines after target physical address, can and service server corresponding to target physical address between establish a communications link, to realize the load balancing of service server.
In optional embodiment, if service server corresponding to target physical address determines that the communication connection between service server is overtime, service server corresponding to target physical address can send the connection time-out information for this service identification to Distributed Services end, Distributed Services end can be according to the connection time-out information receiving, delete the target physical address for this service identification, and send announcement information to service customer end, so that service customer end is deleted the target physical address for this service identification in default memory according to this announcement information, can ensure the real-time of the physical address of the service server in default memory.
In the service server load-balancing method shown in Fig. 2, if the address date of the service server that Distributed Services end upgrades comprises the physical address of service server, announcement information is sent to service customer end by Distributed Services end, service customer end is according to announcement information, upgrade the physical address of the service server that service identification in default memory is corresponding, further, service customer end obtains service identification corresponding to service request of user when submit, the physical address of at least one service server corresponding with this service identification obtain distributed type assemblies server in default memory in, and according to default load-balancing algorithm, in the physical address of at least one service server getting, determine target physical address, and establish a communications link between service server corresponding to target physical address, can realize the distributed terminator scheduling based on business by service customer end, improve resource utilization, reduce schedule risk, and cost is lower.
Refer to Fig. 3, Fig. 3 is the schematic flow sheet of a kind of service server load-balancing method that in the embodiment of the present invention, the third aspect provides, and the service server load-balancing method in the present embodiment can comprise as shown in the figure:
Step S301, service server sends register instruction to Distributed Services end, and this register instruction is carried the physical address of service server.
Each service server in distributed type assemblies server can send register instruction to Distributed Services end respectively, and this register instruction can be carried the physical address of service server.
Step S302, Distributed Services end storage service identifies the physical address of corresponding service server.
Distributed Services termination receives after the physical address that service server sends, can storage service the physical address of this service server corresponding to mark.
Step S303, service customer end obtains service identification corresponding to service request of user when submit.
Service customer end can obtain service identification corresponding to service request of user when submit, service request can comprise the request for business such as deposit, loan, investment or advisory agents, service identification can comprise user work as submit for service identification corresponding to service request such as deposit, loan, investment or advisory agents.
Step S304, the service identification getting is sent to Distributed Services end by service customer end.
Concrete, service customer end can pass through API (Application Program Interface, application programming interfaces) service identification getting is sent to Distributed Services end, so that Distributed Services end is searched the physical address of at least one service server corresponding with this service identification in distributed type assemblies server, the physical address of at least one service server finding is sent to service customer end by Distributed Services end, wherein API is by presetting Development Framework encapsulation, and realize concrete applied logic by default Development Framework, ensure the cutting of applied logic and Floor layer Technology logic, the addressing mode based on service codes is transparent to concrete application, performance is higher.
Step S305, Distributed Services end, according to this service identification, sends the physical address of at least one service server corresponding with this service identification in distributed type assemblies server to service customer end.
Distributed Services end can, according to this service identification, be searched the physical address of at least one service server corresponding with this service identification, and the physical address of at least one corresponding this service identification service server is sent to service customer end.
Step S306, service customer end, according to default load-balancing algorithm, is determined target physical address in the physical address of at least one service server getting.
Concrete, default load-balancing algorithm can comprise polling algorithm, minimum join algorithm, response time algorithm etc., for example, service customer end can be according to polling algorithm, in the physical address of at least one service server getting, determine the physical address of the service server connecting for the last service request, the physical address of wherein said at least one service server is arranged according to default putting in order, service customer end can be according to the physical address of the service server connecting for the last service request of determining, in the physical address of at least one service server of arranging, obtain target physical address, wherein polling algorithm is suitable for Servers-all in distributed type assemblies server the situation of identical software and hardware configuration and average service request relative equilibrium, minimum join algorithm is suitable for the situation of the load balancing of growing for the processing time of service request, response speed algorithm can reflect the current running status of each service server preferably.Prior art F5 realizes load balancing based on minimum join algorithm, scheduling mode is single, and in the embodiment of the present invention, service customer end can preset corresponding load-balancing algorithm according to different scenes, realizes distributed terminator scheduling, flexibility is higher, promotes load-balancing efficiency.
In optional embodiment, service customer end can store the physical address of at least one corresponding service identification getting service server in default memory.
Step S307, establishes a communications link between service server corresponding to service customer end and target physical address.
Service server determines after target physical address, can and service server corresponding to target physical address between establish a communications link, to realize the load balancing of service server.
In the service server load-balancing method shown in Fig. 3, the register instruction that Distributed Services end sends according to service server, storage service identifies the physical address of corresponding service server, service identification corresponding to service request that user is worked as submit by service customer end sends to Distributed Services end, Distributed Services end is according to this service identification, send the physical address of at least one service server corresponding with this service identification in distributed type assemblies server to service customer end, service customer end is according to default load-balancing algorithm, in the physical address of at least one service server getting, determine target physical address, between service server corresponding to service customer end and target physical address, establish a communications link, can realize the distributed terminator scheduling based on business by service customer end, improve resource utilization, reduce schedule risk, and cost is lower.
Refer to Fig. 4, Fig. 4 is the structural representation of a kind of service customer end 400 of providing in the embodiment of the present invention, service customer end 400 in the embodiment of the present invention at least can comprise that service identification acquiring unit 401, physical address acquiring unit 402, physical address determining unit 403 and communication connection set up unit 404 as shown in the figure, wherein:
Service identification acquiring unit 401, for obtaining service identification corresponding to service request of user when submit, service request can comprise the request for business such as deposit, loan, investment or advisory agents, service identification can comprise user work as submit for service identification corresponding to service request such as deposit, loan, investment or advisory agents.
Physical address acquiring unit 402, for obtaining the physical address of at least one service server that the service identification that gets with service identification acquiring unit 401 is corresponding at distributed type assemblies server.
Physical address determining unit 403, for according to default load-balancing algorithm, determines target physical address in the physical address of at least one service server getting at physical address acquiring unit 402.
Concrete, default load-balancing algorithm can comprise polling algorithm, minimum join algorithm, response time algorithm etc., for example, physical address determining unit 403 can be according to polling algorithm, in the physical address of at least one service server getting, determine the physical address of the service server connecting for the last service request, the physical address of wherein said at least one service server is arranged according to default putting in order, physical address determining unit 403 can be according to the physical address of the service server connecting for the last service request of determining, in the physical address of at least one service server of arranging, obtain target physical address, in the embodiment of the present invention, service customer end can be realized distributed terminator scheduling, flexibility is higher, promote load-balancing efficiency.
Unit 404 is set up in communication connection, for and service server corresponding to the definite target physical address of physical address determining unit 403 between establish a communications link.
As the optional execution mode of one, the physical address acquiring unit 402 in the embodiment of the present invention can also comprise:
Service identification sending module 501, for sending described service identification to Distributed Services end.
Service identification sending module 501 can send to Distributed Services end by the service identification getting by API, so that Distributed Services end is searched the physical address of at least one service server corresponding with this service identification in distributed type assemblies server, wherein API is by presetting Development Framework encapsulation, and realize concrete applied logic by default Development Framework, ensure the cutting of applied logic and Floor layer Technology logic, the addressing mode based on service codes is transparent to concrete application, and performance is higher.
Physical address acquisition module 502, for receiving the physical address of at least one service server that described distributed type assemblies server that described Distributed Services end sends is corresponding with described service identification.
As the optional execution mode of one, the service customer end 400 in the embodiment of the present invention can also comprise:
Memory cell 405, the physical address of at least one service server getting for physical address acquiring unit 402 corresponding to service identification that service identification acquiring unit 401 is got stores default memory into.
As the optional execution mode of one, physical address acquiring unit 402, for the physical address of at least one service server corresponding with described service identification in default memory obtains described distributed type assemblies server.
As the optional execution mode of one, the service customer end 400 in the embodiment of the present invention can also comprise:
Announcement information receiving element 406, the announcement information sending for receiving described Distributed Services end.
Updating block 407, for the announcement information receiving according to announcement information receiving element 406, upgrades the physical address of the service server that service identification in described default memory is corresponding.
In the service customer end 400 shown in Fig. 4 and Fig. 5, service identification acquiring unit 401 obtains service identification corresponding to service request of user when submit, physical address acquiring unit 402 obtains the physical address of at least one service server corresponding with service identification in distributed type assemblies server, physical address determining unit 403 is according to default load-balancing algorithm, in the physical address of at least one service server getting, determine target physical address, communication connection is set up between unit 404 and service server corresponding to definite target physical address and is established a communications link, can realize the distributed terminator scheduling based on business by service customer end 400, improve resource utilization, reduce schedule risk, and cost is lower.
Refer to Fig. 6, Fig. 6 is the structural representation of a kind of Distributed Services end 600 of providing in the embodiment of the present invention, Distributed Services end 600 in the embodiment of the present invention at least can comprise service identification receiving element 601 and physical address transmitting element 602 as shown in the figure, wherein:
Service identification receiving element 601, the service identification sending for receiving service customer end.
Physical address transmitting element 602, be used for according to described service identification, send the physical address of at least one service server corresponding with described service identification in distributed type assemblies server to described service customer end, so that described service customer end is according to default load-balancing algorithm, in the physical address of described at least one service server, determine target physical address, between service server corresponding to described service customer end and described target physical address, establish a communications link.
As the optional execution mode of one, the Distributed Services end 600 in the embodiment of the present invention can also comprise:
Register instruction receiving element 603, the register instruction sending for receiving the service server of described distributed type assemblies server, described register instruction is carried the physical address of described service server.
Memory cell 604, for the physical address of described service server corresponding to storage service mark, triggers service identification receiving element 601 and receives the service identification that service customer end sends.
As the optional execution mode of one, the Distributed Services end 600 in the embodiment of the present invention can also comprise:
Updating block 605, for upgrading the address date of described service server.
Announcement information transmitting element 606, if the address date of the described service server upgrading for updating block 605 comprises the physical address of described service server, announcement information is sent to described service customer end by described Distributed Services end, so that described service customer end according to described in the announcement information that receives, upgrade the physical address of the described service server that service identification in default memory is corresponding.
As the optional execution mode of one, the updating block 605 in the embodiment of the present invention can as shown in Figure 7, further comprise:
Monitoring module 701, for monitoring business information and the business addressing information thereof of described service server.
Update module 702, if the business information and the business addressing information thereof that monitor described service server for monitoring module 701 are modified or delete, upgrades the address date of described service server.
As the optional execution mode of one, if the described service server of described renewal comprises the service server that target physical address is corresponding, the updating block 605 in the embodiment of the present invention can as shown in Figure 8, further comprise:
Time-out information receiver module 801, if overtime for being connected between service server corresponding to described target physical address and described service customer end, receive the connection time-out information for described service identification that service server corresponding to described target physical address sends.
Physical address removing module 802, for the connection time-out information receiving according to time-out information receiver module 801, deletes the described target physical address for described service identification.
At Fig. 6, in Distributed Services end shown in Fig. 7 and Fig. 8, service identification receiving element 601 receives the service identification that service customer end sends, physical address transmitting element 602 is according to described service identification, send the physical address of at least one service server corresponding with described service identification in distributed type assemblies server to described service customer end, so that described service customer end is according to default load-balancing algorithm, in the physical address of described at least one service server, determine target physical address, between service server corresponding to described service customer end and described target physical address, establish a communications link, can improve resource utilization, reduce schedule risk, and cost is lower.
Refer to Fig. 9, Fig. 9 is the structural representation of a kind of service server SiteServer LBS 900 of providing in the embodiment of the present invention, service server SiteServer LBS 900 in the embodiment of the present invention at least can comprise service customer end 901 and service server 902 as shown in the figure, service customer end 901 can be in conjunction with the service customer end shown in Fig. 4 and Fig. 5, service server 902 can be in conjunction with the service server shown in Fig. 6, Fig. 7 and Fig. 8, wherein:
Service customer end 901, for obtaining service identification corresponding to service request of user when submit; In distributed type assemblies server, obtain the physical address of at least one service server corresponding with described service identification; According to default load-balancing algorithm, in the physical address of described at least one service server getting, determine target physical address; And establish a communications link between service server corresponding to described target physical address.
Service server 902, for and described service customer end between establish a communications link.
As the optional execution mode of one, the service server SiteServer LBS 900 in the embodiment of the present invention can also comprise Distributed Services end 903, wherein:
Service customer end 901, for sending to Distributed Services end 903 by the service identification getting.
Further, Distributed Services end 903, for sending to service customer end 901 by the physical address of at least one corresponding with described service identification described distributed type assemblies server service server.
Further alternative, service customer end 901, stores default memory into for the physical address of at least one service server corresponding to described service identification that Distributed Services end 903 is sent.
As the optional execution mode of one, service customer end 901, for the physical address of at least one service server corresponding with described service identification in default memory obtains described distributed type assemblies server.
As the optional execution mode of one, Distributed Services end 903, also, for upgrading the address date of service server, if the address date of the service server upgrading comprises the physical address of described service server, announcement information is sent to service customer end 901 by Distributed Services end 903.
Further, service customer end 901, for the announcement information receiving described in basis, upgrades the physical address of the described service server that service identification in default memory is corresponding.
Optionally, Distributed Services end 903 is monitored business information and the business addressing information thereof of the service server in described distributed type assemblies server, if the business information of described service server and business addressing information thereof are modified or delete, upgrade the address date of described service server.
Optionally, if be connected overtime between the service server 902 that described target physical address is corresponding and service customer end 901, the connection time-out information for described service identification that service server 902 corresponding to Distributed Services end 903 receiving target physical addresss sends, and according to the connection time-out information receiving, delete the described target physical address for described service identification.
In service server SiteServer LBS in the present embodiment, service customer end 901 obtains service identification corresponding to service request of user when submit, in distributed type assemblies server, obtain the physical address of at least one service server corresponding with described service identification, according to default load-balancing algorithm, in the physical address of at least one service server getting, determine target physical address, and establish a communications link between service server corresponding to target physical address, can improve resource utilization, reduce schedule risk, and cost is lower.
One of ordinary skill in the art will appreciate that all or part of flow process realizing in above-described embodiment method, can carry out the hardware that instruction is relevant by computer program to complete, described program can be stored in computer read/write memory medium, this program, in the time carrying out, can comprise as the flow process of the embodiment of above-mentioned each side method.Wherein, described storage medium can be magnetic disc, CD, read-only store-memory body (Read-Only Memory, ROM) or random store-memory body (Random Access Memory, RAM) etc.
It should be noted that, in the above-described embodiments, the description of each embodiment is all emphasized particularly on different fields in certain embodiment, there is no the part of detailed description, can be referring to the associated description of other embodiment.Secondly, those skilled in the art also should know, the embodiment described in specification all belongs to preferred embodiment, and related action and module might not be that the present invention is necessary.
Step in embodiment of the present invention method can be carried out according to actual needs order and adjusted, merges and delete.
Unit in embodiment of the present invention device or module can merge according to actual needs, divide and delete.
Unit described in the embodiment of the present invention or module, can pass through universal integrated circuit, for example CPU (Central Processing Unit, central processing unit), or realize by ASIC (Application Specific Integrated Circuit, application-specific integrated circuit (ASIC)).
The service server load-balancing method, client, service end and the system that above the embodiment of the present invention are provided are described in detail, applied specific case herein principle of the present invention and execution mode are set forth, the explanation of above embodiment is just for helping to understand method of the present invention and core concept thereof; , for one of ordinary skill in the art, according to thought of the present invention, all will change in specific embodiments and applications, in sum, this description should not be construed as limitation of the present invention meanwhile.
Claims (21)
1. a service server load-balancing method, is characterized in that, described method comprises:
Service customer end obtains service identification corresponding to service request of user when submit;
Described service customer end obtains the physical address of at least one service server corresponding with described service identification in distributed type assemblies server;
Described service customer end, according to default load-balancing algorithm, is determined target physical address in the physical address of described at least one service server getting;
Between service server corresponding to described service customer end and described target physical address, establish a communications link.
2. the method for claim 1, is characterized in that, the physical address that described service customer end obtains at least one service server corresponding with described service identification in distributed type assemblies server comprises:
Described service customer end sends described service identification to Distributed Services end;
Described service customer end receives the physical address of at least one service server corresponding with described service identification in the described distributed type assemblies server of described Distributed Services end transmission.
3. method as claimed in claim 2, is characterized in that, described method also comprises:
Described service customer end stores the corresponding relation of the physical address of described service identification and described at least one service server in default memory into.
4. the method for claim 1, is characterized in that, the physical address that described service customer end obtains at least one service server corresponding with described service identification in distributed type assemblies server comprises:
Described service customer end obtains the physical address of at least one service server corresponding with described service identification in described distributed type assemblies server in described default memory.
5. method as claimed in claim 4, is characterized in that, described method also comprises:
Described service customer end receives the announcement information that described Distributed Services end sends;
Described service customer end according to described in the announcement information that receives, upgrade the physical address of the service server that service identification in described default memory is corresponding.
6. a service server load-balancing method, is characterized in that, described method comprises:
Distributed Services termination is received the service identification that service customer end sends;
Described Distributed Services end is according to described service identification, send the physical address of at least one service server corresponding with described service identification in distributed type assemblies server to described service customer end, so that described service customer end is according to default load-balancing algorithm, in the physical address of described at least one service server, determine target physical address, between service server corresponding to described service customer end and described target physical address, establish a communications link.
7. method as claimed in claim 6, is characterized in that, before described Distributed Services termination is received the service identification of service customer end transmission, described method also comprises:
Described Distributed Services termination is received the register instruction that the service server in described distributed type assemblies server sends, and described register instruction is carried the physical address of described service server;
The physical address of the described service server of described Distributed Services end storage service mark correspondence.
8. method as claimed in claim 7, is characterized in that, described method also comprises:
Described Distributed Services end upgrades the address date of described service server;
If the address date of the described service server of described renewal comprises the physical address of described service server, announcement information is sent to described service customer end by described Distributed Services end, so that described service customer end according to described in the announcement information that receives, upgrade the physical address of the described service server that service identification in default memory is corresponding.
9. method as claimed in claim 8, is characterized in that, the address date that described Distributed Services end upgrades described service server comprises:
Described Distributed Services end is monitored business information and the business addressing information thereof of described service server;
If described Distributed Services end monitors business information and the business addressing information thereof of described service server and is modified or deletes, upgrade the address date of described service server.
10. method as claimed in claim 8, is characterized in that, described service server comprises the service server that described target physical address is corresponding;
The address date that described Distributed Services end upgrades described service server comprises:
If be connected overtimely between the service server that described target physical address is corresponding and described service customer end, described Distributed Services termination is received the connection time-out information for described service identification that service server corresponding to described target physical address sends;
The connection time-out information receiving described in described Distributed Services end basis, deletes the described target physical address for described service identification.
11. 1 kinds of service customer ends, is characterized in that, described service customer end comprises:
Service identification acquiring unit, for obtaining service identification corresponding to service request of user when submit;
Physical address acquiring unit, for obtaining the physical address of at least one service server that the service identification that gets with described service identification acquiring unit is corresponding at distributed type assemblies server;
Physical address determining unit, for according to default load-balancing algorithm, determines target physical address in the physical address of at least one service server getting at described physical address acquiring unit;
Unit is set up in communication connection, for and service server corresponding to the definite target physical address of described physical address determining unit between establish a communications link.
12. service customer ends as claimed in claim 11, is characterized in that, described physical address acquiring unit comprises:
Service identification sending module, for sending described service identification to Distributed Services end;
Physical address acquisition module, for receiving the physical address of at least one service server that described distributed type assemblies server that described Distributed Services end sends is corresponding with described service identification.
13. service customer ends as claimed in claim 12, is characterized in that, described service customer end also comprises:
Memory cell, the corresponding relation of the physical address of at least one service server getting for service identification that described service identification acquiring unit is got and described physical address acquiring unit stores default memory into.
14. service customer ends as claimed in claim 11, is characterized in that,
Described physical address acquiring unit, for obtaining the physical address of at least one service server corresponding with described service identification in described distributed type assemblies server at described default memory.
15. service customer ends as claimed in claim 14, is characterized in that, described service customer end also comprises:
Announcement information receiving element, the announcement information sending for receiving described Distributed Services end;
Updating block, for the announcement information receiving according to described announcement information receiving element, upgrades the physical address of the service server that service identification in described default memory is corresponding.
16. 1 kinds of Distributed Services ends, is characterized in that, described Distributed Services end comprises:
Service identification receiving element, the service identification sending for receiving service customer end;
Physical address transmitting element, be used for according to described service identification, send the physical address of at least one service server corresponding with described service identification in distributed type assemblies server to described service customer end, so that described service customer end is according to default load-balancing algorithm, in the physical address of described at least one service server, determine target physical address, between service server corresponding to described service customer end and described target physical address, establish a communications link.
17. Distributed Services ends as claimed in claim 16, is characterized in that, described Distributed Services end also comprises:
Register instruction receiving element, the register instruction sending for receiving the service server of described distributed type assemblies server, described register instruction is carried the physical address of described service server;
Memory cell, for the physical address of described service server corresponding to storage service mark, triggers described service identification receiving element and receives the service identification that described service customer end sends.
18. Distributed Services ends as claimed in claim 17, is characterized in that, described Distributed Services end also comprises:
Updating block, for upgrading the address date of described service server;
Announcement information transmitting element, if the address date of the described service server upgrading for described updating block comprises the physical address of described service server, announcement information is sent to described service customer end by described Distributed Services end, so that described service customer end according to described in the announcement information that receives, upgrade the physical address of the described service server that service identification in default memory is corresponding.
19. Distributed Services ends as claimed in claim 18, is characterized in that, described updating block comprises:
Monitoring module, for monitoring business information and the business addressing information thereof of described service server;
Update module, if the business information and the business addressing information thereof that monitor described service server for described monitoring module are modified or delete, upgrades the address date of described service server.
20. Distributed Services ends as claimed in claim 18, is characterized in that, described service server comprises the service server that described target physical address is corresponding;
Described updating block comprises:
Time-out information receiver module, if overtime for being connected between service server corresponding to described target physical address and described service customer end, receive the connection time-out information for described service identification that service server corresponding to described target physical address sends;
Physical address removing module, for the connection time-out information receiving according to described time-out information receiver module, deletes the described target physical address for described service identification.
21. 1 kinds of service server SiteServer LBSs, is characterized in that, described system comprises service customer end and the service server as described in any one in claim 11～15, wherein:
Described service customer end, for obtaining service identification corresponding to service request of user when submit; In distributed type assemblies server, obtain the physical address of at least one service server corresponding with described service identification; According to default load-balancing algorithm, in the physical address of described at least one service server getting, determine target physical address; And establish a communications link between service server corresponding to described target physical address;
Described service server, for and described service customer end between establish a communications link.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410251491.7A CN104079630A (en) | 2014-06-09 | 2014-06-09 | Business server side load balancing method, client side, server side and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410251491.7A CN104079630A (en) | 2014-06-09 | 2014-06-09 | Business server side load balancing method, client side, server side and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104079630A true CN104079630A (en) | 2014-10-01 |
Family
ID=51600670
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410251491.7A Pending CN104079630A (en) | 2014-06-09 | 2014-06-09 | Business server side load balancing method, client side, server side and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104079630A (en) |
Cited By (36)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104618466A (en) * | 2015-01-20 | 2015-05-13 | 上海交通大学 | System for balancing load and controlling overload based on message transfer and control method of system |
| CN105141452A (en) * | 2015-08-07 | 2015-12-09 | 北京思特奇信息技术股份有限公司 | High-performance service system and method based on CXF |
| CN105610907A (en) * | 2015-12-18 | 2016-05-25 | 华夏银行股份有限公司 | Server access method and device |
| CN105607951A (en) * | 2015-12-17 | 2016-05-25 | 北京奇虎科技有限公司 | Method and device for processing data request and obtaining server information |
| CN106302648A (en) * | 2016-07-29 | 2017-01-04 | 北京小米移动软件有限公司 | Method for processing business and device |
| CN106375355A (en) * | 2015-07-20 | 2017-02-01 | 中兴通讯股份有限公司 | Load balancing processing method and apparatus |
| CN106445536A (en) * | 2016-09-28 | 2017-02-22 | 湛江市霞山区新软佳科技有限公司 | Automated business design management system |
| CN106549878A (en) * | 2016-10-26 | 2017-03-29 | 中国银联股份有限公司 | A kind of service shunting method and device |
| CN106550003A (en) * | 2015-09-23 | 2017-03-29 | 腾讯科技（深圳）有限公司 | The control method of load balancing, apparatus and system |
| CN106657367A (en) * | 2016-12-30 | 2017-05-10 | 北京三快在线科技有限公司 | Service data acquisition method, device and system |
| CN106899680A (en) * | 2017-03-09 | 2017-06-27 | 上海亿账通区块链科技有限公司 | The burst treating method and apparatus of multi-tiling chain |
| CN107172214A (en) * | 2017-07-18 | 2017-09-15 | 广州华多网络科技有限公司 | A kind of service node with load balancing finds method and device |
| CN107368259A (en) * | 2017-05-25 | 2017-11-21 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus that business datum is write in the catenary system to block |
| CN107807815A (en) * | 2017-10-19 | 2018-03-16 | 北京京东尚科信息技术有限公司 | The method and apparatus of distributed treatment task |
| CN108696557A (en) * | 2017-04-11 | 2018-10-23 | 北京京东尚科信息技术有限公司 | Information processing system, method and apparatus |
| WO2019034091A1 (en) * | 2017-08-15 | 2019-02-21 | 中兴通讯股份有限公司 | Distribution method for distributed data computing, device, server and storage medium |
| CN109660607A (en) * | 2018-12-05 | 2019-04-19 | 北京金山云网络技术有限公司 | A kind of service request distribution method, method of reseptance, device and server cluster |
| CN109698785A (en) * | 2017-10-24 | 2019-04-30 | 广东亿迅科技有限公司 | A kind of the real-time messages method for pushing and device of distribution high concurrent |
| CN110351342A (en) * | 2019-06-20 | 2019-10-18 | 平安科技（深圳）有限公司 | Service order processing method, device, computer equipment and storage medium |
| CN110401708A (en) * | 2019-07-23 | 2019-11-01 | 中南民族大学 | Session processing system and method based on server load state |
| CN110417886A (en) * | 2019-07-29 | 2019-11-05 | 广州竞远安全技术股份有限公司 | A kind of load-balancing method of integrated service, apparatus and system |
| CN110677353A (en) * | 2019-09-06 | 2020-01-10 | 中国平安财产保险股份有限公司 | Data access method and system |
| CN111385323A (en) * | 2018-12-28 | 2020-07-07 | 中国移动通信集团江西有限公司 | EJB service processing method, device, equipment and medium |
| CN111385324A (en) * | 2018-12-28 | 2020-07-07 | 广州市百果园信息技术有限公司 | Data communication method, device, equipment and storage medium |
| CN111552748A (en) * | 2020-05-08 | 2020-08-18 | 深圳知路科技有限公司 | Data processing method, device and system |
| CN111722920A (en) * | 2019-03-22 | 2020-09-29 | 鼎捷软件股份有限公司 | Load control method |
| CN111787048A (en) * | 2020-04-28 | 2020-10-16 | 北京沃东天骏信息技术有限公司 | Terminal device connection method, scheduling server and Internet of things system |
| CN112383632A (en) * | 2020-11-17 | 2021-02-19 | 珠海大横琴科技发展有限公司 | Load balancing method and device |
| CN113055427A (en) * | 2019-12-28 | 2021-06-29 | 浙江宇视科技有限公司 | Service-based server cluster access method and device |
| CN113268343A (en) * | 2021-05-10 | 2021-08-17 | 北京邮电大学 | Load balancing system and method |
| CN113312154A (en) * | 2021-06-30 | 2021-08-27 | 北京微纳星空科技有限公司 | Method, system, equipment and storage medium for scheduling satellite service resources |
| CN113691573A (en) * | 2020-05-19 | 2021-11-23 | 深圳市理邦精密仪器股份有限公司 | Monitoring method, equipment, system and storage device of medical monitoring system |
| CN114281376A (en) * | 2021-12-09 | 2022-04-05 | 上海卓悠网络科技有限公司 | Service-based hot upgrading method and equipment |
| CN114610461A (en) * | 2022-03-17 | 2022-06-10 | 北京火山引擎科技有限公司 | Task processing method and device |
| CN114915656A (en) * | 2021-12-29 | 2022-08-16 | 南京四维智联科技有限公司 | Internet of vehicles terminal access method, device, storage medium and electronic equipment |
| CN115277351A (en) * | 2022-07-27 | 2022-11-01 | 天翼云科技有限公司 | Distributed management system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102316138A (en) * | 2010-07-02 | 2012-01-11 | 深圳市财付通科技有限公司 | Client end and load balance method |
| US20120231824A1 (en) * | 2011-03-10 | 2012-09-13 | Miroslav Budic | Load balancing in a cellular telecommunication network |
| CN102761618A (en) * | 2012-07-03 | 2012-10-31 | 杭州华三通信技术有限公司 | Method, equipment and system for realizing load balancing |
| CN103457870A (en) * | 2013-09-25 | 2013-12-18 | 武汉理工大学 | Load-balancing and high-availability sub system used for distribution-type system and method |
-
2014
- 2014-06-09 CN CN201410251491.7A patent/CN104079630A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102316138A (en) * | 2010-07-02 | 2012-01-11 | 深圳市财付通科技有限公司 | Client end and load balance method |
| US20120231824A1 (en) * | 2011-03-10 | 2012-09-13 | Miroslav Budic | Load balancing in a cellular telecommunication network |
| CN102761618A (en) * | 2012-07-03 | 2012-10-31 | 杭州华三通信技术有限公司 | Method, equipment and system for realizing load balancing |
| CN103457870A (en) * | 2013-09-25 | 2013-12-18 | 武汉理工大学 | Load-balancing and high-availability sub system used for distribution-type system and method |
Cited By (56)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104618466A (en) * | 2015-01-20 | 2015-05-13 | 上海交通大学 | System for balancing load and controlling overload based on message transfer and control method of system |
| CN106375355A (en) * | 2015-07-20 | 2017-02-01 | 中兴通讯股份有限公司 | Load balancing processing method and apparatus |
| CN106375355B (en) * | 2015-07-20 | 2020-02-28 | 中兴通讯股份有限公司 | Load balancing processing method and device |
| CN105141452A (en) * | 2015-08-07 | 2015-12-09 | 北京思特奇信息技术股份有限公司 | High-performance service system and method based on CXF |
| CN106550003A (en) * | 2015-09-23 | 2017-03-29 | 腾讯科技（深圳）有限公司 | The control method of load balancing, apparatus and system |
| CN106550003B (en) * | 2015-09-23 | 2020-09-11 | 腾讯科技（深圳）有限公司 | Load balancing control method, device and system |
| CN105607951A (en) * | 2015-12-17 | 2016-05-25 | 北京奇虎科技有限公司 | Method and device for processing data request and obtaining server information |
| CN105610907A (en) * | 2015-12-18 | 2016-05-25 | 华夏银行股份有限公司 | Server access method and device |
| CN106302648B (en) * | 2016-07-29 | 2019-05-07 | 北京小米移动软件有限公司 | Method for processing business and device |
| CN106302648A (en) * | 2016-07-29 | 2017-01-04 | 北京小米移动软件有限公司 | Method for processing business and device |
| CN106445536A (en) * | 2016-09-28 | 2017-02-22 | 湛江市霞山区新软佳科技有限公司 | Automated business design management system |
| CN106549878A (en) * | 2016-10-26 | 2017-03-29 | 中国银联股份有限公司 | A kind of service shunting method and device |
| CN106549878B (en) * | 2016-10-26 | 2020-07-07 | 中国银联股份有限公司 | Service distribution method and device |
| CN106657367A (en) * | 2016-12-30 | 2017-05-10 | 北京三快在线科技有限公司 | Service data acquisition method, device and system |
| CN106899680A (en) * | 2017-03-09 | 2017-06-27 | 上海亿账通区块链科技有限公司 | The burst treating method and apparatus of multi-tiling chain |
| CN106899680B (en) * | 2017-03-09 | 2019-07-30 | 深圳壹账通智能科技有限公司 | The fragment treating method and apparatus of multi-tiling chain |
| CN108696557A (en) * | 2017-04-11 | 2018-10-23 | 北京京东尚科信息技术有限公司 | Information processing system, method and apparatus |
| CN108696557B (en) * | 2017-04-11 | 2021-08-10 | 北京京东尚科信息技术有限公司 | Information processing system, method and device |
| US11074245B2 (en) | 2017-05-25 | 2021-07-27 | Advanced New Technologies Co., Ltd. | Method and device for writing service data in block chain system |
| CN107368259B (en) * | 2017-05-25 | 2020-07-10 | 创新先进技术有限公司 | Method and device for writing service data into block chain system |
| CN107368259A (en) * | 2017-05-25 | 2017-11-21 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus that business datum is write in the catenary system to block |
| US10698885B2 (en) | 2017-05-25 | 2020-06-30 | Alibaba Group Holding Limited | Method and device for writing service data in block chain system |
| CN107172214B (en) * | 2017-07-18 | 2020-08-28 | 广州华多网络科技有限公司 | Service node discovery method and device with load balancing function |
| CN107172214A (en) * | 2017-07-18 | 2017-09-15 | 广州华多网络科技有限公司 | A kind of service node with load balancing finds method and device |
| WO2019034091A1 (en) * | 2017-08-15 | 2019-02-21 | 中兴通讯股份有限公司 | Distribution method for distributed data computing, device, server and storage medium |
| CN109413117A (en) * | 2017-08-15 | 2019-03-01 | 中兴通讯股份有限公司 | Distributed data calculation method, device, server and computer storage medium |
| CN109413117B (en) * | 2017-08-15 | 2022-05-06 | 中兴通讯股份有限公司 | Distributed data calculation method, device, server and computer storage medium |
| CN107807815A (en) * | 2017-10-19 | 2018-03-16 | 北京京东尚科信息技术有限公司 | The method and apparatus of distributed treatment task |
| CN107807815B (en) * | 2017-10-19 | 2020-11-24 | 北京京东尚科信息技术有限公司 | Method and device for processing tasks in distributed mode |
| CN109698785A (en) * | 2017-10-24 | 2019-04-30 | 广东亿迅科技有限公司 | A kind of the real-time messages method for pushing and device of distribution high concurrent |
| CN109660607B (en) * | 2018-12-05 | 2021-08-27 | 北京金山云网络技术有限公司 | Service request distribution method, service request receiving method, service request distribution device, service request receiving device and server cluster |
| CN109660607A (en) * | 2018-12-05 | 2019-04-19 | 北京金山云网络技术有限公司 | A kind of service request distribution method, method of reseptance, device and server cluster |
| CN111385323A (en) * | 2018-12-28 | 2020-07-07 | 中国移动通信集团江西有限公司 | EJB service processing method, device, equipment and medium |
| CN111385324A (en) * | 2018-12-28 | 2020-07-07 | 广州市百果园信息技术有限公司 | Data communication method, device, equipment and storage medium |
| CN111385323B (en) * | 2018-12-28 | 2023-04-18 | 中国移动通信集团江西有限公司 | EJB service processing method, device, equipment and medium |
| CN111722920A (en) * | 2019-03-22 | 2020-09-29 | 鼎捷软件股份有限公司 | Load control method |
| CN111722920B (en) * | 2019-03-22 | 2024-06-21 | 鼎捷软件股份有限公司 | Load control method |
| CN110351342A (en) * | 2019-06-20 | 2019-10-18 | 平安科技（深圳）有限公司 | Service order processing method, device, computer equipment and storage medium |
| CN110401708A (en) * | 2019-07-23 | 2019-11-01 | 中南民族大学 | Session processing system and method based on server load state |
| CN110401708B (en) * | 2019-07-23 | 2021-11-23 | 中南民族大学 | Session processing system and method based on server load state |
| CN110417886A (en) * | 2019-07-29 | 2019-11-05 | 广州竞远安全技术股份有限公司 | A kind of load-balancing method of integrated service, apparatus and system |
| CN110677353A (en) * | 2019-09-06 | 2020-01-10 | 中国平安财产保险股份有限公司 | Data access method and system |
| CN113055427A (en) * | 2019-12-28 | 2021-06-29 | 浙江宇视科技有限公司 | Service-based server cluster access method and device |
| CN113055427B (en) * | 2019-12-28 | 2022-12-23 | 浙江宇视科技有限公司 | Service-based server cluster access method and device |
| CN111787048A (en) * | 2020-04-28 | 2020-10-16 | 北京沃东天骏信息技术有限公司 | Terminal device connection method, scheduling server and Internet of things system |
| CN111787048B (en) * | 2020-04-28 | 2023-08-04 | 北京沃东天骏信息技术有限公司 | Connection method of terminal equipment, scheduling server and Internet of things system |
| CN111552748A (en) * | 2020-05-08 | 2020-08-18 | 深圳知路科技有限公司 | Data processing method, device and system |
| CN113691573A (en) * | 2020-05-19 | 2021-11-23 | 深圳市理邦精密仪器股份有限公司 | Monitoring method, equipment, system and storage device of medical monitoring system |
| CN112383632A (en) * | 2020-11-17 | 2021-02-19 | 珠海大横琴科技发展有限公司 | Load balancing method and device |
| CN113268343A (en) * | 2021-05-10 | 2021-08-17 | 北京邮电大学 | Load balancing system and method |
| CN113312154A (en) * | 2021-06-30 | 2021-08-27 | 北京微纳星空科技有限公司 | Method, system, equipment and storage medium for scheduling satellite service resources |
| CN113312154B (en) * | 2021-06-30 | 2022-06-07 | 北京微纳星空科技有限公司 | Method, system, equipment and storage medium for scheduling satellite service resources |
| CN114281376A (en) * | 2021-12-09 | 2022-04-05 | 上海卓悠网络科技有限公司 | Service-based hot upgrading method and equipment |
| CN114915656A (en) * | 2021-12-29 | 2022-08-16 | 南京四维智联科技有限公司 | Internet of vehicles terminal access method, device, storage medium and electronic equipment |
| CN114610461A (en) * | 2022-03-17 | 2022-06-10 | 北京火山引擎科技有限公司 | Task processing method and device |
| CN115277351A (en) * | 2022-07-27 | 2022-11-01 | 天翼云科技有限公司 | Distributed management system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104079630A (en) | Business server side load balancing method, client side, server side and system | |
| CN109618002B (en) | Micro-service gateway optimization method, device and storage medium | |
| CN112788074B (en) | Data transmitting method, processing method, receiving method, apparatus thereof, and storage medium | |
| CN102299959B (en) | Load balance realizing method of database cluster system and device | |
| CN102945175A (en) | Terminal software online upgrading system and method based on cloud computing environment | |
| CN102281190A (en) | Networking method for load balancing apparatus, server and client access method | |
| US20150215394A1 (en) | Load distribution method taking into account each node in multi-level hierarchy | |
| CN103118076A (en) | Upgraded server cluster system and load balancing method thereof | |
| US20160344582A1 (en) | Call home cluster | |
| CN109067869A (en) | The management method and device of micro services node in cloud computing system | |
| CN103188101A (en) | Distributed type collection scheduling method and device | |
| CN106713378B (en) | Method and system for providing service by multiple application servers | |
| US8606908B2 (en) | Wake-up server | |
| US10846788B1 (en) | Resource group traffic rate service | |
| CN113014611B (en) | Load balancing method and related equipment | |
| CN103414657A (en) | Cross-data-center resource scheduling method, super scheduling center and system | |
| WO2020036161A1 (en) | Communication system and communication method | |
| CN107005452A (en) | A kind of network function virtual resources processing method and virtual network function manager | |
| CN109756474A (en) | A kind of trans-regional call method of the service of electric power scheduling automatization system and device | |
| KR102389334B1 (en) | Virtual machine provisioning system and method for cloud service | |
| CN105656964B (en) | The implementation method and device of data-pushing | |
| CN105071965A (en) | Management system of network equipment | |
| CN109104482A (en) | A kind of distributed system of earth mat platform | |
| CN109412940A (en) | Router administration method and router management system | |
| CN103516628A (en) | Method, device and system of updating network strategy |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20141001 |
|
| WD01 | Invention patent application deemed withdrawn after publication |