CN112965850A - Method and equipment for realizing workflow in middle platform system - Google Patents
Method and equipment for realizing workflow in middle platform system Download PDFInfo
- Publication number
- CN112965850A CN112965850A CN202110309859.0A CN202110309859A CN112965850A CN 112965850 A CN112965850 A CN 112965850A CN 202110309859 A CN202110309859 A CN 202110309859A CN 112965850 A CN112965850 A CN 112965850A
- Authority
- CN
- China
- Prior art keywords
- task
- workflow
- subtask
- tasks
- database
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 43
- 230000007246 mechanism Effects 0.000 claims abstract description 20
- 230000008569 process Effects 0.000 claims abstract description 8
- 230000015654 memory Effects 0.000 claims description 29
- 238000004590 computer program Methods 0.000 claims description 14
- 230000006870 function Effects 0.000 description 6
- 230000005291 magnetic effect Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000003936 working memory Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0787—Storage of error reports, e.g. persistent data storage, storage using memory protection
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24553—Query execution of query operations
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Computational Linguistics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Mathematical Physics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The purpose of the application is to provide a scheme for realizing workflow in a middle station system. The method comprises the steps of reading a workflow containing a plurality of tasks from a database, executing the tasks of the workflow, writing a task record related to each task into the database when each task in the workflow is completed, and performing exception capture at the task execution place by using an exception handling mechanism in the task execution process. Compared with the prior art, the scheme provided by the application can enable the workflow of the middle platform system to meet the requirements of parallel task exception tolerance and multiple exception handling of the parallel task, and improves the stability of the middle platform system. Furthermore, the scheme provided by the application can enable the workflow of the middle station system to meet the requirements of task rollback, task redoing and the like, so that the user experience is improved.
Description
Technical Field
The present application relates to the field of information technology, and in particular, to a technology for implementing a workflow in a middlebox system.
Background
Modern middlebox systems carry complex business logic of enterprise business operation, and workflow of the middlebox systems needs to realize complex operation arrangement. These complex business logic consists of a series of asynchronous calls, between which complex constraints and conditional branches also exist. The workflow of the middlebox system cannot fulfill the following requirements if it is called asynchronously as in the conventional art: (1) parallel task exception tolerance; (2) processing multiple exceptions by parallel tasks; (3) the task is rolled back, namely after the task is in error, the preorder task can be rolled back; (4) and (4) task redoing, namely the task can be continuously completed after power failure.
Currently there are some simple implementations of JavaScript-based workflows in open source software libraries. However, these workflows are not perfect and do not have complete functions such as multiple exception handling, task rollback, task redo, and the like.
Disclosure of Invention
An object of the present application is to provide a method and apparatus for implementing a workflow in a middlebox system.
According to an aspect of the present application, there is provided a method of implementing a workflow in a middlebox system, wherein the method comprises:
reading a workflow from a database, and executing tasks of the workflow, wherein the workflow comprises a plurality of tasks;
when each task in the workflow is completed, writing a task record related to the task into the database;
and in the process of task execution, an exception handling mechanism is utilized to perform exception capture at the task execution place.
According to another aspect of the present application, there is also provided an apparatus for implementing a workflow in a middesk system, wherein the apparatus includes:
the execution module is used for reading a workflow from a database and executing tasks of the workflow, wherein the workflow comprises a plurality of tasks;
the recording module is used for writing the task record related to each task in the workflow into the database when the task is completed;
and the exception handling module is used for carrying out exception capture at the task execution place by utilizing an exception handling mechanism in the task execution process.
According to yet another aspect of the present application, there is also provided a computing device, wherein the device comprises a memory for storing computer program instructions and a processor for executing the computer program instructions, wherein the computer program instructions, when executed by the processor, trigger the device to perform the method of implementing a workflow in a staging system.
According to yet another aspect of the present application, there is also provided a computer readable medium having stored thereon computer program instructions executable by a processor to implement the method of implementing a workflow in a staging system.
The method comprises the steps of reading a workflow containing a plurality of tasks from a database, executing the tasks of the workflow, writing task records related to the tasks into the database when each task in the workflow is completed, and performing exception capture at a task execution place by using an exception handling mechanism in the task execution process. Compared with the prior art, the scheme provided by the application can enable the workflow of the middle platform system to meet the requirements of parallel task exception tolerance and multiple exception handling of the parallel task, and improves the stability of the middle platform system. Furthermore, the scheme provided by the application can enable the workflow of the middle station system to meet the requirements of task rollback, task redoing and the like, so that the user experience is improved.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 is a flow chart of a method for implementing a workflow in a central station system according to an embodiment of the present application;
fig. 2 is a schematic diagram of an apparatus for implementing workflow in a middesk system according to an embodiment of the present application.
The same or similar reference numbers in the drawings identify the same or similar elements.
Detailed Description
The present application is described in further detail below with reference to the attached figures.
In a typical configuration of the present application, the terminal, the device serving the network, and the trusted party each include one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, which include both non-transitory and non-transitory, removable and non-removable media, may implement the information storage by any method or technology. The information may be computer readable instructions, data structures, program means, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device.
The embodiment of the application provides a method for realizing the workflow in the middle platform system, which can enable the workflow of the middle platform system to meet the requirements of parallel task exception tolerance and multiple exception handling of parallel tasks, and improve the stability of the middle platform system. Furthermore, the method can enable the workflow of the middle platform system to meet the requirements of task rollback, task redoing and the like, so that the user experience is improved.
In a practical scenario, the device performing the method may be a user equipment, a network device, or a device formed by integrating the user equipment and the network device through a network. The user equipment includes, but is not limited to, a terminal device such as a smartphone, a tablet computer, a Personal Computer (PC), and the like, and the network device includes, but is not limited to, a network host, a single network server, multiple network server sets, or a cloud computing-based computer set. Here, the Cloud is made up of a large number of hosts or web servers based on Cloud Computing (Cloud Computing), which is a type of distributed Computing, one virtual computer consisting of a collection of loosely coupled computers.
Fig. 1 is a flowchart of a method for implementing a workflow in a central station system according to an embodiment of the present application, where the method includes step S101, step S102, and step S103.
Step S101, reading a workflow from a database, and executing tasks of the workflow, wherein the workflow comprises a plurality of tasks.
For example, the database may be a MySQL database. Each workflow is a row of records in the database. Each time a task is to be performed, a workflow is read out of the database and execution begins.
In some embodiments, the tasks of the workflow are described in a structured language, which allows the structure of the entire task to be more clearly described.
An example of describing a task in a structured language is as follows:
in some embodiments, the type of task of the workflow comprises at least any one of: a parallel task, wherein a plurality of sub-tasks of the parallel task are executed simultaneously; a serial task, wherein a plurality of subtasks of the serial task are executed in sequence; a single task.
For example, several subtasks of the parallel task are executed simultaneously, and these subtasks are considered as a whole (the parallel task), which as a whole has an indication of success or failure of the execution of the task. Specifically, the parallel tasks may be further divided into two types, an error-sensitive parallel task and an error-insensitive parallel task. An error-sensitive parallel task, if one of the subtasks fails during execution, the entire parallel task fails. And if one subtask fails to execute the parallel task, the whole parallel task can still be successfully executed.
Several subtasks of the serial task are executed in sequence and these subtasks are treated as a whole (the serial task) and as a whole these subtasks are marked by success or failure of the task execution. The serial tasks are all error sensitive. When the serial task is executed, as long as one subtask has an error, the whole serial task fails.
The single task is simple, i.e. it is simply executed, and has a result of success or failure in execution. The single task is the most basic execution unit in the workflow.
And step S102, when each task in the workflow is completed, writing the task record related to the task into the database.
For example, each step in the workflow is completed by writing into the database, and the execution condition of each task in the workflow is recorded by the database.
In some embodiments, the step S102 includes: and when the parallel tasks in the workflow are completed, writing the task records related to the parallel tasks into the database, and locking the task records of the parallel tasks by using the row lock of the database.
For example, because several subtasks of the parallel task are executed simultaneously, there may be a case where multiple subtasks complete simultaneously and need to be written to the database. In this case, the record may be locked using a row lock in the MySQL database. Therefore, the correct execution sequence of the parallel tasks is ensured, and other tasks are prevented from being read in a magic manner.
Step S103, in the task execution process, an exception handling mechanism is used for carrying out exception capture at the task execution place.
For example, the exception handling mechanism may be used to ensure that the parallel tasks are correctly handled when multiple exceptions are in succession. Because the tasks are executed asynchronously, exception capture is performed at the place where the tasks are executed, rather than using global exception capture, so exceptions are not missed.
In some embodiments, the exception handling mechanism employs the Try-Catch mechanism of JavaScript. JavaScript is a lightweight, interpreted, or just-in-time high-level programming language with function precedence. JavaScript has the characteristics of wide application range, easy learning and the like, and is very convenient for front-end developers to write back-end codes. The midboard system can be developed using node. Here, the exception may be captured using the Try-Catch mechanism of JavaScript.
In some embodiments, exceptions may also be trapped using the exception handling mechanism of TypeScript. The TypeScript is an enhanced version of JavaScript, and the language enhances a type system on the basis of the JavaScript, so that the error occurrence rate is reduced.
In some embodiments, the method further comprises: when the task is redone, reading the corresponding task into the memory again, and checking the completion condition of each subtask; if the subtask is in a completed state, skipping the subtask; if the subtask is in a failed state, stopping or skipping the subtask; if the subtask is in the executing state, the subtask is re-executed.
For example, task redo refers to a task that may continue to complete after a power outage. When the task is redone, the corresponding task stored in the database is read into the memory again, and whether the task is executed is determined according to the task number. The entire workflow is then re-executed.
In some embodiments, when a task is redone, the corresponding task is read into the memory again, and the completion condition of each subtask is checked; if the subtask is in a failed state, the subtask is stopped or skipped. Specifically, if a subtask of the parallel task is in a failure state, the subtask may be selected to be stopped or skipped according to whether the parallel task is error-sensitive or error-insensitive.
In some embodiments, the method further comprises: when the workflow rolls back, reading the corresponding task into the memory again, and checking the completion condition of each subtask; if the subtask is in a completed or executing state, the subtask performs a rollback; if the subtask is in a failed state, the subtask does not perform a rollback.
For example, task rollback refers to a task that may rollback a predecessor task after an error, and workflow rollback refers to a task in a workflow that may rollback a predecessor task after an error. When the workflow rolls back, the corresponding tasks stored in the database are read into the memory again, the completion condition of each subtask is checked, and then the subtask is determined to execute the roll back or not to execute the roll back according to the completion condition of each subtask.
Fig. 2 is a schematic diagram of an apparatus for implementing a workflow in a staging system according to an embodiment of the present application, where the apparatus includes an execution module 201, a recording module 202, and an exception handling module 203.
The execution module 201 reads a workflow from a database and executes tasks of the workflow, wherein the workflow includes a plurality of tasks.
For example, the database may be a MySQL database. Each workflow is a row of records in the database. Each time a task is to be performed, a workflow is read out of the database and execution begins.
In some embodiments, the tasks of the workflow are described in a structured language, which allows the structure of the entire task to be more clearly described.
An example of describing a task in a structured language is as follows:
in some embodiments, the type of task of the workflow comprises at least any one of: a parallel task, wherein a plurality of sub-tasks of the parallel task are executed simultaneously; a serial task, wherein a plurality of subtasks of the serial task are executed in sequence; a single task.
For example, several subtasks of the parallel task are executed simultaneously, and these subtasks are considered as a whole (the parallel task), which as a whole has an indication of success or failure of the execution of the task. Specifically, the parallel tasks may be further divided into two types, an error-sensitive parallel task and an error-insensitive parallel task. An error-sensitive parallel task, if one of the subtasks fails during execution, the entire parallel task fails. And if one subtask fails to execute the parallel task, the whole parallel task can still be successfully executed.
Several subtasks of the serial task are executed in sequence and these subtasks are treated as a whole (the serial task) and as a whole these subtasks are marked by success or failure of the task execution. The serial tasks are all error sensitive. When the serial task is executed, as long as one subtask has an error, the whole serial task fails.
The single task is simple, i.e. it is simply executed, and has a result of success or failure in execution. The single task is the most basic execution unit in the workflow.
The logging module 202 writes a task log for each task in the workflow into the database when the task is completed.
For example, each step in the workflow is completed by writing into the database, and the execution condition of each task in the workflow is recorded by the database.
In some embodiments, the recording module 202 writes a task record for the parallel task into the database when the parallel task in the workflow is completed, and locks the task record for the parallel task using a row lock of the database.
For example, because several subtasks of the parallel task are executed simultaneously, there may be a case where multiple subtasks complete simultaneously and need to be written to the database. In this case, the record may be locked using a row lock in the MySQL database. Therefore, the correct execution sequence of the parallel tasks is ensured, and other tasks are prevented from being read in a magic manner.
The exception handling module 203 performs exception capture at the task execution place by using an exception handling mechanism in the task execution process.
For example, the exception handling mechanism may be used to ensure that the parallel tasks are correctly handled when multiple exceptions are in succession. Because the tasks are executed asynchronously, exception capture is performed at the place where the tasks are executed, rather than using global exception capture, so exceptions are not missed.
In some embodiments, the exception handling mechanism employs the Try-Catch mechanism of JavaScript. JavaScript is a lightweight, interpreted, or just-in-time high-level programming language with function precedence. JavaScript has the characteristics of wide application range, easy learning and the like, and is very convenient for front-end developers to write back-end codes. The midboard system can be developed using node. Here, the exception may be captured using the Try-Catch mechanism of JavaScript.
In some embodiments, exceptions may also be trapped using the exception handling mechanism of TypeScript. The TypeScript is an enhanced version of JavaScript, and the language enhances a type system on the basis of the JavaScript, so that the error occurrence rate is reduced.
In some embodiments, the apparatus further comprises a task redo module 204; when the task is redone, the task redoing module 204 reads the corresponding task into the memory again, and checks the completion condition of each subtask; if the subtask is in a completed state, skipping the subtask; if the subtask is in a failed state, stopping or skipping the subtask; if the subtask is in the executing state, the subtask is re-executed.
For example, task redo refers to a task that may continue to complete after a power outage. When the task is redone, the corresponding task stored in the database is read into the memory again, and whether the task is executed is determined according to the task number. The entire workflow is then re-executed.
In some embodiments, when a task is redone, the corresponding task is read into the memory again, and the completion condition of each subtask is checked; if the subtask is in a failed state, the subtask is stopped or skipped. Specifically, if a subtask of the parallel task is in a failure state, the subtask may be selected to be stopped or skipped according to whether the parallel task is error-sensitive or error-insensitive.
In some embodiments, the apparatus further comprises a workflow rollback module 205; when the workflow rolls back, the workflow roll-back module 205 reads the corresponding task into the memory again, and checks the completion condition of each subtask; if the subtask is in a completed or executing state, the subtask performs a rollback; if the subtask is in a failed state, the subtask does not perform a rollback.
For example, task rollback refers to a task that may rollback a predecessor task after an error, and workflow rollback refers to a task in a workflow that may rollback a predecessor task after an error. When the workflow rolls back, the corresponding tasks stored in the database are read into the memory again, the completion condition of each subtask is checked, and then the subtask is determined to execute the roll back or not to execute the roll back according to the completion condition of each subtask.
To sum up, the embodiment of the application can enable the workflow of the middle platform system to meet the requirements of parallel task exception tolerance and multiple exception handling of the parallel task, and improves the stability of the middle platform system. Furthermore, the embodiment of the application can also enable the workflow of the middle platform system to meet the requirements of task rollback, task redoing and the like, so that the user experience is improved.
In addition, some of the present application may be implemented as a computer program product, such as computer program instructions, which when executed by a computer, may invoke or provide methods and/or techniques in accordance with the present application through the operation of the computer. Program instructions which invoke the methods of the present application may be stored on a fixed or removable recording medium and/or transmitted via a data stream on a broadcast or other signal-bearing medium and/or stored within a working memory of a computer device operating in accordance with the program instructions. Herein, some embodiments of the present application provide a computing device comprising a memory for storing computer program instructions and a processor for executing the computer program instructions, wherein the computer program instructions, when executed by the processor, trigger the device to perform the methods and/or aspects of the embodiments of the present application as described above.
Furthermore, some embodiments of the present application also provide a computer readable medium, on which computer program instructions are stored, the computer readable instructions being executable by a processor to implement the methods and/or aspects of the foregoing embodiments of the present application.
It should be noted that the present application may be implemented in software and/or a combination of software and hardware, for example, implemented using Application Specific Integrated Circuits (ASICs), general purpose computers or any other similar hardware devices. In some embodiments, the software programs of the present application may be executed by a processor to implement the steps or functions described above. Likewise, the software programs (including associated data structures) of the present application may be stored in a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. Additionally, some of the steps or functions of the present application may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various steps or functions.
It will be evident to those skilled in the art that the present application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is obvious that the word "comprising" does not exclude other elements or steps, and the singular does not exclude the plural. A plurality of units or means recited in the apparatus claims may also be implemented by one unit or means in software or hardware. The terms first, second, etc. are used to denote names, but not any particular order.
Claims (10)
1. A method of implementing a workflow in a staging system, wherein the method comprises:
reading a workflow from a database, and executing tasks of the workflow, wherein the workflow comprises a plurality of tasks;
when each task in the workflow is completed, writing a task record related to the task into the database;
and in the process of task execution, an exception handling mechanism is utilized to perform exception capture at the task execution place.
2. The method of claim 1, wherein the type of task of the workflow comprises at least any one of:
a parallel task, wherein a plurality of sub-tasks of the parallel task are executed simultaneously;
a serial task, wherein a plurality of subtasks of the serial task are executed in sequence;
a single task.
3. The method of claim 2, wherein writing a task record for each task in the workflow to the database upon completion of the task comprises:
and when the parallel tasks in the workflow are completed, writing the task records related to the parallel tasks into the database, and locking the task records of the parallel tasks by using the row lock of the database.
4. The method of claim 1, wherein the exception handling mechanism employs a Try-Catch mechanism of JavaScript.
5. The method of claim 1, wherein the method further comprises:
when the task is redone, reading the corresponding task into the memory again, and checking the completion condition of each subtask;
if the subtask is in a completed state, skipping the subtask;
if the subtask is in a failed state, stopping or skipping the subtask;
if the subtask is in the executing state, the subtask is re-executed.
6. The method of claim 1, wherein the method further comprises:
when the workflow rolls back, reading the corresponding task into the memory again, and checking the completion condition of each subtask;
if the subtask is in a completed or executing state, the subtask performs a rollback;
if the subtask is in a failed state, the subtask does not perform a rollback.
7. The method of any of claims 1-6, wherein tasks of the workflow are described in a structured language.
8. An apparatus for implementing a workflow in a staging system, wherein the apparatus comprises:
the execution module is used for reading a workflow from a database and executing tasks of the workflow, wherein the workflow comprises a plurality of tasks;
the recording module is used for writing the task record related to each task in the workflow into the database when the task is completed;
and the exception handling module is used for carrying out exception capture at the task execution place by utilizing an exception handling mechanism in the task execution process.
9. A computing device, wherein the device comprises a memory for storing computer program instructions and a processor for executing the computer program instructions, wherein the computer program instructions, when executed by the processor, trigger the device to perform the method of any of claims 1 to 7.
10. A computer readable medium having stored thereon computer program instructions executable by a processor to implement the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110309859.0A CN112965850A (en) | 2021-03-23 | 2021-03-23 | Method and equipment for realizing workflow in middle platform system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110309859.0A CN112965850A (en) | 2021-03-23 | 2021-03-23 | Method and equipment for realizing workflow in middle platform system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112965850A true CN112965850A (en) | 2021-06-15 |
Family
ID=76278252
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110309859.0A Pending CN112965850A (en) | 2021-03-23 | 2021-03-23 | Method and equipment for realizing workflow in middle platform system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112965850A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103019806A (en) * | 2011-09-22 | 2013-04-03 | 北京新媒传信科技有限公司 | Asynchronous task processing method and device |
| CN104317843A (en) * | 2014-10-11 | 2015-01-28 | 上海瀚之友信息技术服务有限公司 | Data synchronism ETL (Extract Transform Load) system |
| CN106611297A (en) * | 2015-10-21 | 2017-05-03 | 中兴通讯股份有限公司 | Workflow abnormity handling method and system |
| CN106790455A (en) * | 2016-12-08 | 2017-05-31 | 中国科学院软件研究所 | A kind of distributed cloud management system and method based on mixed mode |
| CN107528709A (en) * | 2016-06-22 | 2017-12-29 | 中兴通讯股份有限公司 | A kind of configuration status backing method and device |
| CN112527484A (en) * | 2020-12-17 | 2021-03-19 | 平安银行股份有限公司 | Workflow breakpoint continuous running method and device, computer equipment and readable storage medium |
-
2021
- 2021-03-23 CN CN202110309859.0A patent/CN112965850A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103019806A (en) * | 2011-09-22 | 2013-04-03 | 北京新媒传信科技有限公司 | Asynchronous task processing method and device |
| CN104317843A (en) * | 2014-10-11 | 2015-01-28 | 上海瀚之友信息技术服务有限公司 | Data synchronism ETL (Extract Transform Load) system |
| CN106611297A (en) * | 2015-10-21 | 2017-05-03 | 中兴通讯股份有限公司 | Workflow abnormity handling method and system |
| CN107528709A (en) * | 2016-06-22 | 2017-12-29 | 中兴通讯股份有限公司 | A kind of configuration status backing method and device |
| CN106790455A (en) * | 2016-12-08 | 2017-05-31 | 中国科学院软件研究所 | A kind of distributed cloud management system and method based on mixed mode |
| CN112527484A (en) * | 2020-12-17 | 2021-03-19 | 平安银行股份有限公司 | Workflow breakpoint continuous running method and device, computer equipment and readable storage medium |
Non-Patent Citations (5)
| Title |
|---|
| 员亚利等: "工作流事务原子性研究", 《计算机应用》 * |
| 张志君等: "工作流系统异常处理实现方法", 《高技术通讯》 * |
| 朱锦泉等: "基于事务的工作流异常处理模型及方法", 《吉林大学学报(工学版)》 * |
| 李明仑等: "《网络数据库设计与管理项目化教程》", 30 September 2015 * |
| 洪运国: "《SQL Server 2012数据库管理教程》", 31 December 2013 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11847029B1 (en) | Log-based rollback-recovery | |
| US11138031B2 (en) | Framework for authoring data loaders and data savers | |
| US8001091B2 (en) | Apparatus, system, and method for hierarchical rollback of business operations | |
| US9009708B2 (en) | Method and system to effectuate recovery for dynamic workflows | |
| BRPI0809078A2 (en) | TRANSACTIONAL MEMORY USING BUFFER STORAGE RECORDS AND ENHANCED SERIALIZATION ORDER | |
| US8145944B2 (en) | Business process error handling through process instance backup and recovery | |
| US8108627B2 (en) | Array comparison and swap operations | |
| JP4923142B2 (en) | Dealing with incorrect parent transaction failures | |
| WO2023160077A1 (en) | Blockchain data recovery method and apparatus, and electronic device | |
| US11099960B2 (en) | Dynamically adjusting statistics collection time in a database management system | |
| US8380941B2 (en) | Dynamic nest level determination for nested transactional memory rollback | |
| CN113360157A (en) | Program compiling method, device and computer readable medium | |
| CN114860654A (en) | Method and system for dynamically changing Iceberg table Schema based on Flink data stream | |
| US9965355B2 (en) | System and method for dynamic collection of system management data in a mainframe computing environment | |
| CN112965850A (en) | Method and equipment for realizing workflow in middle platform system | |
| US20140149697A1 (en) | Memory Pre-Allocation For Cleanup and Rollback Operations | |
| CN110188069B (en) | CSV file storage method and device and computer equipment | |
| CN112765129A (en) | Method and equipment for realizing database data version management | |
| CN112799951A (en) | Method and equipment for generating automatic test case for charging system | |
| CN112052290A (en) | Method and computer readable medium for distributed object warehousing, synchronous data warehousing | |
| CN109271277A (en) | Access method, device and system after database delay machine | |
| US20090276603A1 (en) | Techniques for efficient dataloads into partitioned tables | |
| Abbaspour Asadollah et al. | A model for systematic monitoring and debugging of starvation bugs in multicore software | |
| CN113392119A (en) | Data consistency processing method and equipment | |
| Airaksinen | The Effects of Testing in Software Development |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210615 |