CN119003201A

CN119003201A - Method for unified asynchronous processing of interfaces

Info

Publication number: CN119003201A
Application number: CN202410987926.8A
Authority: CN
Inventors: 代存折; 石小明; 吴奕刚
Original assignee: Hangzhou Arcvideo Technology Co ltd
Current assignee: Hangzhou Arcvideo Technology Co ltd
Priority date: 2024-07-23
Filing date: 2024-07-23
Publication date: 2024-11-22

Abstract

The invention discloses a method for unified and asynchronous processing of interfaces, which comprises the following steps: defining universal asynchronous parameters by using an asynchronous parameter definition module; setting the number of concurrent threads; sending a request to an external interface module by using an access client; setting a verification module to verify whether the request parameters are complete and meet the specification, checking whether the request parameters are asynchronous, determining whether an asynchronous processing mode is adopted, and if the request parameters pass the verification, entering the next step of processing; otherwise, returning error information to the access client; after verification is passed, an asynchronous parameter definition module is set to analyze asynchronous parameters in the request; setting an asynchronous thread pool module, and adding an asynchronous task into a task queue of a thread pool according to the configured asynchronous parameter; and after the asynchronous execution module is set to take out the task from the task queue, reading asynchronous parameters in the task, executing corresponding business logic and sending a result to the access client.

Description

Method for unified asynchronous processing of interfaces

Technical Field

The invention belongs to the technical field of computers, and particularly relates to a method for unified and asynchronous processing of interfaces.

Background

In the current software development and information technology field, interface processing is a key link for the interaction of a software system with the outside world. With rapid development of network technology and increasing complexity of service demands, higher demands are being placed on the speed, efficiency and stability of interface processing. Traditional synchronous interface processing methods often present performance bottlenecks when processing a large number of concurrent requests, resulting in slow system responses and even crashes. Therefore, how to design and implement an efficient and unified interface asynchronous processing method becomes an important research direction. The prior art has the following defects: (1) Callback jail (Callback Hell) problem: in complex asynchronous processing flows, the use of callback functions typically results in code nesting levels that are too deep, forming so-called "callback prisons. This writing not only makes the code difficult to read and maintain, but also increases the likelihood of errors. As the number of asynchronous operations increases, the number of nesting layers of callback functions also increases, further exacerbating the problem. (2) difficulty in handling errors: in callback notification mechanisms, error handling typically needs to be done separately in each callback function, which increases redundancy of the code. In addition, because callback functions may be scattered in multiple locations in code, it is difficult to track a specific source of error when an error occurs. Meanwhile, because dependency relationship may exist between callback functions, an error of one callback function may cause that a plurality of subsequent callback functions cannot be executed normally. (3) control flow is difficult to understand: the callback notification mechanism employs a nonlinear control flow model that is more difficult to understand than traditional linear control flow models. In the callback function, control of the program is transferred to the asynchronous operation, and the control is recovered by the callback function after the asynchronous operation is completed. This frequent transfer of control complicates the control flow of the program and increases the difficulty of understanding and debugging. In addition, since callback functions may be called at different points in time, it is difficult to predict and control the execution order of programs.

Disclosure of Invention

In view of the problems, the invention provides a method for unified asynchronous processing of interfaces, which introduces an asynchronous processing mechanism and improves the response speed and concurrent processing capacity of interface services.

In order to solve the technical problems, the invention adopts the following technical scheme:

The method for unified asynchronous processing of the interface is applied to a system for unified asynchronous processing of the interface comprising an access client and an interface server, wherein the interface server further comprises an external interface module, a verification module, an asynchronous parameter definition module, an asynchronous thread pool module and an asynchronous execution module, and comprises the following steps:

Defining universal asynchronous parameters by using an asynchronous parameter definition module, wherein the universal asynchronous parameters comprise parameters required by service logic execution; setting the number of concurrent threads to limit the number of asynchronous tasks executed simultaneously; transmitting the defined universal asynchronous parameter and the number of concurrent threads to an asynchronous thread pool module;

the method comprises the steps that an access client side is utilized to send a request to an external interface module, the request comprises interface calling parameters, the external interface module receives the request from the access client side, and the external interface module transmits the received request to a verification module for verification;

Setting a verification module to verify whether the request parameters are complete and meet the specification, checking whether the request parameters are asynchronous, determining whether an asynchronous processing mode is adopted, and if the request parameters pass the verification, entering the next step of processing; otherwise, returning error information to the access client;

after verification is passed, an asynchronous parameter definition module is set to analyze asynchronous parameters in the request, and corresponding asynchronous processing parameters are configured according to the analyzed asynchronous parameters;

setting an asynchronous thread pool module, adding asynchronous tasks into a task queue of a thread pool according to configured asynchronous parameters, and taking out tasks from the task queue and executing the tasks by threads in the thread pool according to a first-in first-out principle;

And after the asynchronous execution module is set to take out the task from the task queue, reading asynchronous parameters in the task, executing corresponding business logic, setting the asynchronous execution module to monitor the execution state of the task in the task execution process, setting the asynchronous execution module to generate a task execution result after the execution of the asynchronous task is completed, and sending the result to the access client according to an asynchronous callback address and an asynchronous callback identifier in the asynchronous parameters.

In a possible implementation manner, the interface call parameter includes whether the interface is asynchronous, and is a boolean value for determining whether the interface request should enable asynchronous processing.

In a possible implementation manner, the interface call parameter includes an asynchronous callback address, which is a URL or callback interface address, and is used for notifying the access client of the processing result after the asynchronous task is completed.

In a possible implementation manner, the interface calling parameter includes an asynchronous callback identifier, which is a unique identifier and is used for the access client to confirm the request to which the callback result belongs.

The invention has the following beneficial effects:

(1) Unified processing and configuration: by introducing the asynchronous parameter definition module, unified configuration and management of asynchronous operation are realized, so that a developer can flexibly define and configure parameters and flows of asynchronous operation according to different service scenes. The unified processing mode greatly improves the maintainability and the expandability of the system and reduces the complexity of development and maintenance.

(2) Response speed and concurrent processing capacity are improved: by asynchronous processing, operations which consume longer time are carried out in the background, so that the response speed of the interface is improved. Meanwhile, by utilizing the asynchronous thread pool module, the system can process a plurality of asynchronous operations concurrently, and the concurrent processing capacity of the system is improved. This enables the system to easily cope with a large number of concurrent requests, ensuring the stability and availability of services.

(3) Simplifying callback processing: although a callback notification mechanism is adopted, the callback prison problem is effectively avoided through the optimized design and implementation. By introducing asynchronous execution modules and standardized interface designs, the system is able to handle callback logic in a clearer and more concise manner. This makes the code easier to read and maintain, reducing the possibility of errors.

(4) Enhanced error handling capability: compared with the traditional callback notification mechanism, the callback notification mechanism has obvious improvement in the aspect of error processing. The system provides a global error handling mechanism so that a developer can handle errors in all asynchronous operations in one centralized location. The method not only simplifies the error processing flow, but also improves the efficiency and accuracy of error processing.

(5) Predictable control flow: although asynchronous processing introduces nonlinear control flows, the control flows are made predictable and controllable by reasonable design and scheduling strategies. The system can clearly track and record the execution state and result of asynchronous operation, so that a developer can debug and troubleshoot problems more conveniently.

Drawings

FIG. 1 is a schematic block diagram of an interface unified asynchronous processing system employed in the method of interface unified asynchronous processing according to an embodiment of the present invention;

Fig. 2 is a flow chart of a method for interface unified asynchronous processing according to an embodiment of the invention.

Detailed Description

The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

Referring to fig. 1 and fig. 2, a method for unified asynchronous processing of an interface according to an embodiment of the present invention is applied to a system including an access client and an interface server, where the interface server further includes an external interface module, a verification module, an asynchronous parameter definition module, an asynchronous thread pool module, and an asynchronous execution module, and before the system formally starts to work, the system may be initialized, and necessary initialization operations including loading system configuration, creating and initializing an asynchronous thread pool, starting an external interface module, and the like, and at the same time, ensuring that a communication mechanism between all modules is already established and in a normal working state, including the following steps:

S10, defining universal asynchronous parameters by using an asynchronous parameter definition module, wherein the universal asynchronous parameters comprise parameters required by service logic execution; setting the number of concurrent threads to limit the number of asynchronous tasks executed simultaneously; transmitting the defined universal asynchronous parameter and the number of concurrent threads to an asynchronous thread pool module;

S20, sending a request to an external interface module by using an access client, wherein the request comprises interface calling parameters, the external interface module receives the request from the access client, and the external interface module transmits the received request to a verification module for verification;

S30, a verification module is arranged to verify whether the request parameters are complete and meet the specification, check whether the request parameters are asynchronous, determine whether an asynchronous processing mode is adopted, and enter the next step of processing if the request parameters pass the verification; otherwise, returning error information to the access client;

S40, after verification, the asynchronous parameter definition module is set to analyze the asynchronous parameters in the request, and corresponding asynchronous processing parameters are configured according to the analyzed asynchronous parameters; these parameters include the number of concurrent threads, task timeout time, etc. to ensure the efficiency and stability of asynchronous processing;

S50, setting an asynchronous thread pool module, adding asynchronous tasks into a task queue of a thread pool according to configured asynchronous parameters, and taking out tasks from the task queue and executing the tasks by threads in the thread pool according to a first-in first-out principle;

S60, setting an asynchronous execution module to take out tasks from a task queue, reading asynchronous parameters in the tasks, executing corresponding business logic, setting the asynchronous execution module to monitor the execution state of the tasks in the task execution process, setting the asynchronous execution module to generate task execution results after the execution of the asynchronous tasks is completed, and sending the results to an access client according to asynchronous callback addresses and asynchronous callback identifiers in the asynchronous parameters. Thus, the access client can confirm which request the callback result belongs to according to the callback identifier, and accordingly, the access client can process correspondingly.

During the entire process, the system captures and processes errors that may occur. For errors that cannot be handled, the system records detailed error logs, including error types, error descriptions, time of occurrence, etc., for subsequent investigation and repair. At the same time, the system records key operation logs and performance data for performance analysis and optimization.

In a specific application example, the interface call parameters include whether to be asynchronous, an asynchronous callback address, and an asynchronous callback identifier. Wherein whether asynchronous is a boolean value is used to determine whether the interface request should enable asynchronous processing. The asynchronous callback address is a URL or callback interface address and is used for notifying the access client of the processing result after the asynchronous task is completed. The asynchronous callback identifier is a unique identifier and is used for the access client to confirm the request to which the callback result belongs.

By the method for unified asynchronous processing of the interfaces, an asynchronous processing mechanism is introduced, and the response speed and the concurrent processing capacity of the interface service are improved; the management and configuration of asynchronous tasks are simplified through unified asynchronous parameter definition; the thread pool technology is used, so that the utilization rate of system resources is optimized; clear flow control and error processing mechanisms are provided, and stability and reliability of the system are enhanced.

It should be understood that the exemplary embodiments described herein are illustrative and not limiting. Although one or more embodiments of the present invention have been described with reference to the accompanying drawings, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention as defined by the following claims.

Claims

1. The method is characterized by being applied to a system for interface unified asynchronous processing comprising an access client and an interface server, wherein the interface server further comprises an external interface module, a verification module, an asynchronous parameter definition module, an asynchronous thread pool module and an asynchronous execution module, and the method comprises the following steps of:

2. The method of claim 1, wherein the interface call parameter includes whether asynchronous is a boolean value for determining whether the interface request should enable asynchronous processing.

3. The method for unified asynchronous processing of interfaces according to claim 1, wherein the interface call parameter comprises an asynchronous callback address, which is a URL or callback interface address, for notifying the access client of the processing result after the completion of the asynchronous task.

4. The method for unified and asynchronous processing of an interface according to claim 1, wherein the interface call parameter includes an asynchronous callback identifier, which is a unique identifier, for the visiting client to confirm the request to which the callback result belongs.