WO2019062020A1

WO2019062020A1 - Asynchronous task unified processing method and apparatus, and storage medium

Info

Publication number: WO2019062020A1
Application number: PCT/CN2018/077672
Authority: WO
Inventors: 孙强
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-09-30
Filing date: 2018-02-28
Publication date: 2019-04-04
Also published as: CN108427599A

Abstract

Disclosed are an asynchronous task unified processing method and apparatus, and a storage medium. The method comprises: generating scripts of asynchronous tasks according to basic information of the asynchronous tasks, and adding the scripts into a database; adding configuration information and asynchronous task classes of the asynchronous tasks into a development code, adding service types involved in the asynchronous tasks into the asynchronous task classes, setting processing types involved in the service types, and setting corresponding service logic for the processing types; receiving the asynchronous tasks from a client, and storing the received asynchronous tasks in a task list according to a time sequence; reading, from the task list, an asynchronous task received earliest; and determining the service type and the processing type of the asynchronous task by means of a first determining step and a second determining step. The development time is shortened and the working efficiency is improved.

Description

Asynchronous task unified processing method, device and storage medium

Priority claim

This application claims the priority of the Chinese Patent Application entitled "Asynchronous Task Unified Processing Method, Apparatus and Storage Medium" submitted by the Chinese Patent Office on September 30, 2017, with the application number of 201710916221.7. The overall content of the Chinese patent application is The manner of reference is incorporated in the present application.

Technical field

The present application relates to the field of asynchronous processing technologies, and in particular, to a method, an apparatus, and a computer readable storage medium for a unified processing of asynchronous tasks.

Background technique

With the rapid development of Internet technology, more and more work can be done automatically through the application system. These applications can handle the different needs of different customers, so different asynchronous task applications need to be developed for the needs of customers.

At present, in the project development and application process of the asynchronous task application system, usually the same customer needs involve many asynchronous tasks, and each time an asynchronous task is added, the software development engineer needs to make the following changes: 1. In the database Add scripts for basic information definition of asynchronous tasks, such as task code, task name, and task author. 2. Add configuration information of asynchronous tasks, such as task code and task group, in the code, and add asynchronous task processing JAVA. Class; 3. Focus on the execution results of the new asynchronous task. Because the asynchronous tasks involved in the same requirements have the same basic information and configuration information, the software development engineers must perform some repetitive tasks, such as configuring the same basic information, each time an asynchronous task is added. This not only wastes human resources for development time and testing, but also reduces work efficiency.

Summary of the invention

In view of the above, the present application provides a method, a device, and a computer readable storage medium for asynchronous task processing, which can effectively shorten development time and improve work efficiency.

To achieve the above objective, the present application provides a unified processing method for asynchronous tasks, including:

Database initialization step: generate a script of the asynchronous task according to the basic information of the asynchronous task, and add the script to the database;

Code initialization step: Add the configuration information of the asynchronous task and the asynchronous task class in the development code, add the business type involved in the asynchronous task in the asynchronous task class, set the processing type involved in each business type, and set the corresponding processing type for each processing type. Business logic

Receiving step: receiving an asynchronous task from the client, and storing the received asynchronous tasks in a chronological order to the task list;

Reading step: reading the earliest received asynchronous task from the task list;

The first determining step is: determining whether the service type of the asynchronous task is a defined service type in the asynchronous task class, and if the service type of the asynchronous task is not a defined service type in the asynchronous task class, determining the asynchronous task The service type is an unknown service type, and the execution fails. If the service type of the asynchronous task is a defined service type in the asynchronous task class, the second determining step is performed;

a second determining step: determining whether the processing type of the asynchronous task is a processing type defined in the service type, and if the processing type of the asynchronous task is not a processing type defined in the service type, determining the asynchronous task The processing type is an unknown processing type, indicating that the execution fails. If the processing type of the asynchronous task is a defined processing type in the business type, the corresponding business logic is executed.

Preferably, the method further comprises:

The third determining step is: determining whether the corresponding business logic is successfully executed. If the execution is successful, the execution is successful; otherwise, the execution is failed.

Preferably, the first determining step further includes:

If the service type of the asynchronous task is not the defined service type in the asynchronous task class, the service type of the asynchronous task is prompted to be an unknown service type, and the corresponding service type is added in the asynchronous task class.

Preferably, the second determining step further comprises:

If the processing type of the read asynchronous task is not the processing type defined in the service type, the processing type of the asynchronous task is prompted to be an unknown processing type, and a corresponding processing type is added to the service type.

Preferably, the method further comprises:

Recording step: record the execution result of each asynchronous task and the reason for the failure of the execution, and count the number of times the asynchronous task fails to execute, record it in the same asynchronous task execution result list in a unified format, and feed back to the relevant personnel in a preset manner.

Preferably, the method further comprises:

The fourth determining step is: determining whether the number of times the asynchronous task fails is greater than a preset value;

If the number of times the asynchronous task fails to be greater than the preset value, the number of failed asynchronous tasks exceeds a preset value, and the task is no longer executed;

If the number of times the asynchronous task fails is less than or equal to the preset value, the asynchronous task is restarted.

In addition, the present application further provides an electronic device, including: a memory, a processor, and an asynchronous task unified processing system stored on the memory and operable on the processor, the asynchronous task unified processing system Executed by the processor, the following steps can be implemented:

Preferably, the first determining step further includes:

Preferably, the second determining step further comprises:

In addition, in order to achieve the above object, the present application further provides a computer readable storage medium, which includes an asynchronous task unified processing system, and when the asynchronous task unified processing system is executed by a processor, The asynchronous task unifies any step in the method.

The asynchronous task unified processing method, the electronic device and the computer readable storage medium proposed by the application add a script generated by the basic information of the asynchronous task to the database according to the needs of the client, and add configuration information of the asynchronous task in the development code. Asynchronous task class, adding the business type involved in the timing task in the asynchronous task class, and setting the processing type and business logic involved in each business type, and then uniformly processing the asynchronous tasks received from the client, thereby shortening the development time and improving the software. The efficiency of the engineer.

DRAWINGS

1 is a schematic diagram of a preferred embodiment of an electronic device of the present application;

2 is a functional block diagram of a preferred embodiment of the asynchronous task unified processing system of FIG. 1;

3 is a flowchart of a first embodiment of a method for uniformly processing an asynchronous task according to the present application;

4 is a flowchart of a second embodiment of a method for uniformly processing an asynchronous task according to the present application;

FIG. 5 is a setting frame diagram of an asynchronous task class of the present application.

The implementation, functional features and advantages of the present application will be further described with reference to the accompanying drawings.

Detailed ways

It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

FIG. 1 is a schematic diagram of a preferred embodiment of an electronic device 1 of the present application.

In this embodiment, the electronic device 1 may be a server, a smart phone, a tablet computer, a personal computer, a portable computer, and other electronic devices having computing functions.

The electronic device 1 includes a memory 11, a processor 12, a display 13, and an asynchronous task unified processing system 10 stored on the memory 11 and operable on the processor 12. The electronic device 1 connects one or more clients 3 through the network 2, receives the asynchronous tasks of the client from the client 3, and stores the received tasks into the task list in the order of receiving time. The electronic device 1 can also be connected to a database 4. In the present embodiment, the database 4 stores a script for generating basic information of an asynchronous task.

The network 2 may be a network of a local area network, a wide area network, a metropolitan area network, or the like, and may be a wired network or a wireless network.

The client 3 can be a desktop computer, a notebook, a tablet, a mobile phone, or other terminal device that can communicate with an electronic device through a network.

The memory 11 includes at least one type of readable storage medium. The at least one type of readable storage medium may be a non-volatile storage medium such as a flash memory, a hard disk, a multimedia card, a card type memory, or the like. In some embodiments, the memory 11 may be an internal storage unit of the electronic device 1, such as a hard disk of the electronic device 1. In other embodiments, the memory 11 may also be an external storage unit of the electronic device 1, such as a plug-in hard disk equipped on the electronic device 1, a smart memory card (SMC), and security. Digital (Secure Digital, SD) card, flash card (Flash Card), etc.

In this embodiment, the memory 11 can be used not only for storing application software and various types of data installed in the electronic device 1, such as an asynchronous task unified processing system 10, a task list, and an asynchronous task execution result list, and can also be used. Temporarily storing data that has been output or is about to be output.

The processor 12, in some embodiments, may be a Central Processing Unit (CPU), microprocessor or other data processing chip for running program code or processing data stored in the memory 11, such as performing asynchronous task unification. The computer program code or the like of the processing system 10.

Display 13 can be referred to as a display screen or display unit. In some embodiments, the display 13 may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch sensor, or the like. The display 13 is used to display information processed in the electronic device 1 and a work interface for displaying visualization, such as displaying the result of the task execution (execution failure or execution success), the number of task failures, and the reason for the task failure.

Preferably, the electronic device 1 may further include a user interface, and the user interface may include an input unit such as a keyboard, a voice output device such as an audio, a headphone, etc., optionally, the user interface may further include a standard wired interface and a wireless interface.

In the apparatus embodiment shown in FIG. 1, the program code of the asynchronous task unified processing system 10 is stored in the memory 11 as a computer storage medium, and the processor 12 executes the program code of the asynchronous task unified processing system 10 to implement the following functions:

Add a script that defines the underlying information of the asynchronous task in the database;

Setting the configuration information of the asynchronous task and the asynchronous task class in the development code, and adding all the service types involved in the timing task in the asynchronous task class, and setting all the processing types involved and the corresponding business logic for each service type;

Receiving an asynchronous task from the client, and storing the received asynchronous task in a chronological order to the task list;

Read the earliest received asynchronous task from the task list;

Determining whether the service type and the processing type of the asynchronous task are the defined service type and processing type in the asynchronous task class, and if the service type of the asynchronous task is not the defined service type or processing type in the asynchronous task class, determining The service type or processing type of the asynchronous task is an unknown service type or an unknown processing type. Otherwise, the corresponding business logic is executed.

For details, please refer to the following for a detailed description of the functional module diagram of the asynchronous task unified processing system 10.

As shown in FIG. 2, it is a functional block diagram of a preferred embodiment of the asynchronous task unified processing system 10 of FIG. A module as referred to in this application refers to a series of computer program instructions that are capable of performing a particular function.

In this embodiment, the asynchronous task unified processing system 10 includes a database initialization module 110, a code initialization module 120, a receiving module 130, a reading module 140, a determining module 150, a recording module 160, and a failure number determining module 170.

The database initialization module 110 is configured to generate a script of the asynchronous task according to the basic information of the asynchronous task, and add the script to the database. The basic information includes the task execution frequency, preset values, business name, and business processor. Assuming that an asynchronous task unified processing system 10 needs to be developed, the database initialization module 110 adds a script for generating an asynchronous task, such as a task execution frequency, a preset value, a service name, and a service processor, to the database 4. The task execution frequency (such as the task is fixed every 30 seconds), the preset value (such as the preset value is 20), and the service name includes the service type name and the processing type name; the service processor refers to the service processing corresponding to each processing type. people.

The code initialization module 120 is configured to add the configuration information of the asynchronous task and the asynchronous task class in the development code, add the business type involved in the asynchronous task in the asynchronous task class, set the processing type involved in each business type, and perform each processing for each service type. The type sets the corresponding business logic. Set the asynchronous task class, add all the business types corresponding to the asynchronous task in the asynchronous task class, set all the corresponding processing types in different business types, and set the corresponding business logic codes in different processing types. The service type is used to roughly distinguish different business logics, and the processing type is used to subdivide different business logics under the same business type. For example, set up an asynchronous task class for a developed asynchronous task, as shown in Figure 5. All the service types of the asynchronous task are added to the asynchronous task class. The service types include service type A ₁ , service type A _2, and service type A ₃ . All processing type traffic type A ₁ provided according to the service type A processing type ₁ comprises processing type B _11, type of processing B ₁₂ and the process type B ₁₃ and the like; provided the corresponding business logic code in a different type of processing, such as The corresponding business logic for processing type B ₁₁ is business logic C ₁₁ . The number of processing types of different service types may be different. For example, the number of processing types of the service type A ₁ is different from the number of processing types of the service type A ₂ . At the same time, the configuration information of the asynchronous task is set in the development code, and the configuration information includes the task code and the task group. The task code is used to standardize and quickly query the service type, processing type, and business logic of an asynchronous task. For example, if the service type of an asynchronous task is the service type A ₁ and the corresponding processing type is the processing type B ₁₂ , the asynchronous The tasks of the task are coded as A ₁ -B ₁₂ ; the task group is used to store the business logic in groups for the business type and processing type.

The receiving module 130 is configured to receive an asynchronous task from the client, and store the received asynchronous task in a chronological order to the task list. The receiving module 130 receives the asynchronous task of the client 3 through the network 2, and stores the received asynchronous tasks in the task list in the order of receiving time. For example, the receiving module 130 receives the asynchronous task a, the asynchronous task b, the asynchronous task c, and the asynchronous task d from the client 3, and the asynchronous task a, the asynchronous task b, the asynchronous task c, and the asynchronous task d are in accordance with the receiving time. The order is stored in the task list of the memory 11.

The reading module 140 is configured to read the earliest received asynchronous task from the task list. For example, the read module 140 reads the earliest received asynchronous task a in the task list.

The determining module 150 is configured to determine whether the service type and the processing type of the asynchronous task are the defined service type and processing type in the asynchronous task class, and if the service type of the asynchronous task is not the defined service type in the asynchronous task class Or the processing type determines that the service type or processing type of the asynchronous task is an unknown service type or an unknown processing type. Otherwise, the corresponding business logic is executed and whether the execution is successful. The determining module 150 determines whether the service type of the asynchronous task a read by the reading module 140 is a defined service type in the asynchronous task class. Assume that the business type of asynchronous task a is not the defined business type in the asynchronous task class, then the prompt: execution fails. Assuming that the service type of the asynchronous task a is a defined service type in the asynchronous task class, it is determined whether the processed type of the asynchronous task a is the processing type defined in the task type. Assuming that the processing type of the asynchronous task a is not the processing type defined in the service type, the prompt: the execution fails. Assuming that the processing type of the asynchronous task a is the processing type defined in the service type, the corresponding business logic is executed and it is determined whether the corresponding business logic is successfully executed. Assume that the execution is successful, then the prompt: the execution is successful; if the execution fails, the prompt: the execution fails.

The recording module 160 is configured to record the execution result of each asynchronous task and the reason for the failure of the execution, and count the number of times the asynchronous task fails to be executed, and record it in the same asynchronous task execution result list in a unified format, and feed back in a preset manner. Related personnel. The recording module 160 records the execution result of the asynchronous task a and the reason why the asynchronous task a fails to execute, and counts the number of times the asynchronous task a fails to execute, and finally records it in the same asynchronous task execution result list in a unified format, and displays it on the display 13 The way to feedback to the software development engineer. The software development engineer processes the failure reason of the asynchronous task a in the asynchronous task execution result list. For example, if the service type of the asynchronous task a is not the defined service type in the asynchronous task class, the software development engineer only needs to be in the asynchronous task class. Add the appropriate business type without having to add the basic and configuration information again.

The number of failures determining module 170 is configured to determine whether the number of failed asynchronous tasks is greater than a preset value; if the number of failed asynchronous tasks is greater than a preset value, the number of failed asynchronous tasks exceeds a preset value, and the task is no longer executed. If the number of times the asynchronous task fails is less than or equal to the preset value, the asynchronous task is restarted. The failure number determination module 170 determines whether the number of times the asynchronous task a fails to execute is greater than 20 times. Assuming that the asynchronous task a fails more than 20 times, it is prompted that the asynchronous task a fails more than 20 times and the asynchronous task is no longer executed; if the asynchronous task a fails less than or equal to 20 times, the asynchronous Task a is reloaded into the new task list and the asynchronous task a is re-executed.

As shown in FIG. 3, it is a flowchart of the first embodiment of the unified processing method for asynchronous tasks of the present application.

In the embodiment, when the processor 12 executes the computer program of the asynchronous task unified processing system 10 stored in the memory 11, the following steps are implemented for the asynchronous task unified processing method:

In step S10, the database initialization module 110 generates a script of the asynchronous task according to the basic information of the asynchronous task, and adds the script to the database. The basic information includes the task execution frequency, preset values, business name, and business processor. Assuming that an asynchronous task unified processing system 10 needs to be developed, the database initialization module 110 defines a basic generation information such as a task execution frequency, a preset value, a service name, and a service processor to generate a script, which is added to the database 4. The task execution frequency (such as the task is fixed every 30 seconds), the preset value (such as the preset value is 20), and the service name includes the service type name and the processing type name; the service processor refers to the service processing corresponding to each processing type. people.

Step S20, the code initialization module 120 adds the configuration information of the asynchronous task and the asynchronous task class in the development code, adds the business type involved in the asynchronous task in the asynchronous task class, sets the processing type involved in each service type, and performs for each processing The type sets the corresponding business logic. Set the asynchronous task class, add all the business types corresponding to the asynchronous task in the asynchronous task class, set all the corresponding processing types in different business types, and set the corresponding business logic codes in different processing types. The service type is used to roughly distinguish different business logics, and the processing type is used to subdivide different business logics under the same business type. For example, for example, an asynchronous task class of an insurance company claims system is set, and an service type of adding an asynchronous task in an asynchronous task class includes an accident insurance class A ₁ , a travel insurance class A ₂ , a health insurance class A ₃ , a corporate insurance class A ₄ , Property insurance class A ₅ and other business types. Among them, the types of treatment corresponding to accident insurance class A ₁ include one-year traffic accident insurance B ₁₁ , short-term traffic accident insurance B ₁₂ , aviation accident insurance B ₁₃ , one-year personal accident insurance B ₁₄ and short-term personal accident insurance B ₁₅ Types of. Set the one-year traffic accident insurance business logic C ₁₁ in the one-year traffic accident insurance B ₁₁ treatment type. At the same time, the configuration information of the asynchronous task is set in the development code, and the configuration information includes the task code and the task group. Where tasks and encoding specification for a quick reference asynchronous tasks corresponding to the service type, service type, and processing logic, e.g., a service type of asynchronous tasks accident insurance A _1, corresponding to the processing type is the short-term traffic accident insurance B _12, Then the task of the asynchronous task is coded as A ₁ -B ₁₂ ; the task group is used to store the business logic in groups for the service type and the processing type.

In step S30, the receiving module 130 receives the asynchronous task from the client, and stores the received asynchronous task in the chronological order to the task list. The receiving module 130 receives the asynchronous task of the client 3 through the network 2, and stores the received asynchronous tasks in the task list in the order of receiving time. For example, the receiving module 130 receives the asynchronous tasks of the Bank of Communications: the Bank of Communications flight delay case, the Bank of Communications accidental death/disability case, the Bank of Communications overseas travel case, and the Bank of Communications flight delay case, the Bank of Communications flight accidental death The asynchronous tasks of the disability case and the overseas travel case of the Bank of Communications are stored in the task list in the order of receiving time.

In step S40, the reading module 140 reads the earliest received asynchronous task from the task list. For example, the reading module 140 reads the earliest received asynchronous task in the task list as a Bank of Communications flight delay case.

In step S50, the determining module 150 determines whether the service type of the asynchronous task is a defined service type in the asynchronous task class. If the service type of the asynchronous task is not a defined service type in the asynchronous task class, the asynchronous task is determined. The service type is an unknown service type, and step S100 is performed. If the service type of the asynchronous task is a defined service type in the asynchronous task class, step S60 is performed. The determining module 150 determines whether the service type of the read asynchronous task is a defined service type in the asynchronous task class. If the service type of the asynchronous task is not the defined service type in the asynchronous task class, step S100 is performed; if the service type of the asynchronous task is the defined service type in the asynchronous task class, step S60 is performed. For example, if the judgment module 150 determines that the business type of the read traffic bank flight delay case is the accident insurance class A ₁ defined in the asynchronous task class, step S60 is performed.

In step S60, the determining module 150 determines whether the processing type of the asynchronous task is a processing type defined in the service type. If the processing type of the asynchronous task is not the processing type defined in the service type, determining the asynchronous task If the processing type of the asynchronous task is the processing type defined in the service type, step S70 is performed. The determining module 150 determines whether the processing type of the read asynchronous task is a processing type defined in the task type. Assuming that the processing type of the asynchronous task is not the processing type defined in the service type, step S100 is performed; if the processing type of the asynchronous task is the processing type defined in the service type, step S70 is performed. For example, the type of processing Bank of flights judgment module 150 judges read delay case for accident insurance as defined in A _1-year traffic accident insurance B _11, proceed to step S70.

Step S70: When the processing type of the read service type is a processing type defined in the service type, execute corresponding business logic. For example, the judging module 150 judges that the processing type of the read traffic bank flight delay case is the one-year traffic accident insurance B ₁₁ defined in the task type, and executes the one-year traffic accident insurance business logic.

In step S100, if the corresponding judgment is negative, the execution failure is prompted. If the judgment module 150 performs the corresponding judgment to be no, the prompt: the execution fails.

The asynchronous task unified processing method proposed in this embodiment adds a script for defining the basic information of the asynchronous task in the database; then sets all the business logics corresponding to the business type, the processing type, and the processing type in the asynchronous task class, and simultaneously develops the code. The configuration information of the asynchronous task is set; the first determining step and the second determining step are performed to make different asynchronous tasks processed in the corresponding business logic, thereby shortening the development time and improving the working efficiency.

As shown in FIG. 4, it is a flowchart of the second embodiment of the method for uniformly processing asynchronous tasks of the present application.

In this embodiment, the asynchronous task unified processing method includes: Step S10 - Step S140. The steps S10 to S70 and the step S100 are substantially the same as those in the first embodiment, and details are not described herein again.

In step S80, the determining module 150 determines whether the corresponding business logic is successfully executed. If the execution is successful, the execution is successful; otherwise, the execution fails. For example, the determination module 150 determines whether the execution of the one-year traffic accident insurance business logic is successful. Assuming that the execution is successful, step S90 is performed; if the execution fails, step S100 is performed.

In step S90, if the execution of the corresponding business logic is successful, the execution is prompted to be successful. If the judgment module 150 performs the business logic execution of the one-year traffic accident insurance successfully, it prompts: the execution is successful.

In step S110, the recording module 160 records the execution result of each asynchronous task and the reason for the failure of the execution, and counts the number of times the asynchronous task fails to execute, and records it in the same asynchronous task execution result list in a unified format, and feeds back in a preset manner. Related personnel. The recording module 160 records the execution result of the asynchronous task and the reason for the asynchronous task execution failure, and counts the number of times the asynchronous task fails to execute, and finally records in the same asynchronous task execution result list in a unified format, and provides feedback in the manner displayed by the display 13. To a software development engineer. For example, if the Bank of Communications flight delay case fails to execute, the record module 160 records the name of the asynchronous task: the Bank of Communications flight delay case, the reason for the failure (for example, the service type of the Bank of Communications flight delay case is not the defined service type in the asynchronous task class) and The number of execution failures is increased by one. (If the number of failures is 2 before the task is processed, the number of failures after the task is 3). After all the asynchronous tasks have been processed, the results are recorded in a unified format in the same asynchronous task execution result list, and fed back to the software development engineer in the manner displayed by the display 13. The preset manner further includes a mail or a short message.

In step S120, the failure number determination module 170 determines whether the number of times the asynchronous task fails is greater than a preset value; if the number of failed asynchronous tasks is greater than a preset value, step S130 is performed; if the number of failed asynchronous tasks is less than or equal to a preset For the value, step S140 is performed. The number of failures determining module 170 determines whether the number of times the asynchronous task fails is greater than a preset value; if the number of failed asynchronous tasks is greater than a preset value, step S130 is performed; and if the number of failed asynchronous tasks is less than or equal to a preset value, Step S140 is performed. For example, if the number-of-failure determination module 170 determines that the number of times the bankruptcy flight delay case has failed to be processed is greater than 20 times, step S130 is performed.

Step S130: If the number of failures of the asynchronous task is greater than a preset value, the prompting: the number of failed asynchronous tasks exceeds a preset value, and the asynchronous task is no longer executed. For example, if the Bank of Communications flight delay case fails to process more than 20 times, it indicates that the Bank of Communications flight delay case has failed more than 20 times and the task is no longer executed.

In step S140, if the number of failures of the asynchronous task is less than or equal to the preset value, the determining module 150 processes the failure reason and restarts the execution of the asynchronous task. For example, if the number of failures of the Bank of Communications flight delay case is less than or equal to 20 times, the software development engineer adds the corresponding service type or processing type according to the failure reason of the asynchronous task in the asynchronous task execution result list and puts the Bank of Communications flight delay case to Restart the asynchronous task in the new task list.

Compared with the first embodiment, the asynchronous task unified processing method proposed in this embodiment adds a script defined by the basic information of the asynchronous task in the database; then sets all the service types, processing types, and processing types in the asynchronous task class. Corresponding business logic, at the same time, setting configuration information of the asynchronous task in the development code; and processing the different asynchronous tasks in the corresponding business logic by using the first determining step, the second determining step, the third determining step, and the fourth determining step, It also counts the number of failures and the reasons for the failure of asynchronous tasks. It is convenient for software development engineers to solve problems for failure reasons, shorten development time, and improve work efficiency.

In addition, the embodiment of the present application further provides a computer readable storage medium, which includes an asynchronous task unified processing system 10, and when the asynchronous task unified processing system 10 is executed by the processor, the following operations are implemented:

Preferably, the method further comprises:

Preferably, the first determining step further includes:

Preferably, the second determining step further comprises:

Preferably, the method further comprises:

Recording step: record the execution result of each asynchronous task and the reason for the failure, and count the number of failed asynchronous task executions, record them in the same asynchronous task execution result list in a unified format, and feed back to relevant personnel in a preset manner.

Preferably, the method further comprises:

The specific implementation manner of the computer readable storage medium of the present application is substantially the same as the specific implementation method of the above-mentioned asynchronous task unified processing method, and details are not described herein again.

The serial numbers of the embodiments of the present application are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better. Implementation. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM as described above). , a disk, an optical disk, including a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the methods described in the various embodiments of the present application.

The above is only a preferred embodiment of the present application, and is not intended to limit the scope of the patent application, and the equivalent structure or equivalent process transformations made by the specification and the drawings of the present application, or directly or indirectly applied to other related technical fields. The same is included in the scope of patent protection of this application.

Claims

An asynchronous task unified processing method, the method comprising:

Database initialization step: generate a script of the asynchronous task according to the basic information of the asynchronous task, and add the script to the database;

Code initialization step: Add the configuration information of the asynchronous task and the asynchronous task class in the development code, add the business type involved in the asynchronous task in the asynchronous task class, set the processing type involved in each business type, and set the corresponding processing type for each processing type. Business logic

Receiving step: receiving an asynchronous task from the client, and storing the received asynchronous tasks in a chronological order to the task list;

Reading step: reading the earliest received asynchronous task from the task list;

The first determining step is: determining whether the service type of the asynchronous task is a defined service type in the asynchronous task class, and if the service type of the asynchronous task is not a defined service type in the asynchronous task class, determining the asynchronous task The service type is an unknown service type, and if the service type of the asynchronous task is a defined service type in the asynchronous task class, performing a second determining step;

a second determining step: determining whether the processing type of the asynchronous task is a processing type defined in the service type, and if the processing type of the asynchronous task is not a processing type defined in the service type, determining the asynchronous task The processing type is an unknown processing type. If the processing type of the asynchronous task is a defined processing type in the service type, the corresponding business logic is executed.
The method for processing asynchronous tasks according to claim 1, wherein the method further comprises:

The third determining step is: determining whether the corresponding business logic is successfully executed. If the execution is successful, the execution is successful; otherwise, the execution is failed.
The method for processing the asynchronous task according to claim 1, wherein the first determining step further comprises:

If the service type of the asynchronous task is not the defined service type in the asynchronous task class, the service type of the asynchronous task is prompted to be an unknown service type, and the corresponding service type is added in the asynchronous task class.
The method for processing the asynchronous task according to claim 1, wherein the second determining step further comprises:

If the processing type of the read asynchronous task is not the processing type defined in the service type, the processing type of the asynchronous task is prompted to be an unknown processing type, and a corresponding processing type is added in the service type.
The method for processing asynchronous tasks according to any one of claims 1 to 4, further comprising:

Recording step: record the execution result of each asynchronous task and the reason for the failure, and count the number of failed asynchronous task executions, record them in the same asynchronous task execution result list in a unified format, and feed back to relevant personnel in a preset manner.
The method for processing asynchronous tasks according to claim 1, wherein the method further comprises:

The fourth determining step is: determining whether the number of times the asynchronous task fails is greater than a preset value;

If the number of times the asynchronous task fails to be greater than the preset value, the number of failed asynchronous tasks exceeds a preset value, and the task is no longer executed;

If the number of times the asynchronous task fails is less than or equal to the preset value, the asynchronous task is restarted.
The method for processing asynchronous tasks according to claim 1, wherein the service type is used to roughly distinguish different business logics, and the processing type is used to subdivide different business logics under the same service type.
An electronic device, comprising: a memory, a processor, and an asynchronous task unified processing system stored on the memory and operable on the processor, wherein the asynchronous task unified processing system is The processor executes, and the following steps can be implemented:

Database initialization step: generate a script of the asynchronous task according to the basic information of the asynchronous task, and add the script to the database;

Code initialization step: Add the configuration information of the asynchronous task and the asynchronous task class in the development code, add the business type involved in the asynchronous task in the asynchronous task class, set the processing type involved in each business type, and set the corresponding processing type for each processing type. Business logic

Receiving step: receiving an asynchronous task from the client, and storing the received asynchronous tasks in a chronological order to the task list;

Reading step: reading the earliest received asynchronous task from the task list;

The first determining step is: determining whether the service type of the asynchronous task is a defined service type in the asynchronous task class, and if the service type of the asynchronous task is not a defined service type in the asynchronous task class, determining the asynchronous task The service type is an unknown service type, and if the service type of the asynchronous task is a defined service type in the asynchronous task class, performing a second determining step;

a second determining step: determining whether the processing type of the asynchronous task is a processing type defined in the service type, and if the processing type of the asynchronous task is not a processing type defined in the service type, determining the asynchronous task The processing type is an unknown processing type. If the processing type of the asynchronous task is a defined processing type in the service type, the corresponding business logic is executed.
The electronic device according to claim 8, wherein the asynchronous task unified processing system is executed by the processor, and the following steps are also implemented:

The third determining step is: determining whether the corresponding business logic is successfully executed. If the execution is successful, the execution is successful; otherwise, the execution is failed.
The electronic device according to claim 8, wherein the first determining step further comprises:

If the service type of the asynchronous task is not the defined service type in the asynchronous task class, the service type of the asynchronous task is prompted to be an unknown service type, and the corresponding service type is added in the asynchronous task class.
The electronic device according to claim 8, wherein the second determining step further comprises:

If the processing type of the read asynchronous task is not the processing type defined in the service type, the processing type of the asynchronous task is prompted to be an unknown processing type, and a corresponding processing type is added to the service type.
The electronic device according to any one of claims 8 to 11, wherein the asynchronous task unified processing system is executed by the processor, and the following steps are also implemented:

Recording step: record the execution result of each asynchronous task and the reason for the failure, and count the number of failed asynchronous task executions, record them in the same asynchronous task execution result list in a unified format, and feed back to relevant personnel in a preset manner.
The electronic device according to claim 8, wherein the asynchronous task unified processing system is executed by the processor, and the following steps are also implemented:

The fourth determining step is: determining whether the number of times the asynchronous task fails is greater than a preset value;

If the number of times the asynchronous task fails to be greater than the preset value, the number of failed asynchronous tasks exceeds a preset value, and the task is no longer executed;

If the number of times the asynchronous task fails is less than or equal to the preset value, the asynchronous task is restarted.
The electronic device according to claim 8, wherein the service type is used to roughly distinguish different business logics, and the processing type is used to subdivide different business logics under the same service type.
A computer readable storage medium, comprising: an asynchronous task unified processing system, wherein the unified asynchronous task unified processing system is executed by a processor to implement the following steps:

Database initialization step: generate a script of the asynchronous task according to the basic information of the asynchronous task, and add the script to the database;

Code initialization step: Add the configuration information of the asynchronous task and the asynchronous task class in the development code, add the business type involved in the asynchronous task in the asynchronous task class, set the processing type involved in each business type, and set the corresponding processing type for each processing type. Business logic

Receiving step: receiving an asynchronous task from the client, and storing the received asynchronous tasks in a chronological order to the task list;

Reading step: reading the earliest received asynchronous task from the task list;

The first determining step is: determining whether the service type of the asynchronous task is a defined service type in the asynchronous task class, and if the service type of the asynchronous task is not a defined service type in the asynchronous task class, determining the asynchronous task The service type is an unknown service type, and if the service type of the asynchronous task is a defined service type in the asynchronous task class, performing a second determining step;

a second determining step: determining whether the processing type of the asynchronous task is a processing type defined in the service type, and if the processing type of the asynchronous task is not a processing type defined in the service type, determining the asynchronous task The processing type is an unknown processing type. If the processing type of the asynchronous task is a defined processing type in the service type, the corresponding business logic is executed.
The computer readable storage medium according to claim 15, wherein the asynchronous task unified processing system is executed by the processor, and the following steps are also implemented:

The third determining step is: determining whether the corresponding business logic is successfully executed. If the execution is successful, the execution is successful; otherwise, the execution is failed.
The computer readable storage medium according to claim 15, wherein the first determining step further comprises:

If the service type of the asynchronous task is not the defined service type in the asynchronous task class, the service type of the asynchronous task is prompted to be an unknown service type, and the corresponding service type is added in the asynchronous task class.
The computer readable storage medium according to claim 15, wherein the second determining step further comprises:

If the processing type of the read asynchronous task is not the processing type defined in the service type, the processing type of the asynchronous task is prompted to be an unknown processing type, and a corresponding processing type is added to the service type.
The computer readable storage medium according to any one of claims 15 to 18, wherein the asynchronous task unified processing system is executed by the processor, and the following steps are also implemented:

Recording step: record the execution result of each asynchronous task and the reason for the failure, and count the number of failed asynchronous task executions, record them in the same asynchronous task execution result list in a unified format, and feed back to relevant personnel in a preset manner.
The computer readable storage medium according to claim 15, wherein the asynchronous task unified processing system is executed by the processor, and the following steps are also implemented:

The fourth determining step is: determining whether the number of times the asynchronous task fails is greater than a preset value;

If the number of times the asynchronous task fails to be greater than the preset value, the number of failed asynchronous tasks exceeds a preset value, and the task is no longer executed;

If the number of times the asynchronous task fails is less than or equal to the preset value, the asynchronous task is restarted.