CN115086333A - Service request distribution method, device and storage medium - Google Patents
Service request distribution method, device and storage medium Download PDFInfo
- Publication number
- CN115086333A CN115086333A CN202210444208.7A CN202210444208A CN115086333A CN 115086333 A CN115086333 A CN 115086333A CN 202210444208 A CN202210444208 A CN 202210444208A CN 115086333 A CN115086333 A CN 115086333A
- Authority
- CN
- China
- Prior art keywords
- service
- cluster
- target
- service request
- target service
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 64
- 230000006870 function Effects 0.000 claims description 42
- 230000008569 process Effects 0.000 claims description 25
- 238000004590 computer program Methods 0.000 claims description 7
- 206010033799 Paralysis Diseases 0.000 abstract description 6
- 238000004883 computer application Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 8
- 238000013473 artificial intelligence Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
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
- H04L67/1004—Server selection for load balancing
- H04L67/1014—Server selection for load balancing based on the content of a request
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1034—Reaction to server failures by a load balancer
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The disclosure relates to a service request distribution method, a service request distribution device and a storage medium, and relates to the technical field of computer application. The method comprises the following steps: receiving a service request which is sent by a client and corresponds to a target service function, wherein the service request comprises a target service type identifier; determining a first target service cluster corresponding to the target service type identifier based on a corresponding relation between a service type and a service cluster which are configured in advance; and distributing the service request to a first target service cluster for processing. The method and the device can distribute the service request sent by the client to the corresponding first target service cluster for processing according to the service type, reasonably utilize the service clusters, and avoid the service request blockage caused by paralysis of a certain service cluster due to insufficient processing capacity.
Description
Technical Field
The present disclosure relates to the field of computer application technologies, and in particular, to a service request distribution method, apparatus, and storage medium.
Background
In a cluster system, in order to satisfy service requests of a large number of users, the related art generally distributes the service requests of the users to different clusters in a load balancing manner to process the service requests, so as to prevent a cluster from being broken down due to the concentrated impact of the service requests of the users on the cluster. However, since the operating states and performances of the clusters are different and the processing capabilities of the service requests of the users are different, the related art cannot effectively complete the allocation and scheduling of the service requests, and the problem that a cluster is still likely to be paralyzed due to insufficient processing capabilities occurs, thereby causing service request congestion.
Disclosure of Invention
The present disclosure provides a service request allocation method, device and storage medium, to at least solve the problem in the related art that a cluster is likely to be paralyzed due to insufficient processing capability. The technical scheme of the disclosure is as follows:
according to a first aspect of the embodiments of the present disclosure, there is provided a service request allocation method, including:
receiving a service request which is sent by a client and corresponds to a target service function, wherein the service request comprises a target service type identifier;
determining a first target service cluster corresponding to the target service type identifier based on a corresponding relation between a service type and a service cluster which are configured in advance;
and distributing the service request to the first target service cluster for processing.
In some embodiments, the method further comprises:
receiving a service function identifier, a service type identifier and a service cluster identifier which are input in a configuration interface by a user;
establishing a corresponding relation between the service type identifier and the service cluster identifier as a corresponding relation between the pre-configured service type and the service cluster;
and sending the corresponding relation between the service function identifier and the service type identifier to the client so that the client can determine the target service type identifier based on the service function identifier of the target service function and carry the target service type identifier in the service request when triggering the service request.
In some embodiments, said assigning the service request to the first target service cluster for processing comprises:
creating a calling object for calling the first target service cluster according to the configuration information of the first target service cluster;
and if the creation is successful, based on the calling object, calling the first target service cluster to process the service request.
In some embodiments, the method further comprises:
if the creation is failed, calling the preset service cluster to process the service request based on a pre-created calling object corresponding to the preset service cluster, wherein the preset service cluster is a pre-configured default service cluster for processing the service request.
In some embodiments, the method further comprises:
if the first target service cluster corresponding to the target service type identification does not exist, the preset service cluster is called to process the service request based on a pre-established calling object corresponding to the preset service cluster, and the preset service cluster is a pre-configured default service cluster for processing the service request.
In some embodiments, the method further comprises:
if the first target service cluster is monitored to have a fault, determining a second target service cluster which has the same service type identifier as the first target service cluster;
and switching the service request processed in the first target service cluster to be processed by the second target service cluster.
In some embodiments, the method further comprises:
and if no available second target service cluster with the same service type identifier as the first target service cluster exists, switching the service request processed in the first target service cluster to be processed by a preset service cluster, wherein the preset service cluster is a default service cluster which is configured in advance and processes the service request.
According to a second aspect of the embodiments of the present disclosure, there is provided a service request allocating apparatus, including:
the receiving unit is configured to execute receiving of a service request corresponding to a target service function sent by a client, wherein the service request comprises a target service type identifier;
the determining unit is configured to execute determining a first target service cluster corresponding to the target service type identifier based on a corresponding relation between a service type configured in advance and a service cluster;
a processing unit configured to perform assigning the service request to the first target service cluster for processing.
In some embodiments, the apparatus further comprises:
the first unit is configured to execute the steps of receiving a service function identifier, a service type identifier and a service cluster identifier which are input in a configuration interface by a user;
a second unit, configured to perform establishing a correspondence between the service type identifier and the service cluster identifier as a correspondence between the preconfigured service type and a service cluster;
a third unit, configured to execute sending the corresponding relationship between the service function identifier and the service type identifier to the client, so that the client determines the target service type identifier based on the service function identifier of the target service function and carries the target service type identifier in the service request when triggering the service request.
In some embodiments, said assigning said service request to said first target service cluster for processing comprises:
creating a calling object for calling the first target service cluster according to the configuration information of the first target service cluster;
and if the creation is successful, based on the calling object, calling the first target service cluster to process the service request.
In some embodiments, the apparatus further comprises:
and the fourth unit is configured to execute, if the creating fails, based on a pre-created calling object corresponding to a preset service cluster, calling the preset service cluster to process the service request, where the preset service cluster is a pre-configured default service cluster for processing the service request.
In some embodiments, the apparatus further comprises:
and a fifth unit, configured to execute, if there is no first target service cluster corresponding to the target service type identifier, based on a pre-created call object corresponding to a preset service cluster, calling the preset service cluster to process the service request, where the preset service cluster is a pre-configured default service cluster for processing the service request.
In some embodiments, the apparatus further comprises:
a sixth unit, configured to determine, if it is monitored that the first target service cluster fails, a second target service cluster having a same service type identifier as the first target service cluster;
a seventh unit configured to execute switching of the service request processed in the first target service cluster to be processed by the second target service cluster.
In some embodiments, the apparatus further comprises:
an eighth unit, configured to execute, if there is no available second target service cluster having the same service type identifier as the first target service cluster, switching a service request processed in the first target service cluster to be processed by a preset service cluster, where the preset service cluster is a default service cluster configured in advance to process the service request.
According to a third aspect of the embodiments of the present disclosure, there is provided an electronic apparatus including:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the service request allocation method described above.
According to a fourth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium, in which instructions, when executed by a processor of a server, enable the server to perform the above-mentioned service request allocation method.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the service request allocation method described above.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
according to the service request distribution method provided by the embodiment of the disclosure, after receiving the service request corresponding to the target service function sent by the client, the first target service cluster corresponding to the target service type identifier can be determined based on the pre-configured corresponding relationship between the service type and the service cluster, and then the service request is distributed to the first target service cluster for processing.
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 present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.
FIG. 1 is a flow diagram illustrating a method of service request distribution in accordance with an exemplary embodiment;
FIG. 2 is an exemplary diagram illustrating a parameter configuration interface in accordance with one illustrative embodiment;
FIG. 3 is an exemplary diagram illustrating yet another parameter configuration interface in accordance with an illustrative embodiment;
FIG. 4 is an interaction diagram illustrating a service cluster configuration switch in accordance with an illustrative embodiment;
FIG. 5 is a block diagram illustrating a service request distribution apparatus in accordance with an exemplary embodiment;
fig. 6 is a schematic structural diagram of an electronic device according to an exemplary embodiment.
Detailed Description
In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in 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 above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the disclosure, as detailed in the appended claims.
In a cluster system, in order to satisfy service requests of a large number of users, the related art generally distributes the service requests of the users to different clusters in a load balancing manner to process the service requests, so as to prevent a cluster from being broken down due to the concentrated impact of the service requests of the users on the cluster. However, since the operating states and performances of the clusters are different and the processing capabilities of the service requests of the users are different, the related art cannot effectively complete the allocation and scheduling of the service requests, and the problem that a cluster is still likely to be paralyzed due to insufficient processing capabilities occurs, thereby causing service request congestion.
In view of this, an embodiment of the present disclosure provides a service request allocation method, where after receiving a service request corresponding to a target service function sent by a client, a first target service cluster corresponding to a target service type identifier is determined based on a pre-configured correspondence between a service type and a service cluster, and then the service request is allocated to the first target service cluster for processing, that is, the present disclosure may allocate the service request sent by the client to the corresponding first target service cluster for processing according to the service type, so as to reasonably utilize the service cluster, and avoid a service cluster from being paralyzed due to insufficient processing capability, thereby causing a service request to be blocked.
Fig. 1 is a flow chart illustrating a service request distribution method according to an exemplary embodiment, as shown in fig. 1, the method comprising the steps of:
in step S11, a service request corresponding to the target service function sent by the client is received, where the service request includes a target service type identifier.
In specific implementation, for example, when a merchant wants to obtain the information of the goods in the store, the reply rate of each customer service, the satisfaction degree of the customer, and the like, a corresponding service request is sent through the client. The "obtaining of the commodity information", "obtaining of the reply rate of each customer service", and "obtaining of the satisfaction of the customer" are the "target service functions" described above.
In practical application, when a certain target service function is called, a corresponding service request is triggered, and the service request automatically carries a service type identifier, that is, a client knows in advance what target service function corresponds to what service type, and the corresponding relationship between the target service function and the service type is configured in advance. Specifically, one target service function may correspond to one service type, or a plurality of target service functions may correspond to one service type, for example, "acquire goods information" or "acquire logistics information", which are two target service functions, but both may correspond to one service type, or may correspond to the same service type.
For the "target service type identifier", in practical applications, some optional service type identifiers may be provided in advance for the user to select and use based on all service functions that may be involved in the service that can be provided by the service cluster (it should be understood that the complete service is composed of several service functions). Of course, the user may also customize the service type identifier, that is, the service type identifier may be input by selecting some template identifiers provided in the interface (in the interface, some explanatory text about the template identifier may also be provided for the user to select and refer to). For ease of understanding, reference may be made to fig. 2. The "template key" in fig. 2 is the "target service type identifier" or "template identifier" in this disclosure, and the specific expression form of the "template key" is not limited herein, and may be a combination of letters in fig. 2, a combination of numbers, a combination of symbols, and the like.
Further, in order to ensure that the client carries the target service type identifier when triggering the service request, the service request allocation method further includes the following steps:
in step S21, the service function identifier, the service type identifier, and the service cluster identifier input by the user in the configuration interface are received.
For convenience of understanding, referring to fig. 2, in the parameter configuration interface shown in fig. 2, the "user" is a "service function identifier", the "template key" is a "service type identifier", and the "cluster" is a "service cluster identifier".
In step S22, a correspondence between the service type identifier and the service cluster identifier is established as a correspondence between a service type and a service cluster configured in advance.
In step S23, the correspondence between the service function identifier and the service type identifier is sent to the client, so that the client determines the target service type identifier and carries the service type identifier based on the service function identifier of the target service function when triggering the service request.
In practical applications, the parameter in the parameter configuration interface of fig. 2 is modified to establish the corresponding relationship between the service type identifier and the first service cluster identifier (specifically, the corresponding relationship between the service type identifier and the service cluster identifier may be established by inputting or selecting the service function identifier, the service type identifier, and the service cluster identifier), and then the corresponding relationship between the service function identifier and the service type identifier is sent to the client, so that the client can carry the service type identifier when triggering the service request.
In step S12, a first target service cluster corresponding to the target service type identifier is determined based on the pre-configured correspondence between the service type and the service cluster.
It should be understood that after the corresponding relationship between the service type and the service cluster is configured, the service cluster corresponding to the service type can be determined according to the service type identifier. The number of the service clusters may be multiple, and the services that can be provided by the multiple service clusters are the same, but the corresponding relationship between the service types and the service clusters is set according to the service types that may be involved. Different service clusters can provide services for different services and perform service isolation, and in addition, disaster recovery backup can be performed on the different service clusters.
In step S13, the service request is assigned to the first target service cluster for processing.
In the embodiment of the present disclosure, after determining the first target service cluster, in order to smoothly allocate the service request to the first target service cluster for processing, the following steps may be adopted.
In step S1301, a call object that calls the first target service cluster is created according to the configuration information of the first target service cluster.
In step S1302, if the creation is successful, the first target service cluster is invoked to process the service request based on the invocation object.
In step S1303, if the creation fails, a preset service cluster is called to process the service request based on a pre-created calling object corresponding to the preset service cluster, where the preset service cluster is a pre-configured default service cluster for processing the service request.
It should be understood that before the first target service cluster is called to process the service request, a call object needs to be created, and if the creation is successful, the first target service cluster is called to process the service request based on the call object. If the creation is failed, alarm processing can be carried out, and the preset service cluster is called to process the service request based on a pre-created calling object corresponding to the preset service cluster. The preset service cluster is a default service cluster which is configured in advance and used for processing the service request.
Considering that there may not be a first target service cluster corresponding to the target service type identifier, when there is no first target service cluster corresponding to the target service type identifier, a preset service cluster may be called to process the service request based on a pre-created call object corresponding to the preset service cluster, where the preset service cluster is a pre-configured default service cluster for processing the service request.
In addition, in practical applications, the first target service cluster may have a fault due to a network fault, extreme weather, or the like, and if the first target service cluster has a fault, the first target service cluster may be processed by a method of switching service clusters, specifically as follows:
if the first target service cluster is monitored to have a fault, determining a second target service cluster which has the same service type identifier as the first target service cluster;
and switching the service request processed in the first target service cluster to be processed by the second target service cluster.
Considering that there may not be an available second target service cluster having the same service type identifier as the first target service cluster, when there is no available second target service cluster having the same service type identifier as the first target service cluster, the service request processed in the first target service cluster may be switched to be processed by a preset service cluster, where the preset service cluster is a default service cluster configured in advance to process the service request.
For the multiple service clusters, operations such as adding, updating, deleting, etc. may be performed on the multiple service clusters in another parameter configuration interface, and an exemplary diagram of the parameter configuration interface may refer to fig. 3. Fig. 3 includes configuration information related to a plurality of service clusters and corresponding operation options.
In practical applications, if an addition, update, or deletion operation is performed on a certain service cluster, a service cluster list (used for recording configuration information of each service cluster) after the addition, update, or deletion operation may be updated and stored in the first database. And when the service cluster needs to be switched, directly reading the updated service cluster list. Moreover, after the service cluster switching operation is performed, the switching condition of the service cluster also needs to be updated and recorded in the second database, and a specific process can be seen in fig. 4.
To sum up, after receiving a service request corresponding to a target service function sent by a client, the embodiment of the present disclosure may determine, based on a pre-configured correspondence between a service type and a service cluster, a first target service cluster corresponding to a target service type identifier, and then allocate the service request to the first target service cluster for processing, that is, the disclosure may allocate the service request sent by the client to the corresponding first target service cluster for processing according to the service type, so as to reasonably utilize the service cluster, and avoid a certain service cluster from being paralyzed due to insufficient processing capability, thereby causing a service request to be blocked. In addition, when the service request is distributed, the code does not need to be modified, the service cluster management is carried out in a configuration mode, and the whole scheme is more systematic and has quick response.
Based on the same inventive concept, the embodiment of the present disclosure further provides a service request distribution apparatus, as described in the following embodiments. Since the principle of the service request allocation apparatus for solving the problem is similar to that of the service request allocation method, the implementation of the service request allocation apparatus can refer to the implementation of the service request allocation method, and repeated details are not described herein. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Fig. 5 is a block diagram illustrating a service request distribution apparatus according to an exemplary embodiment, and referring to fig. 5, the apparatus includes a receiving unit 501, a determining unit 502, and a processing unit 503.
The receiving unit 501 is configured to perform receiving a service request corresponding to a target service function sent by a client, where the service request includes a target service type identifier;
the determining unit 502 is configured to perform determining a first target service cluster corresponding to the target service type identifier based on a pre-configured correspondence between the service type and the service cluster;
the processing unit 503 is configured to perform assigning the service request to the first target service cluster for processing.
In an exemplary embodiment of the present disclosure, the apparatus further includes:
the first unit is configured to execute the steps of receiving a service function identifier, a service type identifier and a service cluster identifier which are input in a configuration interface by a user;
a second unit, configured to perform establishing a correspondence between the service type identifier and the service cluster identifier as a correspondence between the preconfigured service type and a service cluster;
a third unit, configured to execute sending the corresponding relationship between the service function identifier and the service type identifier to the client, so that the client determines the target service type identifier based on the service function identifier of the target service function and carries the target service type identifier in the service request when triggering the service request.
In an exemplary embodiment of the present disclosure, the processing unit 503 is further configured to perform:
creating a calling object for calling the first target service cluster according to the configuration information of the first target service cluster;
and if the creation is successful, based on the calling object, calling the first target service cluster to process the service request.
In an exemplary embodiment of the present disclosure, the apparatus further includes:
and the fourth unit is configured to execute, if the creation fails, calling the preset service cluster to process the service request based on a pre-created calling object corresponding to the preset service cluster, where the preset service cluster is a pre-configured default service cluster for processing the service request.
In an exemplary embodiment of the present disclosure, the apparatus further includes:
and a fifth unit, configured to execute, if there is no first target service cluster corresponding to the target service type identifier, based on a pre-created call object corresponding to a preset service cluster, calling the preset service cluster to process the service request, where the preset service cluster is a pre-configured default service cluster for processing the service request.
In an exemplary embodiment of the present disclosure, the apparatus further includes:
a sixth unit, configured to determine, if it is monitored that the first target service cluster fails, a second target service cluster having a same service type identifier as the first target service cluster;
a seventh unit configured to execute switching of the service request processed in the first target service cluster to be processed by the second target service cluster.
In an exemplary embodiment of the present disclosure, the apparatus further includes:
an eighth unit, configured to execute, if there is no available second target service cluster having the same service type identifier as the first target service cluster, switching a service request processed in the first target service cluster to be processed by a preset service cluster, where the preset service cluster is a default service cluster configured in advance to process the service request.
In an exemplary embodiment of the present disclosure, the structure of the service request allocating apparatus shown in fig. 5 may be implemented as an electronic device, which may include: a processor 1001, a memory 1002, a display 1003; the memory 1002 stores executable code thereon, and when the executable code is executed by the processor 1001, the processor 1001 is caused to execute the service request allocation method. The processor 1001 may further perform other related steps in the service request allocation method provided in the related embodiments, which are not described herein again.
Among other things, the processor 1001 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so on. The processor 1001 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 1001 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also referred to as a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 1001 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the display screen. In some embodiments, the processor 1001 may further include an AI (Artificial Intelligence) processor for processing a computing operation related to machine learning.
The memory 1002 may include one or more storage media, which may be non-transitory. Memory 1002 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices.
In an exemplary embodiment, the present disclosure also provides a computer-readable storage medium comprising instructions, such as a memory comprising instructions, executable by the processor 1001 of the electronic device to perform the service request assignment method described above. Alternatively, the storage medium may be a non-transitory storage medium, for example, the non-transitory storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like. The present disclosure also provides a computer program product comprising a computer program which, when executed by the processor 1001, implements the service request allocation method described above.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the 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 will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. A method for service request distribution, comprising:
receiving a service request which is sent by a client and corresponds to a target service function, wherein the service request comprises a target service type identifier;
determining a first target service cluster corresponding to the target service type identifier based on a corresponding relation between a service type and a service cluster which are configured in advance;
and distributing the service request to the first target service cluster for processing.
2. The method of claim 1, further comprising:
receiving a service function identifier, a service type identifier and a service cluster identifier which are input in a configuration interface by a user;
establishing a corresponding relation between the service type identifier and the service cluster identifier as a corresponding relation between the pre-configured service type and the service cluster;
and sending the corresponding relation between the service function identifier and the service type identifier to the client so that the client can determine the target service type identifier based on the service function identifier of the target service function and carry the target service type identifier in the service request when triggering the service request.
3. The method of claim 1, wherein the allocating the service request to the first target service cluster for processing comprises:
creating a calling object for calling the first target service cluster according to the configuration information of the first target service cluster;
and if the creation is successful, based on the calling object, calling the first target service cluster to process the service request.
4. The method of claim 3, further comprising:
if the creation is failed, calling the preset service cluster to process the service request based on a pre-created calling object corresponding to the preset service cluster, wherein the preset service cluster is a pre-configured default service cluster for processing the service request.
5. The method of claim 1, further comprising:
if the first target service cluster corresponding to the target service type identification does not exist, the preset service cluster is called to process the service request based on a pre-established calling object corresponding to the preset service cluster, and the preset service cluster is a pre-configured default service cluster for processing the service request.
6. The method of claim 1, further comprising:
if the first target service cluster is monitored to have a fault, determining a second target service cluster which has the same service type identifier as the first target service cluster;
and switching the service request processed in the first target service cluster to be processed by the second target service cluster.
7. A service request distribution apparatus, comprising:
the receiving unit is configured to execute receiving of a service request corresponding to a target service function sent by a client, wherein the service request comprises a target service type identifier;
the determining unit is configured to execute determining a first target service cluster corresponding to the target service type identifier based on a corresponding relation between a service type configured in advance and a service cluster;
a processing unit configured to perform assigning the service request to the first target service cluster for processing.
8. An electronic device, 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 allocation method of any of claims 1 to 6.
9. A computer-readable storage medium, wherein instructions in the computer-readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the service request distribution method of any of claims 1 to 6.
10. A computer program product comprising a computer program, characterized in that the computer program realizes the service request distribution method of any of claims 1 to 6 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210444208.7A CN115086333B (en) | 2022-04-25 | 2022-04-25 | Service request distribution method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210444208.7A CN115086333B (en) | 2022-04-25 | 2022-04-25 | Service request distribution method, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115086333A true CN115086333A (en) | 2022-09-20 |
| CN115086333B CN115086333B (en) | 2024-08-13 |
Family
ID=83247527
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210444208.7A Active CN115086333B (en) | 2022-04-25 | 2022-04-25 | Service request distribution method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115086333B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018149221A1 (en) * | 2017-02-20 | 2018-08-23 | 京信通信系统（中国）有限公司 | Device management method and network management system |
| CN109660607A (en) * | 2018-12-05 | 2019-04-19 | 北京金山云网络技术有限公司 | A kind of service request distribution method, method of reseptance, device and server cluster |
| CN111428099A (en) * | 2020-03-23 | 2020-07-17 | 中国建设银行股份有限公司 | Financial service capability query method based on Internet of things and network management center system |
| CN111600794A (en) * | 2020-07-24 | 2020-08-28 | 腾讯科技（深圳）有限公司 | Server switching method, terminal, server and storage medium |
| CN112561264A (en) * | 2020-12-04 | 2021-03-26 | 中广核工程有限公司 | Service method, service system and storage medium for enterprise content |
| CN112953982A (en) * | 2019-11-26 | 2021-06-11 | 腾讯科技（深圳）有限公司 | Service processing method, service configuration method and related device |
| CN113645304A (en) * | 2021-08-13 | 2021-11-12 | 恒生电子股份有限公司 | Data service processing method and related equipment |
| CN114003337A (en) * | 2021-10-12 | 2022-02-01 | 深圳思为科技有限公司 | Access request distribution method and device |
-
2022
- 2022-04-25 CN CN202210444208.7A patent/CN115086333B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018149221A1 (en) * | 2017-02-20 | 2018-08-23 | 京信通信系统（中国）有限公司 | Device management method and network management system |
| CN109660607A (en) * | 2018-12-05 | 2019-04-19 | 北京金山云网络技术有限公司 | A kind of service request distribution method, method of reseptance, device and server cluster |
| CN112953982A (en) * | 2019-11-26 | 2021-06-11 | 腾讯科技（深圳）有限公司 | Service processing method, service configuration method and related device |
| CN111428099A (en) * | 2020-03-23 | 2020-07-17 | 中国建设银行股份有限公司 | Financial service capability query method based on Internet of things and network management center system |
| CN111600794A (en) * | 2020-07-24 | 2020-08-28 | 腾讯科技（深圳）有限公司 | Server switching method, terminal, server and storage medium |
| CN112561264A (en) * | 2020-12-04 | 2021-03-26 | 中广核工程有限公司 | Service method, service system and storage medium for enterprise content |
| CN113645304A (en) * | 2021-08-13 | 2021-11-12 | 恒生电子股份有限公司 | Data service processing method and related equipment |
| CN114003337A (en) * | 2021-10-12 | 2022-02-01 | 深圳思为科技有限公司 | Access request distribution method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115086333B (en) | 2024-08-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109565515B (en) | System, apparatus, and process for dynamic tenant fabric adjustment in a distributed resource management system | |
| EP3220269B1 (en) | Mobile terminal and resource management method thereof | |
| US10601680B2 (en) | Application resiliency using APIs | |
| CN104635901A (en) | Systems and methods for protecting virtualized assets | |
| US11381488B2 (en) | Centralized, scalable, resource monitoring system | |
| CN108134766A (en) | A kind of method, apparatus, system, server and client for servicing publication | |
| CN111427675A (en) | Data processing method and device and computer readable storage medium | |
| CN111274033B (en) | Resource deployment method, device, server and storage medium | |
| CN112231108A (en) | Task processing method, device, computer-readable storage medium, and server | |
| CN108268211B (en) | Data processing method and device | |
| CN111061432A (en) | Service migration method, device, equipment and readable storage medium | |
| CN107689879A (en) | The management method and device of Virtual NE | |
| CN105404547A (en) | Fusion method and device of operating system | |
| EP4006725A1 (en) | Virtual machine migration processing and strategy generation method, apparatus and device, and storage medium | |
| CN106357791A (en) | Method, device and system for processing services | |
| CN111309216A (en) | List page display method and device, computer equipment and storage medium | |
| CN112003754A (en) | Visual node registration method for OpenStack cluster | |
| CN115167992A (en) | Task processing method, system, device, server, medium, and program product | |
| CN109582439A (en) | DCN dispositions method, device, equipment and computer readable storage medium | |
| US11531674B2 (en) | System and method for supporting rollback of changes made to target systems via an integration platform | |
| CN113326052B (en) | Business component upgrade method, device, computer equipment and storage medium | |
| CN115086333B (en) | Service request distribution method, device and storage medium | |
| US12073263B1 (en) | Dynamic processing of API requests | |
| CN115756840A (en) | Hardware resource scheduling method, system, computer device and storage medium | |
| CN114629958A (en) | Resource allocation method, device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |