Method, device and system for processing service request

Abstract

The invention provides a method for processing a service request. The method comprises the steps as follows: receiving an uploaded service request; extracting a resource locator of the service request; obtaining a service identification corresponding to the resource locator, obtaining a linking number corresponding to the service identification and a linking number quota; judging whether the linking number is less than the linking number quota; transmitting the service request to a service node corresponding to the service identification if the linking number is less than the linking number quota; otherwise, performing queued processing to the service request. In addition, the invention further provides a device and a system for processing the service request. The method and the device for processing the service request could reduce the average waiting time of a user.

Description

technical field [0001] The present invention relates to the field of computer technology, in particular to a method, device and system for processing service requests. Background technique [0002] Some existing large-scale websites or Internet applications usually face a sudden increase in access traffic, such as train ticket pre-purchase websites during the Spring Festival travel season, e-commerce websites during price reduction promotions, and newly opened game business nodes. In order to cope with the sudden increase in access traffic, the business nodes of websites or Internet applications usually introduce a queuing mechanism. In the case of concurrency, only a small number of business requests are processed in batches according to the order of receipt, and the subsequent business requests received Put it in the waiting queue so that the business node will not crash due to too many concurrent requests. [0003] In traditional technology, the queuing process is usuall...

AI Technical Summary

Problems solved by technology

[0003] In traditional technology, the queuing process is usually implemented by the application server that handles the business. The application server binds many non-performance bottleneck services and performance bottleneck services together. Users can only operate after queuing into the system, and may need to complete multiple non-performance bottleneck services. The business process can only be completed after the bottleneck business and performance bottleneck business, and the users who are still in the queue need to wait for the user to complete the entire business process before entering the system, making the average waiting time of users in the queue longer

Images