CN110858843B - Service request processing method and device and computer readable storage medium - Google Patents

Service request processing method and device and computer readable storage medium Download PDF

Info

Publication number
CN110858843B
CN110858843B CN201810959862.5A CN201810959862A CN110858843B CN 110858843 B CN110858843 B CN 110858843B CN 201810959862 A CN201810959862 A CN 201810959862A CN 110858843 B CN110858843 B CN 110858843B
Authority
CN
China
Prior art keywords
service request
service
target service
server
target
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
Application number
CN201810959862.5A
Other languages
Chinese (zh)
Other versions
CN110858843A (en
Inventor
陈岗
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Simplecredit Micro-Lending Co ltd
Original Assignee
Simplecredit Micro-Lending Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Simplecredit Micro-Lending Co ltd filed Critical Simplecredit Micro-Lending Co ltd
Priority to CN201810959862.5A priority Critical patent/CN110858843B/en
Publication of CN110858843A publication Critical patent/CN110858843A/en
Application granted granted Critical
Publication of CN110858843B publication Critical patent/CN110858843B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/60Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1001Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004Server selection for load balancing
    • H04L67/1008Server selection for load balancing based on parameters of servers, e.g. available memory or workload
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/60Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/62Establishing a time schedule for servicing the requests

Abstract

The embodiment of the invention provides a service request processing method, a device and a computer readable storage medium, wherein the service request processing method comprises the following steps: when a target service request sent by a target service interface is received, acquiring the number of service requests from the target service interface which are being processed by a server; then, determining a first quantity threshold corresponding to the target service interface from the corresponding relationship between at least one group of preset service interfaces and the quantity threshold; and if the judgment determines that the number of the service requests from the target service interface, which are processed by the server, is smaller than the first number threshold, sending the target service request to the server so as to instruct the server to process the target service request. By adopting the embodiment of the invention, the middleware is added between the service interface and the server and is used for managing and controlling the service request of each service interface, thereby avoiding the overload of the server, ensuring that different services are not influenced mutually and improving the service processing efficiency.

Description

Service request processing method and device and computer readable storage medium
Technical Field
The present invention relates to the field of computers, and in particular, to a method and an apparatus for processing a service request, and a computer-readable storage medium.
Background
With the development of internet technology, service providers can provide users with various services such as shopping, listening to songs, online payment, getting a car, etc. through the internet. Specifically, a service provider sets up a server for various services, and provides service interfaces through which various services are connected to the server, and a user can access the server through the service interfaces to use various services. In recent years, with the development of the information age, the types of services are increasing, so that the types of service requests to be processed by the server are increasing, and even the requests of a certain service type may increase in a certain period of time, and most of server resources are occupied. Due to the limited load capacity of the server, if a certain service request is processed too much, the server cannot process other types of service requests, so that the services are mutually influenced.
Disclosure of Invention
The embodiment of the invention provides a service request processing method, a service request processing device and a computer readable storage medium, wherein middleware is added between a service interface and a server and is used for managing and controlling service requests of all service interfaces, so that the server load is avoided from being too heavy, different services are guaranteed not to be influenced mutually, and the service processing efficiency is improved.
In a first aspect, an embodiment of the present invention provides a method for processing a service request, including:
when a target service request sent by a target service interface is received, acquiring the number of the service requests from the target service interface which are processed by a server;
determining a first quantity threshold corresponding to a target service interface from the corresponding relation between at least one group of preset service interfaces and the quantity threshold;
judging whether the number of the service requests from the target service interface, which are processed by the server, is smaller than a first number threshold corresponding to the target service interface;
and if so, sending the target service request to the server to instruct the server to process the target service request.
Optionally, determining a first quantity threshold corresponding to the target service interface from a preset correspondence between at least one group of service interfaces and the quantity threshold includes:
determining a first time period to which the time of receiving a target service request sent by a target service interface belongs;
and determining a first quantity threshold corresponding to the target service interface according to the first time period.
Optionally, before sending the target service request to the server, the method further includes:
judging whether the target service request meets a preset processing condition or not according to a service request processing result corresponding to the target service interface;
and if so, executing the step of sending the target service request to the server.
Optionally, the service request processing result corresponding to the target service interface includes a service request processing state, and determining whether the target service request meets a preset processing condition according to the service request processing result corresponding to the target service interface includes:
acquiring a service request processing state which is sent by the server in a second time period and used for processing a service request from a target service interface, wherein the service request processing state is used for indicating that the service request processing is normal or abnormal;
and if the ratio of the number of the service request processing states which represent abnormal service request processing to the total number of the service request processing states is not greater than a ratio threshold, determining that the target service request meets the preset processing condition.
Optionally, the service request processing result corresponding to the target service interface includes service request processing duration, and determining whether the target service request meets a preset processing condition according to the service request processing result corresponding to the target service interface includes:
acquiring service request processing duration for processing a service request from a target service interface, which is sent by a server in a third time period;
acquiring the number of service request processing durations exceeding a duration threshold in the service request processing durations;
and if the number of the service request processing time lengths exceeding the time length threshold in the service request processing time lengths is not larger than the second number threshold, determining that the target service request meets the preset processing condition.
Optionally, the first preset number threshold is set according to one or more of a service type corresponding to the target service interface, a time period, and a load capacity of the server.
Optionally, the service request processing method further includes:
if the number of the service requests from the target service interface which are processed by the server is not less than a first number threshold value, adding the target service requests into a service request queue to be processed;
and when detecting that the number of the service requests from the target service interface which are processed by the server is smaller than a first number threshold, taking out the target service requests from the service request queue to be processed, and sending the target service requests to the server.
In a second aspect, an embodiment of the present invention provides a service request processing apparatus, including:
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring the number of service requests from a target service interface which are processed by a server when receiving the target service requests sent by the target service interface;
the device comprises a determining unit, a judging unit and a judging unit, wherein the determining unit is used for acquiring a first quantity threshold corresponding to a target service interface from the corresponding relation between at least one group of preset service interfaces and the quantity threshold;
the judging unit is used for judging whether the number of the service requests from the target service interface processed by the server is smaller than a first number threshold corresponding to the target service interface;
and the sending unit is used for sending the target service request to the sending server to indicate the server to process the target service request if the judging unit judges that the number of the service requests from the target service interface, which are processed by the server, is smaller than the first number threshold corresponding to the target service interface.
Optionally, the determining unit is specifically configured to:
determining a first time period to which the time of receiving a target service request sent by a target service interface belongs;
and determining a first quantity threshold corresponding to the target service interface according to the first time period.
Optionally, the determining unit is further configured to determine whether the target service request meets a preset processing condition according to a service request processing result corresponding to the target service interface; and the sending unit is used for sending the target service request to the server under the condition that the judging unit judges that the target service request meets the preset processing conditions.
Optionally, the service request processing result corresponding to the target service interface includes a service request processing state, and the implementation manner that the determining unit is configured to determine whether the target service request meets the preset processing condition according to the service request processing result corresponding to the target service interface is:
acquiring a service request processing state which is sent by the server in a second time period and used for processing a service request from a target service interface, wherein the service request processing state is used for indicating that the service request processing is normal or abnormal;
and if the ratio of the number of the service request processing states representing abnormal service request processing to the total number of the service request processing states is not greater than a ratio threshold, determining that the target service request meets the preset processing condition.
Optionally, the service request processing result corresponding to the target service interface includes a service request processing duration, and the implementation manner in which the determining unit is configured to determine whether the target service request meets the preset blowing condition according to the service request processing result corresponding to the target service interface is as follows:
acquiring service request processing duration for processing a service request from a target service interface, which is sent by a server in a third time period;
acquiring the number of service request processing time lengths exceeding a time length threshold in service request processing time lengths;
and if the number of the service request processing time lengths exceeding the time length threshold in the service request processing time lengths is not larger than the second number threshold, determining that the target service request meets the preset processing condition.
Optionally, the first number threshold is set according to one or more of a traffic type, a time period and a load capacity of the server corresponding to the target traffic interface.
Optionally, the service request processing apparatus further includes an adding unit:
the adding unit is used for adding the target service request into a service request queue to be processed if the judging unit judges that the number of the service requests from the target service interface, which are processed by the server, is not less than a first number threshold;
and the sending unit is also used for taking out the target service request from the service request queue to be processed and sending the target service request to the server when detecting that the number of the service requests from the target service interface, which are processed by the server, is a first number threshold.
In a third aspect, an embodiment of the present invention provides a service management apparatus, including a processor, a receiving module, a sending module, and a memory, where the processor, the receiving module, the sending module, and the memory are connected to each other, where the memory is used to store a computer program that supports a terminal to execute the foregoing method, the computer program includes program instructions, and the processor is configured to call the program instructions to execute the foregoing method of the first aspect.
In a fourth aspect, embodiments of the present invention provide a computer-readable storage medium storing a computer program, the computer program comprising program instructions that, when executed by a processor, cause the processor to perform the first aspect and any of the alternative methods described above.
When a target service request sent by a target service interface is received, the number of the service requests from the target service interface, which are being processed by a server, is counted. If the number of the service requests from the target service interface, which are being processed by the server, is smaller than the first number threshold corresponding to the target service interface, the target service request can be sent to the server to indicate the server to process the target service request.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is an architecture diagram of a service request processing system according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a service request processing method according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating another service request processing method according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a service request processing apparatus according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a service management device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, an architecture diagram of a service request processing method according to an embodiment of the present invention, as shown in fig. 1, may include a service interface 10, a service management device 20, and a server 30. In one embodiment, the service management device may be configured on the server 30 shown in fig. 1, or may be configured on another independent server; the service interface 10 includes a plurality of service interfaces, one service interface corresponds to a service type, or one service interface corresponds to a service of a partner, and the service type of each partner may include a user loanable amount, a loan condition, a historical repayment condition, a local repayment condition, and the like; the server 30 may be a server cluster including a plurality of servers, and the same service execution program may be integrated in the plurality of servers, that is, each of the plurality of servers may execute a service request sent by any one service interface. Alternatively, as shown in fig. 1, the service management device 20 is located between the service interface 10 and the server 30, and may be understood as a kind of middleware.
In one embodiment, the traffic management device 20 may be configured to: when a target service request sent by a target service interface is received, acquiring the number of the service requests from the target service interface which are processed by a server; determining a first quantity threshold corresponding to a target service interface from the corresponding relation between at least one group of preset service interfaces and the quantity threshold; judging whether the number of the service requests from the target service interface, which are processed by the server, is smaller than a first number threshold corresponding to the target service interface; and if so, sending the target service request to the server to instruct the server to process the target service request. Optionally, the first quantity threshold refers to a quantity of service requests from the target service interface that can be processed by the server 30 at the same time within the server load capacity, for example, the first quantity threshold is 30, which indicates that the server 30 can process 30 service requests from the target service interface at the same time.
In one embodiment, the service management apparatus may set a corresponding number threshold for each service interface according to the server load capacity and the service requirements of different service interfaces, for example, if the online payment service has a larger amount than the online taxi service requirement, and assuming that the total number of service requests that can be processed at most within the server load capacity is 50, the number threshold corresponding to the service interface that can be paid online is higher than the number threshold corresponding to the service interface that can be taxi service. For another example, if the service requirement of the partner a is greater than that of the partner b, the service management apparatus may set the number threshold corresponding to the service interface associated with the partner a to be greater than the number threshold corresponding to the service interface associated with the partner b within the range of the server load capacity. In yet another embodiment, the traffic management device may set a number threshold for different traffic interfaces at different time periods according to the server load capacity, the traffic type, and the time period.
In an embodiment, the implementation manner of the service management apparatus 20 when configured to determine the first number threshold corresponding to the target service interface from the preset correspondence between at least one group of service interfaces and the number threshold may be: determining a first time period to which the time of receiving a target service request sent by a target service interface belongs; and determining a first quantity threshold corresponding to the target service interface according to the first time period. In other words, before comparing the number of service requests from the target service interface that are being processed by the server with the first number threshold, the service management device 20 first obtains the first number threshold corresponding to the target service interface. Optionally, the method for obtaining the first number threshold may be: presetting a corresponding relation among a time period, a service interface and a quantity threshold; and searching a first quantity threshold of the target service interface corresponding to the first time period according to the first time period to which the time of receiving the target service request belongs.
In one embodiment, before the service management device 20 sends the target service request to the server, it is further configured to: judging whether the target service request meets a preset processing condition or not according to a service request processing result corresponding to the target service interface; if so, the service management device 20 sends the target service request to the server. Optionally, if it is determined that the target service request does not meet the preset processing condition, the service management device may ignore the target service request, so that power consumption of the service management device may be saved, meanwhile, the server 30 may be prevented from processing an invalid service request, and the service request processing efficiency of the server 30 is improved.
In an embodiment, the service request processing result corresponding to the target service interface may include a service request processing state, and the implementation manner that the service management device 20 is configured to determine whether the target service request meets the preset processing condition according to the service request processing result corresponding to the target service interface may be: acquiring a service request processing state which is sent by the server in a second time period and used for processing a service request from a target service interface, wherein the service request processing state is used for indicating that the service request processing is normal or abnormal; and if the ratio of the number of the service request processing states representing abnormal service request processing to the total number of the service request processing states is not greater than a ratio threshold, determining that the target service request meets the preset processing condition.
In another embodiment, the service request processing result corresponding to the target service interface may include a service request processing duration, and the implementation manner of the service management device 20 for determining whether the target service request meets the preset processing condition according to the service request processing result corresponding to the target service interface may be: acquiring service request processing duration for processing a service request from a target service interface, which is sent by a server in a third time period; acquiring the number of service request processing time lengths exceeding a time length threshold in service request processing time lengths; and if the number of the service request processing time lengths exceeding the time length threshold in the service request processing time lengths is not larger than the second number threshold, determining that the target service request meets the preset processing condition.
In one embodiment, the traffic management device 20 is further configured to: if the number of the service requests from the target service interface, which are being processed by the server, is not less than a first number threshold, adding the target service requests into a to-be-processed service request queue; and when detecting that the number of the service requests from the target service interface which are processed by the server is smaller than a first number threshold, taking out the target service requests from the service request queue to be processed, and sending the target service requests to the server.
In one embodiment, the server 30 is configured to receive a target service request sent by the service management device and process the target service request. The server 30 is further configured to store a service request processing result from the target service interface, where the service request processing result includes a service request processing state and a service request processing duration. Optionally, the server 30 may send the stored processing result of the service request corresponding to the target service interface to the service management device 20 at preset intervals, so that the service management device 20 determines whether to send the received target service request to the server according to the processing result of the service request of the target service interface. Alternatively, optionally, the server 30 may further send the service request processing result of the target service interface to the service management device 20 when receiving the query request sent by the service management device 20.
To sum up, in the embodiment of the present invention, when receiving a target service request sent by a target service interface, a service management device 20 obtains the number of service requests from the target service interface currently being processed by a server 30, and further, when determining that the number of service requests from the target service interface being processed by the server 30 is smaller than a first number threshold, the service management device 20 processes the received target service request, so that a middleware is added between the service interface and the server to manage and control the service requests of each service interface, thereby avoiding overload of the server, ensuring that different services are not affected by each other, and improving service processing efficiency.
Referring to fig. 2, a schematic flow chart of a service request processing method according to an embodiment of the present invention is shown, where the service request processing method shown in fig. 2 may include the following steps:
s201, when receiving a target service request sent by a target service interface, the service management device obtains the number of the service requests from the target service interface which are being processed by the server.
Optionally, the service management device is configured with middleware, and the service management device is located between the service interface and the server. In one embodiment, the service management device may be configured at the front end of the server, or the service management device may be a separate device located between the service interface and the server.
In one embodiment, one service interface corresponds to one service type, or one service interface corresponds to a service of a partner, the service management device and the server may both have a correspondence between the service interface and the service type or the partner pre-stored therein, and when any one of the service interface and the service type is known, the server may determine the other one according to the correspondence. For example, the service type corresponding to the service interface a is a video service, and when the server detects that the service being processed is a video service, it can be determined that the video service is from the service interface a according to the correspondence. For another example, when the service interface B corresponds to the service of the partner B, and the server detects that the service being processed is the payment condition query from the partner B, the server may determine that the payment condition query service being processed by the server is from the service interface B according to the corresponding relationship. In this case, the service request sent by the service interface to the service management device may carry a service type or a partner identifier, so that the service management device determines from which service interface the service request comes according to the service type or the partner identifier in the service request and a pre-stored service type or a correspondence between a partner and the service interface. In one embodiment, when the service management device receives a target service request, the service management device determines that the target service request is from a target service interface according to a service type carried in the target service request, and further, the service management device obtains the number of service requests from the target service interface being processed by the server.
Optionally, after completing processing of each service request, the server returns a service processing condition to the service management device, where the service processing condition is used to indicate that the server is abnormal or normal in processing the service request. In one embodiment, the way for the service management device to obtain the number of service requests from the target service interface being processed by the server may be: when the service management device receives a target service request sent by a target service interface, the service management device detects the number of the service requests of the target service interface sent to the server; then obtaining the number of the service request processing states aiming at the service request sent by a server stored in the local; and determining the number of service requests from the target service interface which are processed by the server according to the service requests and the target service interface.
In a simple example, assuming that the service management device detects that 10 service requests of the target service interface have been sent to the server, and obtains that the number of service request processing states sent by the server stored locally is 5, the service management device may determine that the number of service requests from the target service interface that are being processed by the server is 5.
In another embodiment, the manner for the service management device to obtain the number of service requests from the target service interface being processed by the server may be: the service management device counts the number of service requests from the target service interface, which are processed by the server, once every preset time; and when a target service request sent by the target service interface is received, taking the latest statistical result of the service management device as the number of the service requests from the target service interface which are processed by the server. Optionally, the manner of counting, by the service management device, the number of service requests from the target service interface, which are being processed by the server, every preset time may be as follows: the method comprises the steps of detecting the number of service requests of a target service interface sent to a server within preset time, detecting the number of service request processing states of the service requests of the target service interface sent by the server within the preset time, and obtaining the number of the service requests from the target service interface which are processed by the server according to the difference of the two numbers.
For example, assuming that the service management device counts the number of service requests from the target service interface being processed by the server every 10 minutes, when receiving the target service request sent by the target service interface, and the service management device differs from the last counting time by 5 minutes, the service management device takes the result of the last 10-minute counting as the number of service requests from the target service interface being processed by the server.
S202, the service management device determines a first quantity threshold corresponding to the target service interface from the corresponding relationship between at least one group of preset service interfaces and the quantity threshold.
In one embodiment, the first number threshold is used to define a maximum number of service requests of the target service interface that the server can simultaneously process. It can be understood that, because the load capacity of the server is limited, in order to prevent the system from being broken down due to the excessive load of the server and simultaneously avoid the situation that the server cannot process other service requests due to the excessive processing of a certain service request in a certain time period, the service management device may set a number threshold for different service interfaces in advance according to the load capacity of the server and different requirements of each service type, and the number threshold corresponding to each service interface may be embodied in the form of a hash table. For example, the service management device setup server may simultaneously process 50 maximum service requests of the a interface, 30 maximum service requests of the B interface, and 40 maximum service requests of the C interface.
In an embodiment, when the service management device receives a target service request, the service management device may determine, according to a service type carried in the target service request or other identifiers capable of indicating service interfaces, which target service interface the target service request comes from; and searching a first quantity threshold corresponding to the target service interface according to the preset corresponding relation between each service interface and the quantity threshold.
S203, the service management apparatus determines whether the number of service requests from the target service interface being processed by the server is smaller than a first number threshold corresponding to the target service interface.
In one embodiment, the way for the service management device to determine whether the number of service requests from the target service interface being processed by the server is smaller than the first number threshold corresponding to the target service interface may be: the service management device searches a first quantity threshold corresponding to a target service interface from a pre-stored hash table (namely, the corresponding relation between the service interface and the quantity threshold is stored in the service management device in the form of the hash table); and comparing the first quantity threshold corresponding to the target interface with the quantity of the service requests from the target service interface, which are processed by the server.
In one embodiment, if the service management device determines that the number of service requests from the target service interface being processed by the server is smaller than the first number threshold, it indicates that the server can also receive and process the service requests from the target service interface, and therefore, the service management device sends the target service request to the server, that is, step S204; if the service management device judges that the number of the service requests from the target service interface, which are being processed by the server, is not less than the first number threshold, the service management device indicates that the service requests from the target service interface, which are being processed by the server, have reached the maximum value.
And S204, if the number of the service requests from the target service interface, which are processed by the server, is smaller than a first number threshold, the service management device sends the target service requests to the server.
In an embodiment, if the number of the service requests from the target service interface being processed by the server is not less than the first number threshold, the service management device may also reject the target service request from the target service interface, or the service management device may also add the target service request to the to-be-processed service request queue, then detect the number of the service requests from the target service interface being processed by the server at preset time intervals, and when detecting that the number is less than the first number threshold, the service management device takes out the target service request from the to-be-processed service request queue and sends the target service request to the server, so as to facilitate processing by the server.
In an embodiment, when the service management device determines that the number of service requests from the target service interface being processed by the server is smaller than the first number threshold, the service management device may further determine whether the target service request meets a preset processing condition, if yes, the service management device sends the target service request to the server for processing, and if not, the service management device may not send the target service request to the server, so that power consumption overhead of the service management device may be saved, and the working efficiency of the server may be improved.
Or, the service management device may also determine whether the target service request meets the preset processing condition, and then determine whether the number of the service requests from the target service interface being processed by the server is smaller than the first number threshold.
In this embodiment, when a target service request sent by a target service interface is received, the number of service requests from the target service interface that are being processed by a server is counted. If the number of the service requests from the target service interface, which are being processed by the server, is smaller than the first number threshold, the target service request can be sent to the server to indicate the server to process the target service request.
Referring to fig. 3, a schematic flow chart of another service request processing method provided in the embodiment of the present invention is shown, where the service request processing method shown in fig. 3 may include:
s301, when receiving the target service request sent by the target service interface, the service management device obtains the number of the service requests from the target service interface which are being processed by the server.
Optionally, it is described in S201 shown in fig. 2 that one service interface corresponds to one service type, and a service request sent by each service interface to the service management device may carry the service type. In one embodiment, the way for the service management device to obtain the number of service requests from the target service interface being processed by the server may be: the service management device sends a query request to the server, wherein the query request carries an interface identifier of a target service interface; the server searches a service type corresponding to the target service interface from a preset corresponding relation between the service interface and the service type according to the interface identifier carried in the query request; after the server finds the service type, detecting the number of the service requests related to the service type; the number of service requests relating to the service type being processed is sent to the service management device.
In another embodiment, the manner for the service management device to obtain the number of service requests from the target service interface being processed by the server may further be: the service management device determines the service type according to the received target service request, generates a query request carrying the service type and sends the query request to the server; after receiving the query request, the server detects the number of the service requests related to the service type carried in the query request in the service requests being processed, and returns the number to the service management device, so that the service management device can obtain the number of the service requests from the target service interface being processed by the server.
S302, the service management device determines a first time period to which the time of receiving the target service request sent by the target service interface belongs.
S303, the service management device determines a first quantity threshold corresponding to the target service interface according to the first time period.
Optionally, the first number threshold is set according to one or more of a traffic type, a time period and a server load capacity corresponding to the target traffic interface. In one embodiment, the first quantity threshold may be set by the service management device according to a service type corresponding to the target service interface and a load capability of the server. For example, the service type corresponding to the target service interface is a chat service, the service type corresponding to the a service interface is a taxi-taking service, the service type corresponding to the B interface is an online shopping service, and the number of the servers capable of processing service requests within the load capacity of the server is 60 at most. Since the chat service is more demanded than the other two services, and the online shopping service is more demanded than the taxi-calling service, the service management apparatus may set the first number threshold of the target service interface to be 30, the number threshold of the a interface to be 20, and the number threshold of the B interface to be 10, respectively, within the server load capacity.
For another example, the service type corresponding to the target service interface is a loan amount query service of the user of the party a, the service type corresponding to the service interface B is a local repayment condition query of the party B, assuming that the number of the servers capable of simultaneously processing service requests within the range of the load capacity of the server is 50 at most, if the loan amount query service demand of the user of the party a is greater than the local repayment condition query service of the party B, the service management device may set the first number threshold corresponding to the target service interface to be 30, and the number threshold corresponding to the service interface B may be 20.
In another embodiment, the first number threshold may be set by the service management device according to the service type, the time period and the load capacity of the server corresponding to the target service interface. For example, assume that the service type corresponding to the target service interface is video service, and assume that the threshold of the number of video services that can be processed by the server is 80. Because most users in the daytime are inconvenient to watch videos in the working hours, and the peak time period for watching the videos is night, the service management device can set the first quantity threshold value corresponding to the target service interface to be 30 or less in the daytime, and set the time period to be 50 or more in the night, so that resources can be saved by the server in the daytime to process other service requests with more demands, resources for processing other service requests can be saved in the night to process the service videos, and thus, the resources are reasonably distributed by the server, and the working efficiency is improved.
S304, if the number of the service requests from the target service interface processed by the server is smaller than the first number threshold, the service management device judges whether the target service request meets the preset processing condition according to the service request processing result corresponding to the target service interface.
S305, if the target service request meets the preset processing condition, the service management device sends the target service request to the server.
Optionally, before sending the target service request to the server, the service management apparatus may first execute S304 to determine whether the target service request meets a preset processing condition: if yes, executing S305 to send the target service request to the server; if not, the service management device may not perform S305.
In an embodiment, the service management device may determine whether the target service request meets a preset processing condition according to a service request processing result corresponding to the target service interface, where the service request processing result corresponding to the target service interface includes a service request processing state. In an embodiment, the manner for the service management device to determine whether the target service request meets the preset processing condition according to the service request processing result corresponding to the target service interface may be: acquiring a service request processing state which is sent by the server in a second time period and used for processing a service request from a target service interface, wherein the service request processing state is used for indicating that the service request processing is normal or abnormal; and if the ratio of the number of the service request processing states which represent abnormal service request processing to the total number of the service request processing states is not greater than a ratio threshold, determining that the target service request meets the preset processing condition.
It can be understood that, if the ratio between the number of the service request processing states indicating that the service request processing is abnormal and the total number of the service request processing states, which is obtained in the second time period, is not greater than the ratio threshold, it indicates that the processing status of the service request of the target service interface by the server is good in the second preset time period, and the server can continue to receive and process the target service request sent by the target service interface. If the ratio between the number of the service request processing states for identifying the abnormal service request processing and the total number of the service request processing states acquired in the second time period is greater than the ratio threshold, it indicates that the service request processing condition of the server to the target service interface is poor, and in order to save server resource consumption, the service request from the target service interface can no longer be received.
For a simple example, assuming that the second time period is one week, the ratio threshold is 50%, and the service management apparatus counts that 200 service requests from the target service interface are processed by the server within one week, that is, the service management apparatus receives service request processing statuses of the service requests sent by 200 servers and directed to the target service interface. If more than 100 service request processing states among the 200 service request processing states represent processing abnormality, the service management device may not transmit the target service request to the server.
In another embodiment, the service request processing result corresponding to the target service interface includes a service request processing duration, and the manner for the service management device to determine whether the target service request meets the preset processing condition according to the service request processing result corresponding to the target service interface may be: acquiring service request processing duration for processing a service request from a target service interface, which is sent by a server in a third time period; acquiring the number of service request processing time lengths exceeding a time length threshold in service request processing time lengths; and if the number of the service request processing time lengths exceeding the time length threshold in the service request processing time lengths is not larger than the second number threshold, determining that the target service request meets the preset processing condition.
It can be understood that, if the server has a long processing time for a certain service request, which may be due to the fact that the service corresponding to the service request is relatively complex, but if most of the service requests sent by the server to a certain service interface have a long processing time, it indicates that the service request sent by the service interface may have a problem. For example, the third preset time may be 1 hour, the time threshold may be 20 seconds, and the second number threshold is 18, assuming that the server processes 30 service requests from the target service interface within the third preset time, that is, the service management device receives 30 processing time durations. And if the number of the processing time length of 30 exceeds 20 seconds exceeds 18, the service management device determines that the target service request does not meet the preset processing condition.
When receiving a target service request sent by a target service interface, the embodiment of the invention counts the number of the service requests from the target service interface which are being processed by a server. If the number of the service requests from the target service interface, which are being processed by the server, is smaller than the first number threshold, the service management device can further judge whether the target service requests meet preset processing conditions, and if the target service requests meet the preset processing conditions, the service management device can send the target service requests to the server to indicate the server to process the target service requests.
Referring to fig. 4, a schematic structural diagram of a service request processing apparatus according to an embodiment of the present invention is shown, where the service request processing apparatus shown in fig. 4 may include: acquisition unit 401, determination unit 402, and transmission unit 403:
an obtaining unit 401, configured to obtain, when receiving a target service request sent by a target service interface, the number of service requests from the target service interface that are being processed by a server;
a determining unit 402, configured to determine a first quantity threshold corresponding to a target service interface from a correspondence between at least one preset group of service interfaces and the quantity threshold;
a determining unit 403, configured to determine whether the number of service requests from the target service interface that are being processed by the server is smaller than a first number threshold corresponding to the target service interface;
a sending unit 404, configured to send the target service request to the sending server to instruct the server to process the target service request if the determining unit determines that the number of the service requests from the target service interface that are being processed by the server is smaller than the first number threshold corresponding to the target service interface.
Optionally, the determining unit 402 is specifically configured to:
determining a first time period to which the time of receiving a target service request sent by a target service interface belongs;
and determining a first quantity threshold corresponding to the target service interface according to the first time period.
Optionally, the determining unit 403 is further configured to determine whether the target service request meets a preset processing condition according to a service request processing result corresponding to the target service interface; and a sending unit 404, configured to send the target service request to the server when the determining unit determines that the target service request meets the preset processing condition.
Optionally, the service request processing result corresponding to the target service interface includes a service request processing state, and the implementation manner that the determining unit 403 is configured to determine whether the target service request meets the preset processing condition according to the service request processing result corresponding to the target service interface is:
acquiring a service request processing state which is sent by the server in a second time period and used for processing a service request from a target service interface, wherein the service request processing state is used for indicating that the service request processing is normal or abnormal;
and if the ratio of the number of the service request processing states which represent abnormal service request processing to the total number of the service request processing states is not greater than a ratio threshold, determining that the target service request meets the preset processing condition.
Optionally, the service request processing result corresponding to the target service interface includes a service request processing duration, and the implementation manner that the determining unit 403 is configured to determine whether the target service request meets the preset processing condition according to the service request processing result corresponding to the target service interface is as follows:
acquiring service request processing duration for processing a service request from a target service interface, which is sent by a server in a third time period;
acquiring the number of service request processing time lengths exceeding a time length threshold in service request processing time lengths;
and if the number of the service request processing durations exceeding the duration threshold in the service request processing durations is not greater than a second number threshold, determining that the target service request meets the preset processing condition.
Optionally, the first number threshold is set according to one or more of a traffic type corresponding to the target traffic interface, a time period, and a load capacity of the server.
Optionally, the service request processing apparatus further includes an adding unit 405:
an adding unit 405, configured to add the target service request to a to-be-processed service request queue if the determining unit determines that the number of service requests from the target service interface, which are being processed by the server, is not less than a first number threshold;
the sending unit 404 is further configured to, when it is detected that the number of the service requests from the target service interface that the server is processing is a first number threshold, take out the target service request from the queue of the service requests to be processed, and send the target service request to the server.
In this embodiment, when receiving a target service request sent by a target service interface, the obtaining unit 401 obtains the number of service requests from the target service interface that are being processed by a server. Furthermore, the determining unit 402 determines a first quantity threshold corresponding to the target service interface from a preset corresponding relationship between at least one group of service interfaces and the quantity threshold, and then the determining unit 403 determines whether the quantity is smaller than the first quantity threshold, and if so, the sending unit 404 sends the target service request to the server to instruct the server to process the target service request.
It can be understood that the functions of each functional unit and unit of the service request processing apparatus in this embodiment may be specifically implemented according to the method in the method embodiment shown in fig. 2, and the specific implementation process may refer to the description related to the method embodiment shown in fig. 3, which is not described herein again.
Fig. 5 is a schematic block diagram of a service management apparatus according to an embodiment of the present invention. The load balancing server in the embodiment shown in fig. 5 may include: one or more processors 501; one or more receiving modules 502, one or more transmitting modules 503, and a memory 504. The processor 501, the receiving module 502, the sending module 503 and the memory 504 are connected by a bus 505. The memory 504 is used for storing a computer program comprising program instructions, and the processor 501 is used for executing the program instructions stored by the memory 504. Wherein the processor 501 is configured to invoke program instructions to perform:
when a target service request sent by a target service interface is received, acquiring the number of the service requests from the target service interface which are processed by a server;
determining a first quantity threshold corresponding to a target service interface from the corresponding relation between at least one group of preset service interfaces and the quantity threshold;
judging whether the number of the service requests from the target service interface, which are processed by the server, is smaller than a first number threshold corresponding to the target service interface;
and if so, sending the target service request to the server to instruct the server to process the target service request.
Optionally, the first quantity threshold corresponding to the target service interface is determined from a preset corresponding relationship between at least one group of service interfaces and the quantity threshold, and the processor 501 is configured to invoke a program instruction to specifically execute:
determining a first time period to which time of receiving a target service request sent by a target service interface belongs;
and determining a first quantity threshold corresponding to the target service interface according to the first time period.
Optionally, before sending the target service request to the server, the processor 501 is configured to further perform:
judging whether the target service request meets a preset processing condition or not according to a service request processing result corresponding to the target service interface;
and if so, executing the step of sending the target service request to the server.
Optionally, the service request processing result corresponding to the target service interface includes a service request processing state, and whether the target service request meets a preset processing condition is determined according to the service request processing result corresponding to the target service interface, and the processor 501 is configured to specifically execute a call program instruction:
acquiring a service request processing state which is sent by the server in a second time period and used for processing a service request from a target service interface, wherein the service request processing state is used for indicating that the service request processing is normal or abnormal;
and if the ratio of the number of the service request processing states representing abnormal service request processing to the total number of the service request processing states is not greater than a ratio threshold, determining that the target service request meets the preset processing condition.
Optionally, the service request processing result corresponding to the target service interface includes a service request processing duration, and whether the target service request meets a preset processing condition is determined according to the service request processing result corresponding to the target service interface, where the processor 501 is configured to specifically execute a call program instruction:
acquiring service request processing duration for processing a service request from a target service interface, which is sent by a server in a third time period;
acquiring the number of service request processing time lengths exceeding a time length threshold in service request processing time lengths;
and if the number of the service request processing time lengths exceeding the time length threshold in the service request processing time lengths is not larger than the second number threshold, determining that the target service request meets the preset processing condition.
Optionally, the first preset number threshold is set according to one or more of a service type corresponding to the target service interface, a time period, and a load capacity of the server.
Optionally, the processor 501 is configured to invoke the program instructions to further perform:
if the number of the service requests from the target service interface, which are being processed by the server, is not less than a first number threshold, adding the target service requests into a to-be-processed service request queue;
and when detecting that the number of the service requests from the target service interface which are processed by the server is smaller than a first number threshold, taking out the target service requests from the service request queue to be processed, and sending the target service requests to the server.
It should be understood that, in the embodiment of the present invention, the Processor 501 may be a Central Processing Unit (CPU), and the Processor may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The receiving module 502 may be configured to receive a target service request sent by a target service interface, and the sending module 503 may be configured to send the target service request to a server.
The memory 504 may include a read-only memory and a random access memory, and provides instructions and data to the processor 501. A portion of the memory 504 may also include non-volatile random access memory. For example, the memory 504 may also store device type information.
In specific implementation, the processor 501 described in the embodiment of the present invention may execute the implementation described in the embodiment of the service request processing method provided in fig. 2, and may also execute the implementation of the service request processing apparatus described in fig. 4, which is not described herein again.
In an embodiment of the present invention, there is provided a computer-readable storage medium storing a computer program, the computer program comprising program instructions that when executed by a processor implement:
when a target service request sent by a target service interface is received, acquiring the number of the service requests from the target service interface which are processed by a server;
determining a first quantity threshold corresponding to a target service interface from the corresponding relation between at least one group of preset service interfaces and the quantity threshold;
judging whether the number of the service requests from the target service interface, which are processed by the server, is smaller than a first number threshold corresponding to the target service interface;
and if so, sending the target service request to the server to instruct the server to process the target service request.
Optionally, the first quantity threshold corresponding to the target service interface is determined from a preset corresponding relationship between at least one group of service interfaces and the quantity threshold, and when executed by the processor, the program instruction implements:
determining a first time period to which the time of receiving a target service request sent by a target service interface belongs;
and determining a first quantity threshold corresponding to the target service interface according to the first time period.
Optionally, before sending the target service request to the server, the program instructions, when executed by the processor, further implement:
judging whether the target service request meets a preset processing condition or not according to a service request processing result corresponding to the target service interface;
and if so, executing the step of sending the target service request to the server.
Optionally, the service request processing result corresponding to the target service interface includes a service request processing state, and whether the target service request meets a preset processing condition is determined according to the service request processing result corresponding to the target service interface, and when executed by the processor, the program instruction is specifically implemented as:
acquiring a service request processing state which is sent by the server in a second time period and used for processing a service request from a target service interface, wherein the service request processing state is used for indicating that the service request processing is normal or abnormal;
and if the ratio of the number of the service request processing states representing abnormal service request processing to the total number of the service request processing states is not greater than a ratio threshold, determining that the target service request meets the preset processing condition.
Optionally, the service request processing result corresponding to the target service interface includes a service request processing duration, and whether the target service request meets a preset processing condition is determined according to the service request processing result corresponding to the target service interface, where the program instruction is specifically implemented when executed by the processor:
acquiring service request processing duration for processing a service request from a target service interface, which is sent by a server in a third time period;
acquiring the number of service request processing time lengths exceeding a time length threshold in service request processing time lengths;
and if the number of the service request processing time lengths exceeding the time length threshold in the service request processing time lengths is not larger than the second number threshold, determining that the target service request meets the preset processing condition.
Optionally, the first preset number threshold is set according to one or more of a service type corresponding to the target service interface, a time period, and a load capacity of the server.
Optionally, the program instructions when executed by the processor further implement:
if the number of the service requests from the target service interface which are processed by the server is not less than a first number threshold value, adding the target service requests into a service request queue to be processed;
and when detecting that the number of the service requests from the target service interface which are processed by the server is smaller than a first number threshold, taking out the target service requests from the service request queue to be processed, and sending the target service requests to the server.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware related to instructions of a computer program, and the program can be stored in a computer readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
While the invention has been described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

Claims (6)

1. A service request processing method is applied to a service management device, wherein the service management device is located between a service interface and a server, and is a middleware, comprising:
when a target service request sent by a target service interface is received, acquiring the number of service requests from the target service interface which are being processed by a server;
determining a first quantity threshold corresponding to the target service interface from the corresponding relation between at least one group of preset service interfaces and the quantity threshold;
judging whether the number of the service requests from the target service interface, which are processed by the server, is smaller than the first number threshold corresponding to the target service interface;
if so, sending the target service request to the server to instruct the server to process the target service request;
if not, adding the target service request into a service request queue to be processed;
when detecting that the number of the service requests from the target service interface, which are processed by the server, is smaller than the first number threshold, taking out the target service request from the to-be-processed service request queue, and sending the target service request to the server;
before sending the target service request to the server, the method further includes:
judging whether the target service request meets a preset processing condition according to a service request processing result corresponding to the target service interface, including: acquiring a service request processing state which is sent by the server in a second time period and used for processing a service request from the target service interface, wherein the service request processing state is used for indicating that service request processing is normal or abnormal; if the ratio of the number of the service request processing states representing abnormal service request processing to the total number of the service request processing states is not greater than a ratio threshold, determining that the target service request meets a preset processing condition; or, acquiring a service request processing duration for processing the service request from the target service interface, which is sent by the server in a third time period; acquiring the number of the service request processing time lengths exceeding a time length threshold value in the service request processing time lengths; if the number of the service request processing durations exceeding the duration threshold in the service request processing durations is not greater than a second number threshold, determining that the target service request meets a preset processing condition;
and if the target service request meets the preset processing condition, executing the step of sending the target service request to the server.
2. The method according to claim 1, wherein the determining a first quantity threshold corresponding to the target service interface from a preset correspondence relationship between at least one group of service interfaces and a quantity threshold comprises:
determining a first time period to which the time of receiving the target service request sent by the target service interface belongs;
and determining a first quantity threshold corresponding to the target service interface according to the first time period.
3. The method of claim 1, wherein the first quantity threshold is set according to one or more of a traffic type, a time period and a load capacity of the server corresponding to the target traffic interface.
4. A service request processing apparatus, which is located between a service interface and a server and is middleware, comprising:
the system comprises an acquisition unit, a service processing unit and a service processing unit, wherein the acquisition unit is used for acquiring the number of service requests from a target service interface which are processed by a server when receiving the target service requests sent by the target service interface;
the determining unit is used for determining a first quantity threshold corresponding to the target service interface from the corresponding relationship between at least one group of preset service interfaces and the quantity threshold;
a determining unit, configured to determine whether a number of service requests from the target service interface that are being processed by the server is smaller than the first number threshold corresponding to the target service interface;
a sending unit, configured to send the target service request to the server to instruct the server to process the target service request if the determining unit determines that the number of service requests from the target service interface being processed by the server is smaller than a first number threshold corresponding to the target service interface;
an adding unit, configured to add the target service request to a to-be-processed service request queue if the determining unit determines that the number of service requests from the target service interface, which are being processed by the server, is not less than the first number threshold;
the sending unit is further configured to, when it is detected that the number of the service requests from the target service interface being processed by the server is smaller than the first number threshold, take out the target service request from the to-be-processed service request queue, and send the target service request to the server;
the judging unit is further configured to judge whether the target service request meets a preset processing condition according to a service request processing result corresponding to the target service interface, and includes: acquiring a service request processing state which is sent by the server in a second time period and is used for processing the service request from the target service interface, wherein the service request processing state is used for indicating that the service request processing is normal or abnormal; if the ratio of the number of the service request processing states representing abnormal service request processing to the total number of the service request processing states is not greater than a ratio threshold, determining that the target service request meets a preset processing condition; or, acquiring a service request processing duration for processing the service request from the target service interface, which is sent by the server in a third time period; acquiring the number of the service request processing time lengths exceeding a time length threshold in the service request processing time lengths; if the number of the service request processing durations exceeding the duration threshold in the service request processing durations is not greater than a second number threshold, determining that the target service request meets a preset processing condition;
the sending unit is further configured to send the target service request to a server when the determining unit determines that the target service request meets the preset processing condition.
5. A service management device, comprising a processor, a receiving module, a sending module and a memory, wherein the processor, the receiving module, the sending module and the memory are connected to each other, the memory is used for storing a computer program supporting the service management device to execute the method, the computer program comprises program instructions, and the processor is configured to call the program instructions to execute the service request processing method according to any one of the claims 1 to 3.
6. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions that, when executed by a processor, cause the processor to carry out the service request processing method according to any one of claims 1-3.
CN201810959862.5A 2018-08-22 2018-08-22 Service request processing method and device and computer readable storage medium Active CN110858843B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810959862.5A CN110858843B (en) 2018-08-22 2018-08-22 Service request processing method and device and computer readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810959862.5A CN110858843B (en) 2018-08-22 2018-08-22 Service request processing method and device and computer readable storage medium

Publications (2)

Publication Number Publication Date
CN110858843A CN110858843A (en) 2020-03-03
CN110858843B true CN110858843B (en) 2022-09-20

Family

ID=69635926

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810959862.5A Active CN110858843B (en) 2018-08-22 2018-08-22 Service request processing method and device and computer readable storage medium

Country Status (1)

Country Link
CN (1) CN110858843B (en)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113765864B (en) * 2020-06-11 2023-06-23 北京京东振世信息技术有限公司 Service request processing method and device
CN112036852A (en) * 2020-08-25 2020-12-04 北京达佳互联信息技术有限公司 Payment processing method and device, server and electronic equipment
CN113760398A (en) * 2020-09-29 2021-12-07 北京沃东天骏信息技术有限公司 Interface calling method, server, system and storage medium
CN114125066A (en) * 2021-01-15 2022-03-01 北京京东乾石科技有限公司 Method and device for processing service request
CN113285883A (en) * 2021-05-25 2021-08-20 挂号网(杭州)科技有限公司 Access request current limiting method and device, electronic equipment and storage medium
CN113434228A (en) * 2021-06-21 2021-09-24 青岛海尔科技有限公司 Page request method and device, storage medium and electronic device
CN113836405B (en) * 2021-09-09 2024-03-12 深圳Tcl新技术有限公司 Information query method, device and computer readable storage medium
CN114417081A (en) * 2021-12-27 2022-04-29 深圳萨摩耶数字科技有限公司 Processing method, device, system and storage medium
CN114745329B (en) * 2022-03-30 2024-03-22 青岛海尔科技有限公司 Flow control method and device, storage medium and electronic device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006129213A (en) * 2004-10-29 2006-05-18 Hitachi Ltd Packet communication equipment
CN105872007A (en) * 2015-12-31 2016-08-17 乐视网信息技术(北京)股份有限公司 Access request processing method, device and system
CN107508860A (en) * 2017-07-21 2017-12-22 深圳市金立通信设备有限公司 One kind service current-limiting method, server and terminal
CN107688899A (en) * 2017-08-22 2018-02-13 北京潘达互娱科技有限公司 Business process monitoring method and device

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006129213A (en) * 2004-10-29 2006-05-18 Hitachi Ltd Packet communication equipment
CN105872007A (en) * 2015-12-31 2016-08-17 乐视网信息技术(北京)股份有限公司 Access request processing method, device and system
CN107508860A (en) * 2017-07-21 2017-12-22 深圳市金立通信设备有限公司 One kind service current-limiting method, server and terminal
CN107688899A (en) * 2017-08-22 2018-02-13 北京潘达互娱科技有限公司 Business process monitoring method and device

Also Published As

Publication number Publication date
CN110858843A (en) 2020-03-03

Similar Documents

Publication Publication Date Title
CN110858843B (en) Service request processing method and device and computer readable storage medium
CN110049130B (en) Service deployment and task scheduling method and device based on edge computing
CN111131058B (en) Access quantity control method and device
CN108173698B (en) Network service management method, device, server and storage medium
CN110633442A (en) Pushing method and device and electronic equipment
US10389801B2 (en) Service request processing method, related apparatus, and system
CN110519183B (en) Node speed limiting method and device, electronic equipment and storage medium
CN107819797B (en) Access request processing method and device
CN109769029B (en) Communication connection method based on electricity consumption information acquisition system and terminal equipment
US20070265976A1 (en) License distribution in a packet data network
CN112383585A (en) Message processing system and method and electronic equipment
CN111131841A (en) Live indirect access method and device, electronic equipment and storage medium
CN111401956A (en) Advertisement service degradation method, device, server and storage medium
US7096289B2 (en) Sender to receiver request retry method and apparatus
CN111538572A (en) Task processing method, device, scheduling server and medium
CN106936926B (en) Method and system for accessing data node
CN113361913A (en) Communication service arranging method, device, computer equipment and storage medium
US10044833B2 (en) Data processing method and apparatus used for terminal application
CN111597041B (en) Calling method and device of distributed system, terminal equipment and server
CN116382892B (en) Load balancing method and device based on multi-cloud fusion and cloud service
CN113835905B (en) Message queue load balancing method and device, electronic equipment and medium
CN117032987A (en) Distributed task scheduling method, system, equipment and computer readable medium
CN116192752A (en) Service flow control method, device, electronic equipment and storage medium
CN111935782B (en) Optimization method of client retry mechanism and storage medium
CN111193760B (en) Information sending method, device 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