CN117573396A - Distributed workflow event processing method, device and medium - Google Patents
Distributed workflow event processing method, device and medium Download PDFInfo
- Publication number
- CN117573396A CN117573396A CN202410051361.2A CN202410051361A CN117573396A CN 117573396 A CN117573396 A CN 117573396A CN 202410051361 A CN202410051361 A CN 202410051361A CN 117573396 A CN117573396 A CN 117573396A
- Authority
- CN
- China
- Prior art keywords
- event
- workflow
- preset
- business
- service
- 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.)
- Granted
Links
- 238000003672 processing method Methods 0.000 title abstract description 10
- 238000000034 method Methods 0.000 claims abstract description 31
- 238000012544 monitoring process Methods 0.000 claims abstract description 28
- 238000012545 processing Methods 0.000 claims abstract description 27
- 230000015654 memory Effects 0.000 claims description 9
- 230000006870 function Effects 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims 2
- 230000008569 process Effects 0.000 abstract description 11
- 230000003993 interaction Effects 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 5
- 230000001960 triggered effect Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000009969 flowable effect Effects 0.000 description 1
- 239000000178 monomer Substances 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The embodiment of the application discloses a distributed workflow event processing method, equipment and a medium. Belongs to the technical field of electric digital data processing, and solves the problem that data flow among different workflow nodes is difficult to carry out when a plurality of processes carry out data interaction. The service end stores the monitoring event to a first storage center and a second storage center of the middleware; the workflow end monitors based on a preset first storage center, acquires a business event object in the first storage center, stores the business event object into a preset event pool, and registers the business event object into a workflow engine; when the business event object is executed, triggering a workflow engine at a workflow end, and acquiring corresponding business event information from a preset event pool based on the workflow engine; the workflow end calls a preset interface corresponding to the business end based on the business event information, obtains an event execution result corresponding to the business event through the preset interface, and writes the event execution result into the workflow engine.
Description
Technical Field
The present disclosure relates to the field of digital data processing technologies, and in particular, to a method, an apparatus, and a medium for processing a distributed workflow event.
Background
In modern software systems, traditional backend services are monolithic services, with all business logic in the same engineering project. If the project engineering is simple, the single-body service is a good choice, but when the service becomes complex, the traditional single-body service has the problems of strong service coupling, poor maintainability, poor transverse expansion capability and the like.
In the prior art, services are typically split into micro services according to whether the services are the same or similar, and deployed in a distributed manner. In the prior art, the method of adding interception by the monomer type service is that the adding registration and interception execution of the event are completed in the same program process, which is equivalent to the action in the same program process, so that the adding interception is easier.
However, by adopting a distributed microservice mode, after the service end and the workflow end are split, event monitoring added by one application program needs to be synchronized into other application programs, and data communication interaction among a plurality of program processes is involved, so that data flow among different workflow nodes is difficult to realize.
Disclosure of Invention
The embodiment of the application provides a distributed workflow event processing method, equipment and medium, which are used for solving the following technical problems: the distributed microservice mode is adopted, and data communication interaction among a plurality of program processes is involved, so that data flow among different workflow nodes is difficult to realize.
The embodiment of the application adopts the following technical scheme:
the embodiment of the application provides a distributed workflow event processing method. The method comprises the steps that a service end stores monitoring events to a first storage center and a second storage center of a middleware; the workflow end monitors based on a preset first storage center, acquires a business event object in the first storage center, stores the business event object into a preset event pool, and registers the business event object into a workflow engine; when the business event object is executed, triggering a workflow engine at a workflow end, and acquiring corresponding business event information from a preset event pool based on the workflow engine; the workflow terminal calls a preset interface corresponding to the business terminal based on the business event information to acquire an event execution result corresponding to the business event object through the preset interface, and writes the event execution result into the workflow engine.
The embodiment of the application is based on the first storage center in the middleware and is used for registering the workflow business event of the business end to the workflow end, and the event can be re-registered after the workflow end is restarted. The second storage center is used for storing the event object of the service end, and after the service end is restarted, the event object is prevented from being lost. The callback of the business event from the workflow end to the business end is processed through the preset interface, the execution result of the event is obtained and written into the workflow engine, and the execution result of the business event can participate in the subsequent business processing logic of the business process, so that the data flow among the workflow nodes of each business system is realized.
In one implementation manner of the present application, a workflow terminal invokes a preset interface corresponding to a service terminal based on service event information, so as to obtain an event execution result corresponding to a service event object through the preset interface, which specifically includes: the workflow end calls a preset interface corresponding to the service end based on the service event information so as to send an event execution request to the service end; the service terminal obtains corresponding serialized event data from a second storage center based on the service event information, and deserializes the serialized event data into an event object to be executed; the business end executes the event object to be executed and sends the execution result to the workflow end.
In one implementation manner of the present application, the service end stores a listening event to a first storage center and a second storage center of the middleware, and specifically includes: the service end calls the application program interface function provided by the workflow end to acquire a monitoring event; the service end carries out serialization processing on the monitoring event and stores the serialized data into a first storage center; and the service end takes the name of the monitoring event as an identifier, and stores the identifier and the serialized data into a second storage center.
In one implementation of the present application, storing a business event object in a preset event pool, and registering the business event object in a workflow engine specifically includes: the workflow end determines the type of the business event object and acquires the type of a preset event pool; matching the type of the business event object with the type of the preset event pool to store the business event object in the preset event pool in a classified manner; the workflow end converts the business event object into an event object of a preset workflow engine, and registers the event object of the preset workflow engine into the workflow engine.
In one implementation manner of the present application, after the workflow end converts the service event object into the event object of the preset workflow engine, the method further includes: and the workflow end binds the business event object with the event object of the preset workflow engine.
In one implementation of the present application, before storing the snoop event to the first storage center and the second storage center of the middleware, the method further includes: and the service end registers a preset interface in a service center of the middleware.
In one implementation manner of the present application, the service end registers a preset interface in a service center of the middleware, and specifically includes: the service end obtains a preset interface registration file; the preset interface registration file comprises a JAR file sent by a workflow end, an ordered set of preset frames and preset dynamic configuration service; based on the preset interface registration file, the service end dynamically registers the preset interface in the service center of the middleware so as to monitor the event through the preset interface.
In one implementation manner of the present application, after the service end stores the listening event in the first storage center and the second storage center of the middleware, the method further includes: under the condition that the workflow end is restarted, automatically triggering a preset first storage center to monitor; and under the condition that the first storage center is determined to have a new monitoring event, acquiring the business event object in the first storage center through monitoring the preset first storage center.
The embodiment of the application provides distributed workflow event processing, which comprises the following steps: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executable by the at least one processor to enable the at least one processor to: the service end stores the monitoring event to a first storage center and a second storage center of the middleware; the workflow end monitors based on a preset first storage center, acquires a business event object in the first storage center, stores the business event object into a preset event pool, and registers the business event object into a workflow engine; when the business event object is executed, triggering a workflow engine at a workflow end, and acquiring corresponding business event information from a preset event pool based on the workflow engine; the workflow terminal calls a preset interface corresponding to the business terminal based on the business event information to acquire an event execution result corresponding to the business event object through the preset interface, and writes the event execution result into the workflow engine.
The embodiment of the application provides a nonvolatile computer storage medium, which stores computer executable instructions, wherein the computer executable instructions are configured to: the service end stores the monitoring event to a first storage center and a second storage center of the middleware; the workflow end monitors based on a preset first storage center, acquires a business event object in the first storage center, stores the business event object into a preset event pool, and registers the business event object into a workflow engine; when the business event object is executed, triggering a workflow engine at a workflow end, and acquiring corresponding business event information from a preset event pool based on the workflow engine; the workflow terminal calls a preset interface corresponding to the business terminal based on the business event information to acquire an event execution result corresponding to the business event object through the preset interface, and writes the event execution result into the workflow engine.
The above-mentioned at least one technical scheme that this application embodiment adopted can reach following beneficial effect: the embodiment of the application is based on the first storage center in the middleware and is used for registering the workflow business event of the business end to the workflow end, and the event can be re-registered after the workflow end is restarted. The second storage center is used for storing the event object of the service end, and after the service end is restarted, the event object is prevented from being lost. The callback of the business event from the workflow end to the business end is processed through the preset interface, the execution result of the event is obtained and written into the workflow engine, and the execution result of the business event can participate in the subsequent business processing logic of the business process, so that the data flow among the workflow nodes of each business system is realized.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and that other drawings may be obtained according to these drawings without inventive effort to a person skilled in the art. In the drawings:
FIG. 1 is a flowchart of a method for processing distributed workflow events according to an embodiment of the present application;
FIG. 2 is a block diagram of a distributed workflow event processing flow provided in an embodiment of the present application;
fig. 3 is a schematic structural diagram of a distributed workflow event processing device according to an embodiment of the present application.
Reference numerals:
200 distributed workflow event processing device, 201 processor, 202 memory.
Detailed Description
The embodiment of the application provides a distributed workflow event processing method, equipment and medium.
In order to better understand the technical solutions in the present application, the following description will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
The following describes in detail the technical solution proposed in the embodiments of the present application through the accompanying drawings.
Fig. 1 is a flowchart of a distributed workflow event processing method provided in an embodiment of the present application, where, as shown in fig. 1, the distributed workflow event processing method includes the following steps:
and step 101, the service end stores the monitoring event to a first storage center and a second storage center of the middleware.
In one embodiment of the present application, the distributed workflow event processing method provided in the embodiment of the present application is executed by a distributed workflow event processing system. The system comprises a service end, middleware and a workflow end.
Specifically, the service end and the workflow end are two systems independent from each other, and the workflow end is an abstract set of common services related to the workflow, for example: workflow diagram management, workflow engine related API (Application Programming Interface ) encapsulation, flow diagram related form management, and the like. A service end is a system for realizing actual service requirements, for example: leave examination and approval, reimbursement system, etc. The middleware is an open source component used for coordinating data interaction between the service end and the workflow end.
In one embodiment of the present application, the service end registers the preset interface in the service center of the middleware.
Specifically, a service end acquires a preset interface registration file; the preset interface registration file comprises a JAR file sent by a workflow end, an ordered set of preset frames and preset dynamic configuration service. Based on the preset interface registration file, the service end dynamically registers the preset interface in the service center of the middleware so as to monitor the event through the preset interface.
Further, the service end registers a REST (Representational State Transfer, a design and development manner for network applications) interface for performing interception with the service center, that is, the service end dynamically registers REST interfaces for performing events with the service center of the middleware based on a JAR package (a software package file format) provided by the workflow engine end, and a spring group (an ordered set of preset frameworks) and a jacos (preset dynamic configuration service).
In one embodiment of the present application, the service side invokes an application program interface function provided by the workflow side to obtain a listening event. The service end performs serialization processing on the monitoring event and stores the serialized data to the first storage center. And the service end takes the name of the monitoring event as an identifier, and stores the identifier and the serialized data into a second storage center.
Further, when the service end adds an event to a specified task or process, the monitoring event is serialized into storable data, and then the storable data is stored in a first storage center and a second storage center in the middleware, where the first storage center in the embodiment of the present application may be a zookeeper (a distributed, open source distributed application coordination service), and the second storage center may be a redis (memory database), or may be replaced by other storage media with similar characteristics. That is, the service side calls an API (Application Programming Interface ) function provided by the workflow side, adds a service event object to the first storage center, and stores the event object in the second storage center with the name of the event object as an identification.
Further, in the embodiment of the present application, the serialized data is stored in the first storage center, so as to coordinate the serialized event data between the service end and the workflow end, and stored in the second storage center, so that when the event is executed, the service end can obtain the corresponding serialized event data, and it is ensured that the event is not lost after the service end is restarted.
Further, in the embodiment of the present application, the serialized data is stored in the first storage center and the second storage center, so as to ensure that different service processes can acquire the serialized event data related to the event. Second, because the first storage center and the second storage center are two distributed components which are deployed independently, the first storage center and the second storage center also have the function similar to a database. After the first storage center and the second storage center start to store the data to the disk function, the serialized event data can be stored to the first storage center and the second storage center and can be stored on the disk, so long as the server disk is not damaged, the data cannot be lost, and even if the first storage center and the second storage center are restarted, the data can still be automatically restored to the process memories of the first storage center and the second storage center.
Step 102, the workflow terminal monitors based on a preset first storage center, acquires a business event object in the first storage center, stores the business event object in a preset event pool, and registers the business event object in a workflow engine.
In one embodiment of the present application, the workflow end determines the type of the business event object and obtains the type of the preset event pool. The type of the business event object is matched with the type of the preset event pool, so that the business event object classification is stored in the preset event pool. The workflow end converts the business event object into an event object of a preset workflow engine, and registers the event object of the preset workflow engine into the workflow engine.
In one embodiment of the present application, the workflow end binds the business event object with the event object of the preset workflow engine.
Specifically, the workflow end is provided with a preset first storage center monitoring function, and after the workflow end acquires the serial event data from the first storage center under the condition that the first storage center stores new data, the business event is added into a business event pool of the workflow end, and simultaneously, a corresponding flow (a business process management platform) workflow engine event is added, wherein the workflow event and the business event have a binding relationship.
Further, triggering a preset first storage center registered in advance by the workflow terminal to monitor, acquiring an event object from the first storage center, and storing the event object into an event pool in a classified manner according to the event type. And, the business event object is converted into the event object of the flow workflow engine, and the event object is registered in the workflow engine.
In one embodiment of the present application, in the case of a restart of the workflow end, a preset first storage center monitoring is automatically triggered. And under the condition that the first storage center is determined to have a new monitoring event, acquiring the business event object in the first storage center through monitoring the preset first storage center.
Specifically, after the workflow end is restarted, a preset first storage center which is registered in advance is automatically triggered to monitor, whether new data exist or not is determined, if the new data are monitored, event objects are obtained from the first storage center, and the event objects are stored in an event pool in a classified mode according to the event types. And, the business event object is converted into the event object of the flow workflow engine, and the event object is registered in the workflow engine.
And 103, triggering a workflow engine at a workflow end when the business event object is executed, and acquiring corresponding business event information from a preset event pool based on the workflow engine.
In one embodiment of the present application, events registered with the flowable workflow engine are triggered when a workflow or task corresponding to a business event is executed. Then, the corresponding business event is acquired from the event pool.
For example, a user approving the approval of a task to complete may trigger a task completion event, which is a workflow engine event. And acquiring a corresponding event in the service event pool from the workflow engine event, and remotely calling a service end REST event execution interface corresponding to the service event.
Step 104, the workflow terminal calls a preset interface corresponding to the business terminal based on the business event information to obtain an event execution result corresponding to the business event object through the preset interface, and writes the event execution result into the workflow engine.
In one embodiment of the application, the workflow terminal invokes a preset interface corresponding to the service terminal based on the service event information, so as to send an event execution request to the service terminal. The service terminal obtains corresponding serialized event data from the second storage center based on the service event information, and deserializes the serialized event data into an event object to be executed. The business end executes the event object to be executed and sends the execution result to the workflow end.
Specifically, the workflow end remotely invokes a service end REST event execution interface corresponding to the service event based on the service event information. After receiving the event execution request, the service end acquires corresponding serialized event data from the second storage center, inversely serializes the event data into an event object, executes the event object, and returns an execution result to a calling end (namely a workflow end) of the REST interface after the event execution is completed; to this end, the distributed event execution is complete.
Further, the REST of the service end acquires the service event from the second storage center according to the identification of the service event, and deserializes the service event into an executable java object. And executing the business event object and returning an execution result. The workflow engine side acquires the result returned by the REST interface and writes the result into the workflow engine.
Fig. 2 is a flowchart of a distributed workflow event processing, where, as shown in fig. 2, a distributed workflow event processing method is executed by a distributed workflow event processing system according to an embodiment of the present application. The system comprises a service system (distributed subsystem), namely a service end, middleware and a workflow end (approval center). The service end registers a preset interface in a service center of the middleware. The service end calls the application program interface function provided by the workflow end to acquire a monitoring event. The service end performs serialization processing on the monitoring events, and stores the serialized data to a first storage center (distributed coordination middleware) and a second storage center (distributed memory bank). The workflow end monitors based on a preset first storage center, acquires a business event object in the first storage center, stores the business event object in a preset event pool, and registers the business event object in a workflow engine. When the workflow or task corresponding to the business event is executed, the event registered to the flow workflow engine is triggered. Then, the corresponding business event is acquired from the event pool. The workflow terminal calls a preset interface corresponding to the business terminal based on the business event information so as to send an event execution request to the business terminal. The service terminal obtains corresponding serialized event data from the second storage center based on the service event information, and deserializes the serialized event data into an event object to be executed. The business end executes the event object to be executed and sends the execution result to the workflow end. The workflow engine side obtains the result value returned by the service port and writes the result value into the workflow engine.
Fig. 3 is a schematic structural diagram of a distributed workflow event processing device according to an embodiment of the present application. As shown in fig. 3, the distributed workflow event processing apparatus 200 includes: at least one processor 201; and a memory 202 communicatively coupled to the at least one processor 201; wherein the memory 202 stores instructions executable by the at least one processor 201, the instructions being executable by the at least one processor 201 to enable the at least one processor 201 to: the service end stores the monitoring event to a first storage center and a second storage center of the middleware; the workflow end monitors based on a preset first storage center, acquires a business event object in the first storage center, stores the business event object into a preset event pool, and registers the business event object into a workflow engine; when the business event object is executed, triggering a workflow engine at a workflow end, and acquiring corresponding business event information from a preset event pool based on the workflow engine; the workflow terminal calls a preset interface corresponding to the business terminal based on the business event information to acquire an event execution result corresponding to the business event object through the preset interface, and writes the event execution result into the workflow engine.
The embodiments also provide a non-volatile computer storage medium storing computer executable instructions configured to: the service end stores the monitoring event to a first storage center and a second storage center of the middleware; the workflow end monitors based on a preset first storage center, acquires a business event object in the first storage center, stores the business event object into a preset event pool, and registers the business event object into a workflow engine; when the business event object is executed, triggering a workflow engine at a workflow end, and acquiring corresponding business event information from a preset event pool based on the workflow engine; the workflow terminal calls a preset interface corresponding to the business terminal based on the business event information to acquire an event execution result corresponding to the business event object through the preset interface, and writes the event execution result into the workflow engine.
All embodiments in the application are described in a progressive manner, and identical and similar parts of all embodiments are mutually referred, so that each embodiment mainly describes differences from other embodiments. In particular, for apparatus, devices, non-volatile computer storage medium embodiments, the description is relatively simple, as it is substantially similar to method embodiments, with reference to the section of the method embodiments being relevant.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the embodiments of the present application will be apparent to those skilled in the art. Such modifications and substitutions do not depart from the spirit and scope of the corresponding technical solutions.
Claims (10)
1. A method for processing a distributed workflow event, the method being performed by a distributed workflow event processing system, the distributed workflow event processing system comprising a service end, middleware, and a workflow end, the method comprising:
the service end stores the monitoring event to a first storage center and a second storage center of the middleware;
the workflow terminal monitors based on a preset first storage center, acquires a business event object from the first storage center, stores the business event object into a preset event pool, and registers the business event object into a workflow engine;
when the business event object is executed, triggering a workflow engine of the workflow end, and acquiring corresponding business event information from the preset event pool based on the workflow engine;
and the workflow end calls a preset interface corresponding to the business end based on the business event information so as to acquire an event execution result corresponding to the business event object through the preset interface, and writes the event execution result into the workflow engine.
2. The method for processing distributed workflow events according to claim 1, wherein the workflow terminal invokes a preset interface corresponding to the service terminal based on the service event information, so as to obtain an event execution result corresponding to the service event object through the preset interface, specifically including:
the workflow terminal calls a preset interface corresponding to the service terminal based on the service event information so as to send an event execution request to the service terminal;
the service end obtains corresponding serialized event data from the second storage center based on the service event information, and deserializes the serialized event data into an event object to be executed;
the service end executes the event object to be executed and sends an execution result to the workflow end.
3. The method for processing distributed workflow events according to claim 1, wherein the service end stores a listening event in a first storage center and a second storage center of the middleware, specifically comprising:
the service end calls an application program interface function provided by the workflow end to acquire the monitoring event;
the service end carries out serialization processing on the monitoring event and stores the serialized data to the first storage center;
and the service end takes the name of the monitoring event as an identifier, and stores the identifier and the serialized data into the second storage center.
4. The method for processing distributed workflow events according to claim 1, wherein the storing the business event object in a preset event pool and registering the business event object in a workflow engine specifically comprises:
the workflow end determines the type of the business event object and acquires the type of the preset event pool;
matching the type of the business event object with the type of the preset event pool so as to store the business event object in the preset event pool in a classified manner;
the workflow end converts the business event object into an event object of a preset workflow engine, and registers the event object of the preset workflow engine into the workflow engine.
5. The method of claim 4, wherein after the workflow end converts the business event object into an event object of a preset workflow engine, the method further comprises:
and the workflow end binds the business event object with the event object of the preset workflow engine.
6. The method according to claim 1, wherein before the service end stores the listening event in the first storage center and the second storage center of the middleware, the method further comprises:
and the service end registers the preset interface in a service center of the middleware.
7. The method for processing distributed workflow events according to claim 6, wherein the registering the preset interface by the service end in the service center of the middleware specifically comprises:
the service end obtains a preset interface registration file; the preset interface registration file comprises a JAR file sent by the workflow end, an ordered set of preset frames and preset dynamic configuration service;
and based on the preset interface registration file, the service end dynamically registers the preset interface in a service center of the middleware so as to monitor events through the preset interface.
8. The method according to claim 1, wherein after the service end stores the listening event in the first storage center and the second storage center of the middleware, the method further comprises:
under the condition that the workflow end is restarted, automatically triggering the preset first storage center to monitor;
and under the condition that the first storage center is determined to have a new monitoring event, monitoring the first storage center through the preset first storage center to acquire a business event object.
9. A distributed workflow event processing device comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions, when executed by the processor, trigger the device to perform the method of any of claims 1-8.
10. A non-transitory computer storage medium storing computer executable instructions, wherein the computer executable instructions are capable of performing the method of any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410051361.2A CN117573396B (en) | 2024-01-15 | 2024-01-15 | Distributed workflow event processing method, device and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410051361.2A CN117573396B (en) | 2024-01-15 | 2024-01-15 | Distributed workflow event processing method, device and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117573396A true CN117573396A (en) | 2024-02-20 |
| CN117573396B CN117573396B (en) | 2024-03-29 |
Family
ID=89890382
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410051361.2A Active CN117573396B (en) | 2024-01-15 | 2024-01-15 | Distributed workflow event processing method, device and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117573396B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107682206A (en) * | 2017-11-02 | 2018-02-09 | 北京中电普华信息技术有限公司 | The dispositions method and system of business process management system based on micro services |
| CN109739447A (en) * | 2018-12-19 | 2019-05-10 | 深圳怡化电脑股份有限公司 | Middleware and its communication means, middleware layer, storage medium and terminal device |
| CN110532025A (en) * | 2019-08-30 | 2019-12-03 | 上海复深蓝软件股份有限公司 | Data processing method, device, equipment and storage medium based on micro services framework |
| CN110955534A (en) * | 2019-10-10 | 2020-04-03 | 荣邦科技有限公司 | Middleware-based business process automation system and method |
| CN113268319A (en) * | 2021-05-07 | 2021-08-17 | 中国电子科技集团公司第五十四研究所 | Business process customization and distributed process scheduling method based on micro-service architecture |
| CN114661433A (en) * | 2020-12-24 | 2022-06-24 | 北京金山云网络技术有限公司 | Event task scheduling method and device, storage medium and electronic equipment |
| DE102021124688A1 (en) * | 2021-09-25 | 2023-03-23 | Intel Corporation | ALLOW AUTOMATIC SCALE OF COMPUTING POWER BETWEEN DEVICE AND NETWORK WITH DYNAMIC RESOURCE AVAILABILITY |
-
2024
- 2024-01-15 CN CN202410051361.2A patent/CN117573396B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107682206A (en) * | 2017-11-02 | 2018-02-09 | 北京中电普华信息技术有限公司 | The dispositions method and system of business process management system based on micro services |
| CN109739447A (en) * | 2018-12-19 | 2019-05-10 | 深圳怡化电脑股份有限公司 | Middleware and its communication means, middleware layer, storage medium and terminal device |
| CN110532025A (en) * | 2019-08-30 | 2019-12-03 | 上海复深蓝软件股份有限公司 | Data processing method, device, equipment and storage medium based on micro services framework |
| CN110955534A (en) * | 2019-10-10 | 2020-04-03 | 荣邦科技有限公司 | Middleware-based business process automation system and method |
| CN114661433A (en) * | 2020-12-24 | 2022-06-24 | 北京金山云网络技术有限公司 | Event task scheduling method and device, storage medium and electronic equipment |
| CN113268319A (en) * | 2021-05-07 | 2021-08-17 | 中国电子科技集团公司第五十四研究所 | Business process customization and distributed process scheduling method based on micro-service architecture |
| DE102021124688A1 (en) * | 2021-09-25 | 2023-03-23 | Intel Corporation | ALLOW AUTOMATIC SCALE OF COMPUTING POWER BETWEEN DEVICE AND NETWORK WITH DYNAMIC RESOURCE AVAILABILITY |
Non-Patent Citations (2)
| Title |
|---|
| ALAASAM, AMEER B. A.: "Analytic Study of Containerizing Stateful Stream Processing as Microservice to Support Digital Twins in Fog Computing", PROGRAMMING AND COMPUTER SOFTWARE VOLUME46 ISSUE8, 31 December 2020 (2020-12-31), pages 511 - 525 * |
| 邹晶;刘毅敏;: "基于有限状态机的工作流引擎的设计", 计算机应用与软件, no. 08, 12 August 2018 (2018-08-12), pages 66 - 71 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117573396B (en) | 2024-03-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111930529B (en) | Data synchronization method, device and system based on message queue and microservice | |
| CN110399241B (en) | Task exception handling method, device, computer equipment and readable storage medium | |
| CN107241315B (en) | Access method and device of bank gateway interface and computer readable storage medium | |
| CN110888893A (en) | Order processing method based on micro-service e-commerce system | |
| CN110471746B (en) | Distributed transaction callback method, device and system | |
| CN111277639B (en) | Method and device for maintaining data consistency | |
| CN112738060B (en) | Method and device for processing micro-service data, micro-service processing platform and medium | |
| CN111200606A (en) | Deep learning model task processing method, system, server and storage medium | |
| CN108880873B (en) | Transaction compensation method and device applied to heterogeneous system | |
| CN117573396B (en) | Distributed workflow event processing method, device and medium | |
| CN111159298B (en) | Service request processing method and device, electronic equipment and storage medium | |
| CN111143040A (en) | Transaction processing method, device, system and storage medium | |
| CN110609707B (en) | Online data processing system generation method, device and equipment | |
| CN111274047A (en) | Information processing method, terminal, system, computer device and storage medium | |
| CN111625323A (en) | Distributed task processing method, device, equipment and computer readable storage medium | |
| CN112711466B (en) | Hanging affair inspection method and device, electronic equipment and storage medium | |
| CN114610413A (en) | Method, device, equipment and storage medium for executing synchronous and asynchronous tasks based on Java | |
| CN113360386A (en) | Switching chip drive test method, device, electronic equipment and storage medium | |
| CN112948195A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN112818336A (en) | Data access method, data access device and computer readable storage medium | |
| CN111309500A (en) | Service processing method, device, equipment and storage medium | |
| CN112835728B (en) | Message processing method, device, computer equipment and storage medium | |
| CN116010126B (en) | Service aggregation method, device and system | |
| CN115174440B (en) | Connectivity detection method, device, storage medium and equipment | |
| CN112019452B (en) | Method, system and related device for processing service requirement |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |