A process business processing method and device for a distributed process engine

Abstract

The present invention relates to the technical field of process business processing, and discloses a process business processing method and device of a distributed process engine. The present invention obtains a process instance request packet sent by a first user end to request a target process business, and the process instance request packet is loaded with an instance identifier and a request instruction; based on the request instruction, the target process business is locked through a first execution script; if the request resource corresponding to the instance identifier is queried from the target resource library, the target process business is executed according to the request resource; if the request resource corresponding to the instance identifier is not queried from the target resource library, an access failure instruction of the target process business is returned to the first user end. The present invention locks the target process business through the first execution script to prevent the background server from repeating operation actions when different users send multiple process instance requests to the background server in succession, that is, operation conflicts occur, resulting in the background server being unable to perform actions normally according to the pre-set unified command.

Description

Technical Field

[0001] The present invention relates to the technical field of process business processing, and in particular to a process business processing method and device of a distributed process engine. Background Art

[0002] A distributed process engine refers to a group of workflow engines distributed on different nodes that work together to complete the execution of the entire workflow instance. To ensure the efficient execution of business processes in the business system, each workflow engine is responsible for completing the execution of a portion of the activity instances, and different workflow engines collaborate through a reliable communication mechanism. This allows information storage, permissions, approvals, message notifications, etc. in the business process to flow according to certain process rules, thus achieving full or partial automation of the business process.

[0003] In the distributed process engine of the related technology, when different users operate the process business of the same node at the same time, since some users operate quickly and some users operate slowly, the server responds one after another, resulting in the process business of the same node being unable to execute actions normally according to the pre-set unified command due to repeated execution of actions. Summary of the invention

[0004] In view of this, the present invention provides a process business processing method and device of a distributed process engine to solve the problem that the process business of the same node cannot normally execute actions according to a preset unified command due to repeated execution of actions.

[0005] In a first aspect, the present invention provides a process business processing method and device of a distributed process engine, the method comprising:

[0006] Obtaining a process instance request packet sent by the first user end to request a target process service, wherein the process instance request packet is loaded with an instance identifier and a request instruction;

[0007] Based on the request instruction, the target process business is locked through the first execution script;

[0008] If the requested resource corresponding to the instance ID is found from the target resource library, the target process business is executed according to the requested resource;

[0009] If the requested resource corresponding to the instance identifier is not found in the target resource library, an access failure instruction of the target process service is returned to the first user terminal.

[0010] The disclosed embodiment locks the target process business through the first execution script to prevent the background server from performing repeated operations when different users send multiple process instance requests to the background server in succession, that is, operation conflicts occur, resulting in the background server being unable to execute actions normally according to the pre-set unified command.

[0011] In some optional implementations, the process business processing method of the distributed process engine in the embodiment of the present disclosure further includes:

[0012] After the execution of the target flow service according to the requested resources is completed, the target flow service is unlocked by a second execution script to wait for the second user end to access the flow target flow service.

[0013] In some optional implementations, the process business processing method of the distributed process engine in the embodiment of the present disclosure further includes:

[0014] When multiple users simultaneously send process instance request packages requesting the target process business, obtain the current memory usage resources;

[0015] Based on the current memory usage resources, configure the target cache container with preset storage capacity;

[0016] Cache process instance request packages of multiple users through the target cache container.

[0017] In the embodiment of the present disclosure, when a batch of users simultaneously send requests to access the target process business of the same node, the memory of the background server suddenly increases. In order to reduce the data processing pressure of the background server, a target cache container with a preset storage capacity is configured to cache the batch of process instance data, thereby preventing data loss.

[0018] In some optional implementations, the process business processing method of the distributed process engine in the embodiment of the present disclosure further includes:

[0019] Configure the number of core threads and the maximum number of threads;

[0020] Based on the number of core threads and the maximum number of threads, load the process instance request packages sent by multiple users simultaneously to request the target process business;

[0021] The loaded process instance request packages sent by multiple users at the same time to request the target process business are injected into the target cache container.

[0022] The disclosed embodiment configures the number of core threads and the maximum number of threads to load process instance request packets sent by multiple users simultaneously to request target process services, which is beneficial to improving data processing speed.

[0023] In some optional implementations, the process business processing method of the distributed process engine in the embodiment of the present disclosure further includes: after executing the target process business according to the requested resources, using a distributed cache to cache the action execution data of the target process business and returning an access success instruction to the first user end.

[0024] After executing the target process service according to the requested resources, the embodiment of the present disclosure returns a success instruction to the first user terminal in order to prompt the first user terminal to allow it to operate the target process service normally.

[0025] In some optional implementations, in the process business processing method of the distributed process engine in the embodiments of the present disclosure, the distributed process engine is a Flowable process engine.

[0026] In a second aspect, the present invention provides a process business processing device of a distributed process engine, the device comprising:

[0027] An instance acquisition module, used to acquire a process instance request packet sent by a first user end to request a target process service, wherein the process instance request packet is loaded with an instance identifier and a request instruction;

[0028] An instance locking module, used to lock the target process business through the first execution script based on the request instruction;

[0029] An instance execution module is used to execute the target process business according to the requested resources if the requested resources corresponding to the instance identifier are queried from the target resource library;

[0030] The instance returning module is used to return an access denial instruction of the target process service to the first user terminal if the requested resource corresponding to the instance identifier is not found in the target resource library.

[0031] In a third aspect, the present invention provides a computer device comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the process business processing method of the distributed process engine of the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0032] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the process business processing method of a distributed process engine of the above-mentioned first aspect or any corresponding embodiment thereof.

[0033] In a fifth aspect, the present invention provides a computer program product, comprising computer instructions for causing a computer to execute the virus detection method of the first aspect or any corresponding embodiment thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0035] Figure 1 is a schematic diagram of the structure of a distributed process engine according to an embodiment of the present invention;

[0036] Figure 2 is a flowchart of a process business processing method of a distributed process engine according to an embodiment of the present invention;

[0037] Figure 3 is an interactive schematic diagram of a process business processing method of a distributed process engine according to an embodiment of the present invention;

[0038] Figure 4 is a schematic diagram of CPU usage comparison before and after memory optimization according to an embodiment of the present invention;

[0039] Figure 5 is a schematic diagram of memory usage before optimization according to an embodiment of the present invention;

[0040] Figure 6 It is a structural block diagram of a process business processing device of a distributed process engine according to an embodiment of the present invention;

[0041] Figure 7 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0043] According to an embodiment of the present invention, a process business processing method embodiment of a distributed process engine is provided, which is applied to a distributed process engine, and the distributed process engine is a high-concurrency Flowable engine. Flowable is a lightweight business process engine written in Java. The Flowable process engine can be used to deploy BPMN 2.0 process definitions (an industry XML standard for defining processes), create process instances of these process definitions, perform queries, and access running or historical process instances and related data. Figure 1 As shown in the figure, the distributed process engine includes five core components: Business Process Engine (BPMN, Business Process Model and Notation), Form Engine (Form Engine), Case Model Engine (CMMN, (Case Management Model and Notation), Decision Engine (DMN, (Decision Model and Notation), Content Engines. Figure 1 It also includes: Modeler, Task, Internet Download Manager (IDM), Admin, administration, Representational State Transfer-Application Programming Interface (REST API), Engine Specific Services, Job Service, Task Service, Identity Service, Variable Service, Entity managers and Data managers, and MyBatis Persistence Service. Flowable can be embedded in Java applications, run as a server or cluster, and can also provide cloud services.

[0044] According to an embodiment of the present invention, an embodiment of a process business processing method of a distributed process engine is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0045] In this embodiment, a process business processing method of a distributed process engine is provided, which can be used in a backend server, a mobile terminal, such as a mobile phone, a tablet computer, etc. Figure 2 is a flowchart of a process business processing method of a distributed process engine according to an embodiment of the present invention. Figure 2 As shown, the process includes the following steps:

[0046] Step S201: obtaining a process instance request packet sent by a first user end to request a target process service, wherein the process instance request packet is loaded with an instance identifier and a request instruction.

[0047] Specifically, for example, in the scenario of the Double Eleven flash sale order business, there is only one target product A. At this time, customer A and customer B place orders to purchase target product A at the same time. The purchasing platform needs to query the inventory first based on the order instructions of customer A and customer B, then determine whether there is any remaining inventory, then create an order, then reduce the inventory, and finally indicate that the purchase is successful. The first user terminal sends a process instance request package to the backend server for the order business (target process business) requesting the purchase of the target product. The process instance request package records the order product identifier and the purchase request instruction for the purchase of the order product. The first user terminal is the first user terminal to send a request to the backend server.

[0048] Furthermore, during the actual generation of the process instance, the process instance identification id uses the snowflake id generator to generate a globally unique id to ensure the uniqueness of the primary key.

[0049] Step S202: Based on the request instruction, the target process business is locked by a first execution script.

[0050] Specifically, the first execution script is the execution code corresponding to the distributed lock (Redisson lock). During the process operation, the distributed lock is added to ensure that only the single instance requested by the first user terminal is allowed to run. The first execution script is as follows.

[0051] redissonClient.getLock(PROCESSHANDLE_REDISSON_KEY);

[0052] boolean locked=lock.tryLock();

[0053] if(locked){

[0054] try{

[0055] / / TODO

[0056] }catch(Exception e){

[0057] LOGGER.error("commit error"+e.getMessage());

[0058] }finally{

[0059] if(lock.isLocked()){

[0060] if(lock.isHeldByCurrentThread()){

[0061] lock.unlock();

[0062] }

[0063] }

[0064] }

[0065] }else{

[0066] LOGGER.info("redissonClient.getLock()is false");

[0067] }

[0068] For example, in the scenario of the Double Eleven flash sale order business for rush-buying goods in the above example, the normal rush-buying business is that the person who places the order first will be able to rush-buy the only target product A in the inventory first. In the traditional way, in the rush-buying order business, since no distributed lock is set, if the first user terminal and the second user terminal submit order requests at the same time, the first user terminal and the second user terminal will both execute to the same node. The background server believes that there is still inventory that needs to be executed, resulting in the first user terminal and the second user terminal both succeeding in the rush-buying, resulting in overselling. Ultimately, the background server cannot execute the rush-buying action according to the pre-set unified rush-buy one rush-buying product instruction.

[0069] However, the disclosed embodiment locks the target process business through the first execution script based on the request instruction. When the first user terminal places an order to snap up the target product A before the second user terminal, the target process business (target product A order business) is locked through the first execution script. Even when the second user terminal executes to the same node as A, it cannot snap up the target product A. Finally, the backend server can execute the snap-up action according to the pre-set unified snap-up product instruction, ensuring first come first served and no overselling.

[0070] Step S203: If the requested resource corresponding to the instance identifier is found from the target resource library, the target process business is executed according to the requested resource.

[0071] Step S204: if the requested resource corresponding to the instance identifier is not found in the target resource library, an access failure instruction of the target process service is returned to the first user terminal.

[0072] Specifically, a distributed lock Redisson lock is used to obtain lock resources (request resources) with the instance identifier id as the key. If the lock resource is obtained, the asynchronous thread flow process is started. If the lock resource cannot be obtained, the execution is directly rejected and an access failure instruction is returned.

[0073] Therefore, the target process business is locked by the first execution script to prevent repeated operations on the background server when different users send multiple process instance requests to the background server in succession, that is, operation conflicts occur, resulting in the background server being unable to execute actions normally according to the pre-set unified command.

[0074] In some optional implementations, the process business processing method of the distributed process engine in the embodiment of the present disclosure also includes: after the execution of the target process business according to the requested resources is completed, unlocking the target process business through a second execution script to wait for the second user terminal to access the flow target process business.

[0075] The disclosed embodiment unlocks the target process business through a second execution script. In order to ensure that the second user terminal accessing the same node as the first user terminal can execute the target process business normally after the first user terminal completes the execution of the target process business, it is avoided that different users request the same process instance one after another, causing execution data conflicts, thereby ensuring the orderly progress of the process business.

[0076] like Figure 3 , which is a distributed lock timing diagram in an embodiment of the present disclosure.

[0077] In some optional implementations, the process business processing method of the distributed process engine in the embodiment of the present disclosure further includes:

[0078] Step a1, when multiple users simultaneously send process instance request packets requesting the target process business, obtain the current memory usage resources.

[0079] Step a2: Based on the current memory usage resources, configure a target cache container with a preset storage capacity.

[0080] Step a3: caching the process instance request packages of multiple users through the target cache container.

[0081] Specifically, the backpressure strategy is used to configure memory parameters and optimize memory performance. The backpressure strategy is that when the data speed sent by the upstream exceeds the processing capacity of the downstream, a MissingBackpressureException will be thrown. The buffer strategy is set to ensure that data is not lost. The distributed process engine sets the thread scheduler in advance and executes the above steps a1-a3. The thread scheduler is shown in the following code example.

[0082] Flowable.range(1,1000)

[0083] .onBackpressureBuffer()

[0084] .observeOn(Schedulers.computation())

[0085] .subscribe(System.out::println)

[0086] Therefore, when a batch of users simultaneously send requests to access the target process business of the same node, the memory of the background server suddenly increases. In order to reduce the data processing pressure of the background server, a target cache container with a preset storage capacity is configured to cache the batch of process instance data, thereby preventing data loss.

[0087] like Figure 4 As shown in the figure, the target cache container caches the process instance request packets of multiple users, and the CPU usage comparison diagram before and after memory optimization. Figure 5 As shown in the figure, it is a schematic diagram of memory usage before optimization. Figure 6 The figure below is a schematic diagram of memory usage after optimization.

[0088] The embodiment of the present disclosure introduces distributed locks and optimized cache and configuration to improve the performance of the process engine and solve the high concurrency problem. In terms of system load, after the optimization measures of the embodiment of the present disclosure, the load of the number of connections to the persistence layer of a single instance is reduced by 45%, while supporting multi-instance distributed deployment. In terms of application execution time, after the optimization measures of the present invention, the CPU and memory usage of a single instance of the application is reduced by 50%.

[0089] In some optional implementations, the process business processing method of the distributed process engine in the embodiment of the present disclosure further includes:

[0090] Step b1: configure the number of core threads and the maximum number of threads.

[0091] Step b2: Based on the number of core threads and the maximum number of threads, process instance request packets simultaneously sent by multiple users to request the target process business are loaded.

[0092] Step b3, injecting the loaded process instance request packets sent by multiple users simultaneously to request the target process business into the target cache container.

[0093] Specifically, the thread pool strategy is the upstream producer and downstream consumer thread pool. By default, Flowable uses the Schedulers.computation() scheduler, which uses a fixed-size thread pool, the size of which is the number of CPU cores. This thread pool is suitable for computationally intensive operations. Reset the custom thread pool to allocate server resources. Use the following code to set the thread scheduler for the distributed process engine to execute the above steps b1-b3 to improve data processing speed.

[0094] In some optional implementations, the process business processing method of the distributed process engine in the embodiment of the present disclosure further includes: after executing the target process business according to the requested resources, using a distributed cache to cache the action execution data of the target process business and returning an access success instruction to the first user end.

[0095] Specifically, for example, the code data corresponding to the above steps S201-step S204 are uniformly cached in the distributed cache DeploymentCache through the distributed cache interface DeploymentCache to improve the consistency of the data cache, and cache the action data of each node of the target process business to avoid re-querying by users who perform the same action after data loss, thereby improving data processing performance.

[0096] After executing the target process service according to the requested resources, a success instruction is returned to the first user terminal to prompt the first user terminal to allow it to operate the target process service normally.

[0097] In this embodiment, a process business processing device of a distributed process engine is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0098] This embodiment provides a process business processing device of a distributed process engine, such as Figure 6 As shown, including:

[0099] An instance acquisition module 61 is used to acquire a process instance request packet sent by a first user end to request a target process service, wherein the process instance request packet is loaded with an instance identifier and a request instruction;

[0100] An instance locking module 62, configured to lock a target process service through a first execution script based on a request instruction;

[0101] An instance execution module 63 is used to execute a target process business according to the requested resource if a requested resource corresponding to the instance identifier is found from the target resource library;

[0102] The instance returning module 64 is used to return an access denial instruction of the target process service to the first user terminal if the requested resource corresponding to the instance identifier is not found from the target resource library.

[0103] In some optional implementations, the process business processing device of the distributed process engine in the embodiment of the present disclosure further includes:

[0104] The unlocking module is used to unlock the target process service through a second execution script after the target process service is executed according to the requested resources, so as to wait for the second user end to access the flow target process service.

[0105] In some optional implementations, the process business processing device of the distributed process engine in the embodiment of the present disclosure further includes:

[0106] The resource acquisition module is used to obtain the current memory usage resources when multiple users simultaneously send process instance request packets requesting the target process business;

[0107] A memory configuration module, used to configure a target cache container with a preset storage capacity based on current memory usage resources;

[0108] The data cache module is used to cache the process instance request packages of multiple users through the target cache container.

[0109] In some optional implementations, the process business processing device of the distributed process engine in the embodiment of the present disclosure further includes:

[0110] Thread configuration module, used to configure the number of core threads and the maximum number of threads;

[0111] The data loading module is used to load the process instance request packages sent by multiple users simultaneously to request the target process business based on the number of core threads and the maximum number of threads;

[0112] The data injection module is used to inject the loaded process instance request packets sent by multiple users simultaneously to request the target process business into the target cache container.

[0113] In some optional embodiments, the process business processing device of the distributed process engine in the embodiment of the present disclosure also includes: a data cache module, which is used to use a distributed cache to cache the action execution data of the target process business after executing the target process business according to the requested resources and return an access success instruction to the first user end.

[0114] In some optional implementations, the process business processing device of the distributed process engine in the embodiment of the present disclosure, the distributed process engine is a Flowable process engine.

[0115] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0116] The process business processing device of the distributed process engine in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0117] An embodiment of the present invention further provides a computer device having the process business processing device of the above-mentioned distributed process engine.

[0118] See also Figure 7 , Figure 7 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 7 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 7 A processor 10 is taken as an example.

[0119] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0120] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0121] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0122] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0123] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0124] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0125] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0126] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A process business processing method of a distributed process engine, characterized in that: The method comprises: Acquire a process instance request packet sent by a first user end to request a target process service, wherein the process instance request packet is loaded with an instance identifier and a request instruction; Based on the request instruction, locking the target process business through a first execution script; If a request resource corresponding to the instance identifier is found from the target resource library, the target process business is executed according to the request resource; If the requested resource corresponding to the instance identifier is not found in the target resource library, an access failure instruction of the target process service is returned to the first user terminal.

2. The method according to claim 1, characterized in that: Also includes: After the target process service is executed according to the requested resource, the target process service is unlocked by a second execution script to wait for a second user terminal to access the target process service.

3. The method according to claim 1, characterized in that: Also includes: When multiple users simultaneously send process instance request packages requesting the target process business, obtain the current memory usage resources; Based on the current memory usage resources, configure a target cache container with a preset storage capacity; The process instance request packages of multiple users are cached by the target cache container.

4. The method according to claim 3, characterized in that Also includes: Configure the number of core threads and the maximum number of threads; Based on the core thread number and the maximum thread number, loading the process instance request packets simultaneously sent by the multiple users to request the target process business; The loaded process instance request packets simultaneously sent by the multiple users to request the target process business are injected into the target cache container.

5. The method according to claim 1, characterized in that Also includes: After executing the target process business according to the requested resources, a distributed cache is used to cache the action execution data of the target process business and an access success instruction is returned to the first user terminal.

6. The method according to any one of claims 1 to 5, characterized in that The distributed process engine is a Flowable process engine.

7. A process business processing device of a distributed process engine, characterized in that: The device comprises: An instance acquisition module, used to acquire a process instance request packet sent by a first user end to request a target process service, wherein the process instance request packet is loaded with an instance identifier and a request instruction; An instance locking module, used to lock the target process service through a first execution script based on the request instruction; An instance execution module, configured to execute the target process business according to the requested resource if a requested resource corresponding to the instance identifier is queried from the target resource library; The instance returning module is used to return an access denial instruction of the target process service to the first user terminal if the requested resource corresponding to the instance identifier is not found from the target resource library.

8. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the process business processing method of the distributed process engine described in any one of claims 1 to 6 by executing the computer instructions.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the process business processing method of the distributed process engine according to any one of claims 1 to 6.

10. A computer program product, characterized in that It comprises computer instructions, and the computer instructions are used to enable a computer to execute the process business processing method of the distributed process engine according to any one of claims 1 to 6.

Images