Service processing method, device and electronic equipment and storage medium

Abstract

The invention discloses a service processing method, device, equipment and a medium. The method comprises the steps: receiving a web service request issued by a client; selecting a first target long connection in an idle state from a first type of connection pool for storing pre-established long connections for receiving; sending the web service request to a corresponding function module for processing by utilizing the first target long connection to obtain a processing result corresponding to the web service request; selecting a second target long connection in an idle state from a second type of connection pool for storing a pre-established long connection for sending, and returning the processing result to the client through the second target long connection. According to the method disclosed in the invention, each module does not need to keep long connection with nodes, and the number of long connections of the nodes is reduced. After each module processes the result, the result can be sent through the long connection pre-established in the second type connection pool, resource overhead of continuously establishing and destroying the temporary connection is prevented, and establishment time of the connections is reduced.

Description

technical field [0001] The present application relates to the field of computer technology, and more specifically, to a business processing method and device, an electronic device, and a computer-readable storage medium. Background technique [0002] In the architecture of traditional storage management software, different functional modules are split according to different functions of the backend, such as figure 1 , figure 2 As shown, each module of all nodes in the cluster maintains a persistent connection with a message service of a single rabbitmq service node. However, except for modules such as performance and cache that need to be regularly executed to collect information, other business modules are basically inactive. When no command is requested, the module connection is in an idle state, wasting connection resources. At the same time, after processing the request, each module temporarily applies for creating a new connection to send the processing result. Each...

AI Technical Summary

Problems solved by technology

However, except for modules such as performance and cache that need to collect information regularly, other business modules are basically inactive

When no command is requested, the module connection is in an idle state, wasting connection resources

At the same time, after processing the request, each module temporarily applies for creating a new connection to send the processing result. Each time a processing request is received, a new connection is created, and the resource overhead is large. When the number of nodes and modules is large, it will cause a single Rabbitmq service node. a lot of pressure

Images