CN113242307B - Service request processing method, device, server and storage medium - Google Patents
Service request processing method, device, server and storage medium Download PDFInfo
- Publication number
- CN113242307B CN113242307B CN202110538953.3A CN202110538953A CN113242307B CN 113242307 B CN113242307 B CN 113242307B CN 202110538953 A CN202110538953 A CN 202110538953A CN 113242307 B CN113242307 B CN 113242307B
- Authority
- CN
- China
- Prior art keywords
- server
- service request
- service
- heterogeneous
- determining
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The disclosure relates to a service request processing method, a device, a server and a storage medium, and relates to the technical field of Internet. The method comprises the following steps: receiving a first service request sent by a terminal; determining a service resource required by the first service request, and selecting a target server matched with the service resource from a server cluster, wherein the server cluster comprises heterogeneous servers and non-heterogeneous servers; processing the first service request through the target server to obtain a processing result; and sending the processing result to the terminal. According to the scheme, when the required resource amount of the service resource is large, the matched target server can be used for processing, and the first service request can be processed within the designated time, so that the algorithm in the target server is not required to be compressed, and the quality of the processing result of the first service request is ensured on the premise that the first service request is not delayed.
Description
Technical Field
The disclosure relates to the technical field of internet, and in particular relates to a service request processing method, a device, a server and a storage medium.
Background
Among the service requests processed by the server, there are long tail requests whose processing time is significantly longer than the average value. At present, when long-tail requests are processed, models for processing service requests in a server are generally compressed through algorithm optimization, so that the processing speed of the server is improved by reducing the calculated amount of the models in the server, and further the duration of processing the service requests by the server is shortened. However, during the compression of the model, the model is damaged, which results in a decrease in the accuracy of the model and a decrease in the processing effect of the service request.
Disclosure of Invention
The disclosure provides a service request processing method, a device, a server and a storage medium, which can improve the processing effect of a service request. The technical scheme of the present disclosure is as follows:
according to a first aspect of an embodiment of the present disclosure, there is provided a service request processing method, including:
receiving a first service request sent by a terminal;
determining service resources required by the first service request, and selecting a target server matched with the service resources from a server cluster, wherein the server cluster comprises heterogeneous servers and non-heterogeneous servers;
Processing the first service request through the target server to obtain a processing result;
and sending the processing result to the terminal.
In some embodiments, the selecting, from the server cluster, a target server that matches the service resource includes:
if the resource quantity of the service resource is larger than the preset resource quantity, selecting the heterogeneous server from the server cluster, and determining the heterogeneous server as the target server;
and if the resource quantity of the service resource is not greater than the preset resource quantity, selecting the non-heterogeneous server from the server cluster, and determining the non-heterogeneous server as the target server.
In some embodiments, the preset amount of resources is determined by:
determining the maximum delay amount supported by the server cluster, wherein the maximum delay amount is the longest time length of the allowed delay of the server cluster;
determining the fastest processing speed of the non-heterogeneous server for processing a service request;
determining a maximum service resource supported by the non-heterogeneous server based on the maximum delay amount and the fastest processing speed;
and determining the number of the maximum service resources as the preset resource amount.
In some embodiments, the method further comprises:
determining the proportion of different types of service requests received by the server cluster, wherein the different types of service requests comprise service requests with processing time lengths exceeding a preset time length of the non-heterogeneous server and service requests with processing time lengths not exceeding the preset time length;
based on the ratio, a ratio of the number of heterogeneous servers and the number of non-heterogeneous servers is determined.
In some embodiments, the determining the service resource required by the first service request, selecting a target server matching the service resource from a server cluster, includes:
forwarding the first service request to the non-heterogeneous server, wherein the non-heterogeneous server is used for determining service resources required by the first service request, and selecting a target server matched with the service resources from a server cluster.
In some embodiments, the first service request is used for requesting to query a database for target data, and the determining the service resource required by the first service request includes:
determining a target database corresponding to the first service request;
determining data to be queried, which need to be traversed when querying the target data, from the database;
And determining the quantity of the data to be queried as the service resource required by the first service request.
In some embodiments, the processing, by the target server, the first service request to obtain a processing result includes:
determining target port information of the target server;
modifying the port information of the first service request into the target port information to obtain a second service request;
the second service request is sent to the target server, and the second service request is used for processing the second service request by the target server, so that the processing result is obtained;
and receiving the processing result sent by the target server.
According to a second aspect of embodiments of the present disclosure, there is provided a service request processing apparatus, the apparatus including:
a receiving unit configured to perform a first service request transmitted by a receiving terminal;
a first determining unit configured to perform determining a service resource required for the first service request, and select a target server matching the service resource from a server cluster, the server cluster including heterogeneous servers and non-heterogeneous servers;
The processing unit is configured to execute processing of the first service request through the target server to obtain a processing result;
and a transmitting unit configured to perform transmission of the processing result to the terminal.
In some embodiments, the first determining unit includes:
a first determining subunit configured to perform selecting the heterogeneous server from the server cluster and determine the heterogeneous server as the target server if the resource amount of the service resource is greater than a preset resource amount;
and a second determining subunit configured to perform selecting the non-heterogeneous server from the server cluster and determine the non-heterogeneous server as the target server if the resource amount of the service resource is not greater than the preset resource amount.
In some embodiments, the apparatus further comprises:
a second determining unit configured to perform determining a maximum delay amount supported by the server cluster, the maximum delay amount being a longest duration of a delay allowed by the server cluster;
a third determining unit configured to perform determining a fastest processing speed of the non-heterogeneous server to process a service request;
A fourth determining unit configured to perform determining a maximum service resource supported by the non-heterogeneous server based on the maximum delay amount and the fastest processing speed;
and a fifth determining unit configured to perform determination of the number of maximum service resources as the preset resource amount.
In some embodiments, the apparatus further comprises:
a sixth determining unit configured to perform determining a proportion of different types of service requests received by the server cluster, where the different types of service requests include service requests whose processing time periods exceed a preset time period and service requests whose processing time periods do not exceed the preset time period;
a seventh determination unit configured to perform determining a ratio of the number of heterogeneous servers and the number of non-heterogeneous servers based on the ratio.
In some embodiments, the first determining unit includes:
and a forwarding subunit configured to perform forwarding of the first service request to the non-heterogeneous server, where the non-heterogeneous server is configured to determine a service resource required by the first service request, and select a target server matching the service resource from a server cluster.
In some embodiments, the first service request is for requesting a query of a database for target data, and the first determining unit includes:
a third determining subunit configured to perform determining a target database corresponding to the first service request;
a query subunit configured to execute data to be queried, which needs to be traversed when determining to query the target data from the database;
and a fourth determining subunit configured to perform determining the amount of the data to be queried as a service resource required by the first service request.
In some embodiments, the processing unit comprises:
a fifth determination subunit configured to perform determination of target port information of the target server;
a modification subunit configured to perform modification of the port information of the first service request to the target port information, to obtain a second service request;
the sending subunit is configured to send the second service request to the target server, wherein the second service request is used for processing the second service request by the target server to obtain the processing result;
and receiving the processing result sent by the target server.
According to a third aspect of embodiments of the present disclosure, there is provided a server comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the service request processing method according to any of the above aspects.
According to a fourth aspect of embodiments of the present disclosure, there is provided a computer readable storage medium, which when executed by a processor of a server, causes the server to perform the service request processing method as set forth in any one of the above aspects.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product comprising computer program instructions which, when executed by a processor, implement a service request processing method as described in any of the above aspects.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
in the embodiment of the disclosure, the service resource required by the first service request is determined, so that the selected target server for processing the first service request is matched with the service resource required by the first service request, and thus when the amount of the required service resource is large, the matched target server can be used for processing, the first service request can be processed within a designated time, and the algorithm in the target server is not required to be compressed, so that the quality of the processing result of the first service request is ensured on the premise of ensuring that the first service request is not delayed.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.
Fig. 1 is an implementation environment diagram illustrating a service request processing method according to an exemplary embodiment.
Fig. 2 is a schematic diagram illustrating a structure of a server cluster according to an exemplary embodiment.
Fig. 3 is a schematic diagram illustrating a structure of a server cluster according to an exemplary embodiment.
Fig. 4 is a schematic diagram illustrating a structure of a server cluster according to an exemplary embodiment.
Fig. 5 is a flowchart illustrating a service request processing method according to an exemplary embodiment.
Fig. 6 is a flowchart illustrating a service request processing method according to an exemplary embodiment.
Fig. 7 is a flowchart illustrating a service request processing method according to an exemplary embodiment.
Fig. 8 is a flowchart illustrating a service request processing method according to an exemplary embodiment.
Fig. 9 is a flowchart illustrating a service request processing method according to an exemplary embodiment.
Fig. 10 is a flowchart illustrating a service request processing method according to an exemplary embodiment.
Fig. 11 is a flowchart illustrating a service request processing method according to an exemplary embodiment.
Fig. 12 is a block diagram illustrating a service request processing apparatus according to an exemplary embodiment.
Fig. 13 is a block diagram of a server, according to an example embodiment.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims. In addition, the resource and data information to which the present disclosure relates may be resource and data information that is authorized by a user or sufficiently authorized by parties.
Fig. 1 is an implementation environment diagram illustrating a service request processing method according to an exemplary embodiment. Referring to fig. 1, the implementation environment includes a terminal 10 and a server cluster 20. Wherein the terminal 10 and the server cluster 20 are connected through a wireless or wired network.
The terminal 10 installs thereon an application program that is served by the server cluster 20, and the terminal 10 can send a service request to the server cluster 20 through the application program. Accordingly, the server cluster 20 can receive the service request sent by the terminal 10, provide a service resource for the service request, process the service request through the service resource, obtain a processing result of the service request, and send the processing result to the terminal 10.
In some embodiments, referring to fig. 2, the server cluster 20 includes non-heterogeneous servers and heterogeneous servers. The non-heterogeneous server and the heterogeneous server are connected through a wireless or wired network. In some embodiments, the server cluster 20 includes load balancing servers, non-heterogeneous servers, and heterogeneous servers. Referring to fig. 3, the load balancing server is connected with the non-heterogeneous server through a wireless or wired network, and the non-heterogeneous server is also connected with the heterogeneous server through the wireless or wired network. Alternatively, referring to fig. 4, the load balancing server is connected to the heterogeneous server and the non-heterogeneous server by wireless or wired connection, respectively.
In the disclosed embodiment, the terminal 10 generates a first service request and sends the first service request to the server cluster 20. The first service request includes an identification of a service cluster. The identification of the service cluster is used to indicate the identification of the service cluster. For example, the identification of the server cluster 20 is an IP (Internet Protocol Address ) address, port information, etc. of the server cluster 20.
The present disclosure is applied to various scenarios of sending a service request to a server, and the following application scenarios are taken as examples.
Scene one, the data query scene.
In this scenario, the terminal 10 receives a tag of target data to be queried, generates a first service request based on the tag of the target data, sends the first service request to the server cluster 20, and queries the target data based on the first service request through the server cluster 20.
Wherein the data is text data, image data or video data. The first service request is for requesting query target data. Correspondingly, the first service request carries a data tag of the target data to be queried. The data tag is a tag formed by information such as keywords, descriptive text, titles and the like of data. For example, if the first service request is a service request for querying target video data, the first service request carries information such as a title of the target video data to be queried.
Scene two, account registration scene.
In this scenario, the terminal 10 receives registration information, generates a first service request based on the registration information, sends the first service request to the server cluster 20, and completes account registration based on the first service request through the server cluster 20.
The registration information comprises account identification, account name, user information of a user using the account, registration time and the like of an account to be registered. The first server is used for requesting to store the registration information in the server corresponding to the application program and returning a prompt message of successful registration or failure registration.
Scene three, video release scene.
In this scenario, the terminal 10 determines video data to be published, generates a first service request based on the video data, sends the first service request to the server cluster 20, performs coding processing on the video data in the first service request through the server cluster 20, and when the video data needs to be pushed, pushes the video data to other terminals 10 through the server cluster 20, and the other terminals 10 receive the video data pushed by the server cluster 20, perform decoding rendering on the video data, and display the video data in a display interface.
In some embodiments, the terminal 10 is at least one of a cell phone, tablet, PC (Personal Computer) device, and the like. The server cluster 20 is a server cluster 20 composed of a plurality of servers. Wherein the servers in the server cluster 20 may be at least one of a cloud server, a cloud computing platform, and a virtualization center.
Fig. 5 is a flowchart illustrating a service request processing method according to an exemplary embodiment, which is applied to a terminal as shown in fig. 5, and includes the steps of:
step S51, a first service request sent by a terminal is received.
In step S52, a service resource required by the first service request is determined, and a target server matching the service resource is selected from a server cluster, where the server cluster includes heterogeneous servers and non-heterogeneous servers.
Step S53, the target server processes the first service request to obtain a processing result.
Step S54, transmitting the processing result to the terminal.
In some embodiments, the selecting, from the cluster of servers, a target server that matches the service resource includes:
if the resource quantity of the service resource is larger than the preset resource quantity, selecting the heterogeneous server from the server cluster, and determining the heterogeneous server as the target server;
And if the resource quantity of the service resource is not greater than the preset resource quantity, selecting the non-heterogeneous server from the server cluster, and determining the non-heterogeneous server as the target server.
In some embodiments, the preset amount of resources is determined by:
determining the maximum delay amount supported by the server cluster, wherein the maximum delay amount is the longest time of the allowed delay of the server cluster;
determining a fastest processing speed of the non-heterogeneous server for processing the service request;
determining a maximum service resource supported by the non-heterogeneous server based on the maximum amount of delay and the fastest processing speed;
and determining the number of the maximum service resources as the preset resource amount.
In some embodiments, the method further comprises:
determining the proportion of different types of service requests received by the server cluster, wherein the different types of service requests comprise service requests with processing time lengths exceeding a preset time length of the non-heterogeneous server and service requests with processing time lengths not exceeding the preset time length;
based on the ratio, a ratio of the number of heterogeneous servers to the number of non-heterogeneous servers is determined.
In some embodiments, the determining the service resource required for the first service request, selecting a target server from the server cluster that matches the service resource, includes:
And forwarding the first service request to the non-heterogeneous server, wherein the non-heterogeneous server is used for determining service resources required by the first service request, and selecting a target server matched with the service resources from a server cluster.
In some embodiments, the first service request is for requesting a query for target data in a database, and the determining the service resources required for the first service request includes:
determining a target database corresponding to the first service request;
determining data to be queried, which need to be traversed when querying the target data, from the database;
and determining the quantity of the data to be queried as the service resource required by the first service request.
In some embodiments, the processing, by the target server, the first service request to obtain a processing result includes:
determining target port information of the target server;
modifying the port information of the first service request into the target port information to obtain a second service request;
the second service request is sent to the target server, and the second service request is used for processing the second service request by the target server, so that a processing result is obtained;
and receiving the processing result sent by the target server.
In the embodiment of the disclosure, the service resource required by the first service request is determined, so that the selected target server for processing the first service request is matched with the service resource required by the first service request, and thus when the amount of the required service resource is large, the matched target server can be used for processing, the first service request can be processed within a designated time, and the algorithm in the target server is not required to be compressed, so that the quality of the processing result of the first service request is ensured on the premise of ensuring that the first service request is not delayed.
In some implementations, the server cluster includes a load balancing server, a heterogeneous server, and a non-heterogeneous server. The server for processing the first service request is determined from the heterogeneous server and the non-heterogeneous server by the load balancing server. Referring to fig. 6, fig. 6 is a flowchart illustrating a service request processing method according to an exemplary embodiment, and as shown in fig. 6, the service request processing method is applied to a server cluster, and includes the steps of:
in step S61, the terminal transmits a first service request to the load balancing server.
And the terminal generates a first service request according to the task which needs to be processed currently, and sends the first service request to the load balancing server. The first service request is a request for performing a corresponding task by the load balancing server. For example, the first service request is a request for querying target data.
In step S62, the load balancing server receives a first service request sent by the terminal.
It should be noted that the server cluster may include a load balancing server, at least one non-heterogeneous server, and at least one heterogeneous server. The load balancing server is connected with the at least one non-heterogeneous server and the at least one heterogeneous server through a wireless or wired network.
In step S63, the load balancing server determines the service resources required for the first service request.
The service resource is a service resource required by the server to process the first service request. The service resource is a time resource required by the server to process the first service request through the processing resource of the server; or the service resource is the processing resource of the server occupied when the server processes the first service request. In the embodiments of the present disclosure, this is not particularly limited.
In some embodiments, the first service request is used for requesting to query the database for the target data, and the resource amount of the service resource corresponding to the first service request is the data amount of the data to be queried that needs to be traversed in the process of querying the database by the first service request. Accordingly, this step is achieved by the following steps (1) - (3), comprising:
(1) The load balancing server determines a target database corresponding to the first service request.
In this step, the load balancing server determines, according to the first service request, a database to be queried for the first service request. In some embodiments, the first service request carries a database identifier of a database, the load balancing server analyzes the first service request to obtain the database identifier of the database, and determines a database corresponding to the first service request according to the database identifier.
(2) And the load balancing server determines the data to be queried, which need to be traversed when querying the target data, from the database.
When the target data is queried, all data in the database can be traversed, or the data range of the target data can be determined from the database, and the data to be queried can be queried from the data range.
Correspondingly, in the first implementation manner, the load balancing server determines all data in the database as data to be queried to be traversed. In a second implementation manner, the load balancing server determines a data range where the target data is located from the database, and determines the data in the data range as the data to be queried. For example, the database stores image data and video data, the first service request is used for querying an image including a target object, and the load balancing server determines that the target data is in the image data from the stored image data and video data, and determines the image data as data to be queried.
(3) The load balancing determines the amount of the data to be queried as the service resources required by the first service request.
When data is queried from the database, the data in the database generally needs to be traversed to query the target data corresponding to the first service request. Thus, the greater the amount of data to be queried, the longer the traversal time, such that the greater the service resources required. Therefore, the amount of data to be queried is determined in this step as the service resources required for the first service request.
In some embodiments, the load balancing server directly determines the data amount of the data to be queried as the service resource required for the first service request. In some embodiments, the load balancing server determines a duration required to traverse the data to be queried based on the amount of the data to be queried, and determines the duration as a service resource required for the first service request.
For example, if the first service request is to query the maximum k number of the data corresponding to the target tag, after the first service is sent to reach the load balancing server, the load balancing server searches the data corresponding to the target tag from the target database; counting the number of data corresponding to the target labels as N; the amount of service resources required for the first service request is N.
It should be noted that the service resource is a resource required when any type of server in the server cluster processes the first service request. For example, the service resource is a service resource required by a non-heterogeneous server in the server cluster to process the first service request, or the service resource is a service resource required by a heterogeneous server in the server cluster to process the first service request. Correspondingly, the performance information of the non-heterogeneous server or the performance information of the heterogeneous server is stored in the load balancing server. The load balancing server determines service resources required by the first service request based on the performance information of the non-heterogeneous server or the performance information of the heterogeneous server. The performance information includes information such as processing speed when the heterogeneous server or the non-heterogeneous server determines to process the service request, processing resources allocated to the service request, and the like.
In step S64, the load balancing server selects a target server matching the service resource from among the heterogeneous servers and the non-heterogeneous servers.
In this step, referring to fig. 7, the load balancing server compares the resource amount of the service resource with a preset resource amount, and determines, from the server cluster, a target server that matches the service resource according to the comparison result.
If the resource quantity of the service resource is larger than the preset resource quantity, the load balancing server selects the heterogeneous server from the server cluster, and the heterogeneous server is determined to be the target server; if the resource amount of the service resource is not greater than the preset resource amount, the load balancing server selects the non-heterogeneous server from the server cluster, and the non-heterogeneous server is determined to be the target server.
It should be noted that, when the number of heterogeneous servers or non-heterogeneous servers in the server cluster is 1, the load balancing server directly determines the heterogeneous server or the non-heterogeneous server as the target server. In the case that the number of heterogeneous servers or non-heterogeneous servers in the server cluster is a plurality, the load balancing server determines a server type for processing the first service request, and then determines a target server from the corresponding server types. For example, the load balancing server determines that the server type for processing the first service request is a non-heterogeneous server, and if the number of non-heterogeneous servers in the server cluster is a plurality of non-heterogeneous servers, the load balancing server determines the target server from the plurality of non-heterogeneous servers.
The process of determining the target server by the load balancing server from the plurality of non-heterogeneous servers may be: the load balancing server records a history service record of each non-heterogeneous server, determines the current processing task amount of each non-heterogeneous server according to the history service record, and determines the non-heterogeneous server with the minimum current task amount as a target server.
The process of determining the target server from the plurality of heterogeneous servers by the load balancing server is similar to the process of determining the target server from the plurality of non-heterogeneous servers by the load balancing server, and will not be described in detail herein.
In addition, the preset resource amount is set as needed, and in the embodiment of the present disclosure, the preset resource amount is not particularly limited. In some embodiments, the preset amount of resources is determined based on performance of the non-heterogeneous server. Before this step, the load balancing server determines the preset amount of resources. The preset resource amount is determined by the following steps (1) - (4), comprising:
(1) The load balancing server determines the maximum amount of delay supported by the server cluster.
Wherein the maximum delay amount is the longest duration of the allowed delay of the server cluster.
(2) The load balancing server determines the fastest processing speed for the non-heterogeneous server to handle the service request.
Because the performance of the non-heterogeneous servers in the server cluster is lower than that of the heterogeneous servers, that is, the processing speed of the non-heterogeneous servers for processing the service requests is lower than that of the heterogeneous servers. Therefore, in the process of determining the preset resource amount, in order to determine that the non-heterogeneous server can process the service request within the preset resource amount, in this step, the processing speed of the non-heterogeneous server to process the service request is determined.
The load balancing server obtains performance parameters of the non-heterogeneous server, and determines the fastest processing speed of the non-heterogeneous server for processing the service request from the performance parameters.
(3) The load balancing server determines the maximum service resources supported by the non-heterogeneous server based on the maximum amount of delay and the fastest processing speed.
The maximum service resource is the maximum resource amount when the Fischer-Tropsch purchase server processes simultaneously. In this step, the load balancing server determines a duration of processing each server request based on the fastest processing speed. The maximum time length of the allowable delay supported by the server cluster is the sum of the processing time length of the current task and the processing time length of the task before the current task. Correspondingly, the maximum delay l=a+b×n. Wherein L is the maximum delay, A is the time length required by the server cluster to process the current task, B is the time length required by the server cluster to process the task before the current task, and N is the number of tasks before the current task. Accordingly, the maximum service resource nmax= (L-a)/B.
(4) The load balancing server determines the number of the maximum service resources as the preset resource amount.
It should be noted that, the process of determining the preset resource amount may be determined by the load balancing server, or may be determined by another server. If the process of determining the preset resource amount is determined by other servers, the load balancing server directly acquires the preset resource amount from the other servers. The process of determining the preset resource amount by the other servers is similar to the process of determining the preset resource amount by the load balancing server in the steps (1) - (4), and will not be repeated here.
The non-heterogeneous server is a general server capable of processing service requests, and the heterogeneous server is a server which is formed by splitting hardware of the server into a plurality of different units and respectively arranged in a rack, and achieves a service effect through data communication. The heterogeneous servers perform better than non-heterogeneous servers. In addition, the number of servers of any type in the server cluster is set according to needs, and in the embodiment of the present disclosure, the number of servers in the server cluster is not specifically limited.
In some embodiments, the ratio between heterogeneous and non-heterogeneous servers in the server cluster is determined based on the ratio of long-tail requests in service requests received by the server cluster. The server cluster determines the proportion of different types of service requests received by the server cluster, wherein the different types of service requests comprise service requests with processing time lengths exceeding a preset time length of the non-heterogeneous server and service requests with processing time lengths not exceeding the preset time length; based on the ratio, a ratio of the number of heterogeneous servers to the number of non-heterogeneous servers is determined. For example, if the ratio of the long-tail request in the service requests received by the server cluster is 1%, the heterogeneous servers and the non-heterogeneous servers are added into the server cluster according to the ratio of 1:100.
In the implementation manner, the ratio of the long-tail requests in the service requests received by the server cluster determines the proportion relation between the heterogeneous servers and the non-heterogeneous servers in the server cluster, so that the servers in the server cluster can proportion the number of the heterogeneous servers according to the number of the long-tail requests to be processed in the service requests, thereby ensuring that the heterogeneous servers in the server cluster can process the long-tail requests in time and not wasting the resources of the heterogeneous servers.
In step S65, the load balancing server processes the first service request through the target server, to obtain a processing result.
In this step, the load balancing server forwards the first service request to the target server, and the target server receives the first service request forwarded by the load balancing server, and processes the first service request to obtain a processing result. The load balancing server directly forwards the first service request to the target server. Or the load balancing server modifies the first service request to obtain a second service request, and sends the second service request to the target server. The process is realized by the following steps (1) - (6), comprising:
(1) The load balancing server determines target port information of the target server.
In this step, the load balancing server determines server information corresponding to the target server from the server information stored in the server information, and analyzes the target port information of the target server from the server information.
(2) The load balancing server modifies the port information of the first service request into the target port information to obtain a second service request.
The port information of the first service request is used to indicate the port of the server to which the first service request is sent. The original port information in the first service request is port information of the load balancing server. In this step, the load balancing server modifies the original port information in the first service request to the target port information of the target server, so as to obtain the second service request.
(3) The load balancing server sends the second service request to the target server.
The second service request is used for processing the second service request by the target server, and the processing result is obtained.
(4) And the target server receives the second service request and processes the second service request to obtain a processing result.
Because the second service request and the first service request only have the difference of port information, the tasks of the two requests are the same, and therefore, in the step, the processing result obtained by processing the second service request should be the same processing result corresponding to the first service request.
(5) The target server sends the processing result to the load balancing server.
In some embodiments, when the target server modifies the port information of the first service request, the port information of the load server is further used as a port corresponding to the returned result. Correspondingly, in the step, the target server determines the port information of the server to receive the processing result according to the second service request, and returns the processing result based on the port information.
It should be noted that, after the target server obtains the processing result, the target server may directly send the processing result to the terminal. Step the target server does not perform steps (5) and (6) and step S56 is replaced with the target server transmitting the processing result to the terminal
(6) And the load balancing server receives the processing result sent by the target server.
In the implementation manner, the processing of the first service request through the target server is achieved by modifying the port information in the first service request, and a processing result is obtained, so that the processing of the first service request through the target server is achieved.
In step S66, the load balancing server transmits the processing result to the terminal.
In the embodiment of the disclosure, the service resource required by the first service request is determined, so that the selected target server for processing the first service request is matched with the service resource required by the first service request, and thus when the amount of the required service resource is large, the matched target server can be used for processing, the first service request can be processed within a designated time, and the algorithm in the target server is not required to be compressed, so that the quality of the processing result of the first service request is ensured on the premise of ensuring that the first service request is not delayed.
In some implementations, the server cluster includes a load balancing server, a heterogeneous server, and a non-heterogeneous server. Referring to fig. 8, the load balancing server forwards the first service request to the non-heterogeneous server, where the non-heterogeneous server is configured to determine a service resource required by the first service request, and select a target server matching the service resource from a server cluster. A server for processing the first service request is determined from the non-heterogeneous servers by the load balancing server, and whether the first service request needs to be forwarded to the heterogeneous servers is determined by the non-heterogeneous servers. Referring to fig. 9, fig. 9 is a flowchart illustrating a service request processing method according to an exemplary embodiment, and as shown in fig. 9, the service request processing method is applied to a server cluster, and includes the steps of:
In step S91, the terminal transmits a first service request to the load balancing server.
This step is similar to step S61 and will not be described here again.
In step S92, the load balancing server receives a first service request sent by the terminal.
This step is similar to step S62 and will not be described here again.
In step S93, the load balancing server forwards the first service request to the non-heterogeneous server.
The procedure of determining the target server from the non-heterogeneous servers in this step is similar to that in step S64, and will not be described here again.
In step S94, the non-heterogeneous server determines the service resources required for the first service request.
This step is similar to step S63 and will not be described here again.
In step S95, if the resource amount of the service resource is greater than the preset resource amount, the non-heterogeneous server determines the heterogeneous server as the target server.
In step S96, if the resource amount of the service resource is not greater than the preset resource amount, the non-heterogeneous server determines the non-heterogeneous server as the target server.
In step S95 and step S96, the process of selecting the target server matched with the service resource from the heterogeneous server and the non-heterogeneous server by the load balancing server is similar to that in step S64, and will not be described herein.
In step S97, the non-heterogeneous server processes the first service request through the target server, to obtain a processing result.
This step is similar to step S65 and will not be described here again.
In step S98, the non-heterogeneous server transmits the processing result to the terminal.
This step is similar to step S66 and will not be described here again.
In the embodiment of the disclosure, the service resource required by the first service request is determined, so that the selected target server for processing the first service request is matched with the service resource required by the first service request, and thus when the amount of the required service resource is large, the matched target server can be used for processing, the first service request can be processed within a designated time, and the algorithm in the target server is not required to be compressed, so that the quality of the processing result of the first service request is ensured on the premise of ensuring that the first service request is not delayed.
In addition, in the implementation manner, the first server is firstly sent to the non-heterogeneous server through the load balancing server, and the relation between the resource quantity of the service resource required by the first service request and the preset resource quantity is determined through the non-heterogeneous server, so that whether the first server is processed in the current server or forwarded to the non-heterogeneous server for processing is determined, compression of an algorithm in the target server is not needed, and the quality of a processing result of the first service request is guaranteed on the premise that the first service request is not delayed.
In some implementations, heterogeneous servers and non-heterogeneous servers are included in a server cluster. Referring to fig. 10, a terminal transmits a first service request to a non-heterogeneous server for determining a service resource required for the first service request, and selects a target server matching the service resource from a server cluster. The first service request is received by the non-heterogeneous server, and whether the first service request needs to be forwarded to the heterogeneous server is determined. Referring to fig. 11, fig. 11 is a flowchart illustrating a service request processing method according to an exemplary embodiment, and as shown in fig. 11, the service request processing method is applied to a server cluster, and includes the steps of:
in step S111, the terminal transmits a first service request to the non-heterogeneous server.
This step is similar to step S61 and will not be described here again.
It should be noted that, in this step, the terminal sends a first service request to a non-heterogeneous server in the server cluster. In some embodiments, after the terminal generates the first service request, the first service request is randomly sent to a non-heterogeneous server in the server cluster. In some embodiments, the terminal determines the non-heterogeneous server according to the type of the first task request based on the generated first task request.
Another point to be noted is that the terminal can also determine the type of service request, and determine to the heterogeneous server and the non-heterogeneous server according to the type of service request. If the service request is determined to be sent to the non-heterogeneous server according to the type of the service request, step S112 is executed; if the service request is determined to be sent to the heterogeneous server according to the type of the service request, the heterogeneous server is determined to be the target server, and step S116 is performed.
In step S112, the non-heterogeneous server receives a first service request transmitted by the terminal.
This step is similar to step S62 and will not be described here again.
In step S113, the non-heterogeneous server determines the service resources required for the first service request.
This step is similar to step S63 and will not be described here again.
In step S114, if the resource amount of the service resource is greater than the preset resource amount, the non-heterogeneous server determines the heterogeneous server as the target server.
In step S115, if the resource amount of the service resource is not greater than the preset resource amount, the non-heterogeneous server determines the non-heterogeneous server as the target server.
Step S114 and step S115 are similar to step S66, and are not described here again.
In step S116, the non-heterogeneous server processes the first service request through the target server, to obtain a processing result.
This step is similar to step S65 and will not be described here again.
In step S117, the non-heterogeneous server transmits the processing result to the terminal.
This step is similar to step S66 and will not be described here again.
In the embodiment of the disclosure, the service resource required by the first service request is determined, so that the selected target server for processing the first service request is matched with the service resource required by the first service request, and thus when the amount of the required service resource is large, the matched target server can be used for processing, the first service request can be processed within a designated time, and the algorithm in the target server is not required to be compressed, so that the quality of the processing result of the first service request is ensured on the premise of ensuring that the first service request is not delayed.
In addition, in the implementation manner, the relationship between the resource quantity of the service resource required by the first service request and the preset resource quantity is determined through the non-heterogeneous server, so that whether the first server is processed or forwarded to the non-heterogeneous server for processing in the current server is determined, compression of an algorithm in the target server is not needed, and the quality of a processing result of the first service request is guaranteed on the premise that the first service request is not delayed.
Fig. 12 is a block diagram illustrating a service request processing apparatus according to an exemplary embodiment. As shown in fig. 12, the apparatus includes:
a receiving unit 1201 configured to perform a first service request transmitted by a receiving terminal;
a first determining unit 1202 configured to perform determining a service resource required for the first service request, and select a target server matching the service resource from a server cluster, the server cluster including heterogeneous servers and non-heterogeneous servers;
a processing unit 1203 configured to perform processing of the first service request by the target server to obtain a processing result;
a transmitting unit 1204 configured to perform transmission of the processing result to the terminal.
In some embodiments, the first determining unit 1202 includes:
a first determining subunit configured to perform selecting the heterogeneous server from the server cluster and determine the heterogeneous server as the target server if the resource amount of the service resource is greater than a preset resource amount;
and a second determining subunit configured to perform selecting the non-heterogeneous server from the server cluster and determine the non-heterogeneous server as the target server if the resource amount of the service resource is not greater than the preset resource amount.
In some embodiments, the apparatus further comprises:
a second determining unit configured to perform determining a maximum delay amount supported by the server cluster, the maximum delay amount being a longest duration of allowable delays of the server cluster;
a third determining unit configured to perform determining a fastest processing speed of the non-heterogeneous server to process the service request;
a fourth determining unit configured to perform determining a maximum service resource supported by the non-heterogeneous server based on the maximum delay amount and the fastest processing speed;
and a fifth determining unit configured to perform determining the number of the maximum service resources as the preset resource amount.
In some embodiments, the apparatus further comprises:
a sixth determining unit configured to perform determining a proportion of different types of service requests received by the server cluster, where the different types of service requests include service requests whose processing time period exceeds a preset time period and service requests whose processing time period does not exceed the preset time period;
a seventh determining unit configured to perform determining a ratio of the number of the heterogeneous servers and the non-heterogeneous servers based on the ratio.
In some embodiments, the first determining unit 1202 includes:
And a forwarding subunit configured to perform forwarding of the first service request to the non-heterogeneous server, where the non-heterogeneous server is configured to determine a service resource required by the first service request, and select a target server matching the service resource from the server cluster.
In some embodiments, the first service request is for requesting to query the database for target data, the first determining unit 1202 includes:
a third determining subunit configured to perform determining a target database corresponding to the first service request;
a query subunit configured to execute data to be queried, which needs to be traversed when determining to query the target data from the database;
and a fourth determination subunit configured to perform determining the amount of the data to be queried as a service resource required for the first service request.
In some embodiments, the processing unit 1203 includes:
a fifth determination subunit configured to perform determination of the target port information of the target server;
a modification subunit configured to perform modification of the port information of the first service request to the target port information, resulting in a second service request;
a sending subunit, configured to send the second service request to the target server, where the second service request is used for the target server to process the second service request, so as to obtain the processing result;
And receiving the processing result sent by the target server.
In the embodiment of the disclosure, the service resource required by the first service request is determined, so that the selected target server for processing the first service request is matched with the service resource required by the first service request, and thus when the amount of the required service resource is large, the matched target server can be used for processing, the first service request can be processed within a designated time, and the algorithm in the target server is not required to be compressed, so that the quality of the processing result of the first service request is ensured on the premise of ensuring that the first service request is not delayed.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
Fig. 13 shows a block diagram of a server 1300 provided by an exemplary embodiment of the present disclosure. In some embodiments, the server 1300 may have a relatively large difference due to different configurations or performances, including one or more processors (Central Processing Units, CPU) 1301 and one or more memories 1302, where the memory 1301 stores at least one instruction, and the at least one instruction is loaded and executed by the processor 1301 to implement the service request processing method provided in the above method embodiments. Of course, in some embodiments, the server 1300 further includes a wired or wireless network interface, a keyboard, an input/output interface, and other components for implementing the functions of the device, which are not described herein.
In an exemplary embodiment, there is also provided a computer-readable storage medium, which when executed by a processor of a terminal, causes the terminal to perform the service request processing method in the above-described embodiment.
In an exemplary embodiment, a computer program product is also provided, which comprises a computer program/instruction which, when executed by a processor, implements the service request handling method in the above-described embodiments.
In some embodiments, the computer program related to the embodiments of the present disclosure may be deployed to be executed on one computer device or on multiple computer devices located at one site, or alternatively, may be executed on multiple computer devices distributed across multiple sites and interconnected by a communication network, where the multiple computer devices distributed across multiple sites and interconnected by a communication network may constitute a blockchain system.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (12)
1. A method of service request handling, the method comprising:
receiving a first service request sent by a terminal;
determining service resources required by the first service request, if the resource quantity of the service resources is larger than a preset resource quantity, selecting a heterogeneous server from a server cluster, determining the heterogeneous server as a target server matched with the service resources, wherein the server cluster comprises the heterogeneous server and a non-heterogeneous server, and the service resources comprise time resources required by processing the first service request through processing resources or occupied processing resources when the first service request is processed;
if the resource amount of the service resource is not greater than the preset resource amount, selecting the non-heterogeneous server from the server cluster, and determining the non-heterogeneous server as the target server;
processing the first service request through the target server to obtain a processing result;
Sending the processing result to the terminal;
the preset resource amount is determined by the following method:
determining the maximum delay amount supported by the server cluster, wherein the maximum delay amount is the longest time length of the allowed delay of the server cluster;
acquiring performance parameters of the non-heterogeneous server, and determining the fastest processing speed of the non-heterogeneous server for processing a service request from the performance parameters;
determining a duration of processing each service request based on the fastest processing speed;
determining a maximum service resource supported by the non-heterogeneous server based on the maximum delay amount, a time length required by the server cluster to process a current task and a time length required by the server cluster to process a task before the current task, wherein the maximum service resource is the number of tasks before the current task, and the maximum service resource is the maximum resource amount when the non-heterogeneous server processes the tasks simultaneously;
and determining the number of the maximum service resources as the preset resource amount.
2. The method according to claim 1, wherein the method further comprises:
determining the proportion of different types of service requests received by the server cluster, wherein the different types of service requests comprise service requests with processing time lengths exceeding a preset time length of the non-heterogeneous server and service requests with processing time lengths not exceeding the preset time length;
Based on the ratio, a ratio of the number of heterogeneous servers and the number of non-heterogeneous servers is determined.
3. The method according to claim 1, wherein the method further comprises:
forwarding the first service request to the non-heterogeneous server, wherein the non-heterogeneous server is used for determining service resources required by the first service request, and selecting the target server matched with the service resources from the server cluster.
4. The method of claim 1, wherein the first service request is for requesting a query for target data in a database, and wherein the determining the service resources required by the first service request comprises:
determining a target database corresponding to the first service request;
determining data to be queried, which need to be traversed when querying the target data, from the database;
and determining the quantity of the data to be queried as the service resource required by the first service request.
5. The method of claim 1, wherein the processing, by the target server, the first service request to obtain a processing result includes:
determining target port information of the target server;
Modifying the port information of the first service request into the target port information to obtain a second service request;
the second service request is sent to the target server, and the second service request is used for processing the second service request by the target server, so that the processing result is obtained;
and receiving the processing result sent by the target server.
6. A service request processing apparatus, the apparatus comprising:
a receiving unit configured to perform a first service request transmitted by a receiving terminal;
a first determining unit including a first determining subunit and a second determining subunit, where the first determining subunit is configured to perform determining a service resource required by the first service request, and if a resource amount of the service resource is greater than a preset resource amount, select a heterogeneous server from a server cluster, and determine the heterogeneous server as a target server matched with the service resource, where the server cluster includes the heterogeneous server and a non-heterogeneous server, and the service resource includes a time resource required for processing the first service request by a processing resource, or a processing resource occupied when processing the first service request;
The second determining subunit is configured to perform, if the resource amount of the service resource is not greater than the preset resource amount, selecting the non-heterogeneous server from the server cluster, and determining the non-heterogeneous server as the target server;
the processing unit is configured to execute processing of the first service request through the target server to obtain a processing result;
a transmission unit configured to perform transmission of the processing result to the terminal;
a second determining unit configured to perform determining a maximum delay amount supported by the server cluster, the maximum delay amount being a longest duration of a delay allowed by the server cluster;
a third determining unit configured to perform acquisition of performance parameters of the non-heterogeneous server, and determine a fastest processing speed of the non-heterogeneous server to process a service request from the performance parameters;
a fourth determining unit configured to perform determining a time period for processing each service request based on the fastest processing speed;
determining a maximum service resource supported by the non-heterogeneous server based on the maximum delay amount, a time length required by the server cluster to process a current task and a time length required by the server cluster to process a task before the current task, wherein the maximum service resource is the number of tasks before the current task, and the maximum service resource is the maximum resource amount when the non-heterogeneous server processes the tasks simultaneously;
And a fifth determining unit configured to perform determination of the number of maximum service resources as the preset resource amount.
7. The apparatus of claim 6, wherein the apparatus further comprises:
a sixth determining unit configured to perform determining a proportion of different types of service requests received by the server cluster, where the different types of service requests include service requests whose processing time periods exceed a preset time period and service requests whose processing time periods do not exceed the preset time period;
a seventh determination unit configured to perform determining a ratio of the number of heterogeneous servers and the number of non-heterogeneous servers based on the ratio.
8. The apparatus according to claim 6, wherein the first determining unit includes:
and a forwarding subunit configured to perform forwarding of the first service request to the non-heterogeneous server, where the non-heterogeneous server is configured to determine a service resource required by the first service request, and select the target server matching the service resource from the server cluster.
9. The apparatus of claim 6, wherein the first service request is for requesting a query for target data in a database, the first determining unit comprising:
A third determining subunit configured to perform determining a target database corresponding to the first service request;
a query subunit configured to execute data to be queried, which needs to be traversed when determining to query the target data from the database;
and a fourth determining subunit configured to perform determining the amount of the data to be queried as a service resource required by the first service request.
10. The apparatus of claim 6, wherein the processing unit comprises:
a fifth determination subunit configured to perform determination of target port information of the target server;
a modification subunit configured to perform modification of the port information of the first service request to the target port information, to obtain a second service request;
the sending subunit is configured to send the second service request to the target server, wherein the second service request is used for processing the second service request by the target server to obtain the processing result;
and receiving the processing result sent by the target server.
11. A server, comprising:
a processor;
a memory for storing the processor-executable instructions;
Wherein the processor is configured to execute the instructions to implement the service request handling method of any of claims 1 to 5.
12. A computer readable storage medium, characterized in that instructions in the computer readable storage medium, when executed by a processor of a server, enable the server to perform the service request processing method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110538953.3A CN113242307B (en) | 2021-05-18 | 2021-05-18 | Service request processing method, device, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110538953.3A CN113242307B (en) | 2021-05-18 | 2021-05-18 | Service request processing method, device, server and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113242307A CN113242307A (en) | 2021-08-10 |
| CN113242307B true CN113242307B (en) | 2023-04-25 |
Family
ID=77134980
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110538953.3A Active CN113242307B (en) | 2021-05-18 | 2021-05-18 | Service request processing method, device, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113242307B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107819825A (en) * | 2017-10-11 | 2018-03-20 | 深圳市买买提乐购金融服务有限公司 | A kind of service scheduling method, device and electronic equipment |
| CN109327550A (en) * | 2018-11-30 | 2019-02-12 | 网宿科技股份有限公司 | A kind of distribution method of access request, device, storage medium and computer equipment |
| CN112153155A (en) * | 2020-09-28 | 2020-12-29 | 平安数字信息科技(深圳)有限公司 | Service request method, device, computer equipment and medium in server cluster |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7809833B2 (en) * | 2008-07-15 | 2010-10-05 | International Business Machines Corporation | Asymmetric dynamic server clustering with inter-cluster workload balancing |
| US20140149554A1 (en) * | 2012-11-29 | 2014-05-29 | Ricoh Co., Ltd. | Unified Server for Managing a Heterogeneous Mix of Devices |
| CN108173894A (en) * | 2016-12-07 | 2018-06-15 | 阿里巴巴集团控股有限公司 | The method, apparatus and server apparatus of server load balancing |
| CN109558246A (en) * | 2018-12-04 | 2019-04-02 | 北京字节跳动网络技术有限公司 | A kind of load-balancing method, device, electronic equipment and storage medium |
| CN111367654A (en) * | 2020-02-12 | 2020-07-03 | 吉利汽车研究院（宁波）有限公司 | Data processing method and device based on heterogeneous cloud platform |
-
2021
- 2021-05-18 CN CN202110538953.3A patent/CN113242307B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107819825A (en) * | 2017-10-11 | 2018-03-20 | 深圳市买买提乐购金融服务有限公司 | A kind of service scheduling method, device and electronic equipment |
| CN109327550A (en) * | 2018-11-30 | 2019-02-12 | 网宿科技股份有限公司 | A kind of distribution method of access request, device, storage medium and computer equipment |
| CN112153155A (en) * | 2020-09-28 | 2020-12-29 | 平安数字信息科技(深圳)有限公司 | Service request method, device, computer equipment and medium in server cluster |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113242307A (en) | 2021-08-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107566786B (en) | Method and device for acquiring monitoring video and terminal equipment | |
| US10601767B2 (en) | DNS query processing based on application information | |
| WO2017114205A1 (en) | Short link processing method, device and server | |
| EP2985705A2 (en) | Webpage access method and apparatus, and router | |
| CN103391312B (en) | Resource offline method for down loading and device | |
| CN110557284B (en) | Data aggregation method and device based on client gateway | |
| CN108933829A (en) | A kind of load-balancing method and device | |
| CN111327647B (en) | Method and device for providing service to outside by container and electronic equipment | |
| CN106453460B (en) | File distribution method, device and system | |
| CN110336848B (en) | Scheduling method, scheduling system and scheduling equipment for access request | |
| CN110764688B (en) | Method and device for processing data | |
| CN112788126A (en) | Resource downloading method, device, server and storage medium | |
| CN113452808A (en) | Domain name resolution method, device, equipment and storage medium | |
| CN112445700A (en) | Test method and device | |
| US9350606B2 (en) | System and method for assigning server to terminal and efficiently delivering messages to the terminal | |
| CN110943876B (en) | URL state detection method, device, equipment and system | |
| CN108401040B (en) | Content receiving method, content sending method, device and system for NDN | |
| CN111159131A (en) | Performance optimization method, device, equipment and computer readable storage medium | |
| CN109471713B (en) | Method and device for inquiring information | |
| CN114138325A (en) | Gray scale publishing method and device | |
| WO2018068655A1 (en) | License management method and system | |
| CN113242307B (en) | Service request processing method, device, server and storage medium | |
| WO2017000540A1 (en) | Data query method and device | |
| CN113596105B (en) | Content acquisition method, edge node and computer readable storage medium | |
| CN107612831B (en) | Transmission method and device for data message of access source station |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |