Developer Mode Workflow Patch Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing workflow management systems face challenges in efficiently managing workflow instances, particularly in development versus production environments, where developer productivity and system performance are conflicting priorities, and in ensuring scalability and security in high-load scenarios.
Innovation Solution
The implementation of a 'Developer Mode' for workflow systems, which allows for blocking or unblocking workflow instances based on mode settings, and the use of lock-free execution and record-level security access in in-memory databases to enhance scalability and security, respectively.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If workflow template patches are deployed in traditional workflow management systems, then system updates and improvements are achieved, but execution of new workflow instances is blocked and data inconsistencies may occur
Solution Approach 1:
The system dynamically adjusts its behavior based on the developer mode setting. When developer mode is enabled, the system allows new workflow instances to execute alongside patched templates, prioritizing developer productivity. When disabled, it enforces strict blocking to maintain data consistency. This dynamic configuration resolves the contradiction by allowing the system to adapt its consistency enforcement based on operational context.
Solution Approach 2:
The patent introduces a mode parameter (developer mode on/off) that changes the system's patch deployment behavior. This parameter controls whether new workflow instances are blocked during patch deployment. By changing this parameter, the system can switch between two operational states: one prioritizing data consistency (mode off) and another prioritizing developer productivity (mode on), thus resolving the fundamental contradiction.
2Reliability
If database-level locks are used to block workflow execution during patch deployment, then data consistency is maintained, but system performance and scalability deteriorate
Solution Approach 1:
The patent extracts the blocking mechanism from the database level to the application level. Instead of using database-level locks that affect the entire system, the blocking is implemented through workflow template metadata and instance checks at the application layer. This extraction reduces system complexity and database contention while maintaining data consistency through targeted application-level controls.
3Ease of operation
If traditional locking mechanisms are used for workflow execution, then execution control is maintained, but locking bottlenecks reduce system performance under high load
Solution Approach 1:
The patent replaces mechanical database locking mechanisms with a software-based control system using workflow instance metadata and application-level checks. This substitution eliminates the performance bottleneck of database locks while maintaining execution control through the developer mode setting and workflow template versioning. The system achieves both control and high throughput by operating at the application layer rather than the database layer.
4Reliability
If workflow instances are blocked during patch deployment, then data inconsistencies are prevented, but developer iterative changes and testing are hindered
Solution Approach 1:
The system dynamically adapts its patch deployment behavior based on the developer mode configuration. In developer mode, the system allows iterative changes and testing by permitting new workflow instances to execute with updated templates. In production mode, it enforces strict blocking to prevent data inconsistencies. This dynamic behavior enables easy deployment in development while ensuring reliability in production.
Solution Approach 2:
The patent applies different quality requirements to different operational contexts. In developer mode, the system prioritizes flexibility and ease of deployment, allowing local deviations from strict consistency rules. In production mode, it enforces strict data consistency requirements. This local quality approach allows easy deployment during development while maintaining high reliability during production operations.
Data Source
AI summary
In a first method, a developer mode is determined when a workflow template patch is received, and execution of new workflow instances is either blocked or permitted, or continued execution of workflow instances is forbidden. In a second method, parallelization of workflow execution is provided in an in-memory database management system. In a third method, after received user privilege information, database records associated with a workflow are determined and stored for use at workflow instance runtime. In a fourth method, artifacts used by a workflow are identified using a workflow template. When a command to execute a workflow instance is received, information is stored for generating instances of artifacts for use during execution of the workflow instance. In a fifth method, for a workflow template to be inactivated, the associated workflow template is suspended after currently executing workflow instances have completed and job executors have acknowledged a suspending state.