-
Feature
-
Resolution: Done
-
Blocker
-
None
-
None
-
False
-
None
-
False
-
2022 Week 32-34 (from Aug 8)
Motivation
Several use cases such as callbacks, async calls and the SAGA pattern require persistence of states for long-running workflows.
Goal
Enable PostgreSQL persistent storage for workflow states.
Scenarios
As a developer, I need to store the state of my long-running workflow so that it doesn’t consume CPU resources when waiting and can resume its execution upon an event/request arrival.
Expected outcomes
Workflow services can optionally connect to PostgreSQL persistent storage to store its state during a wait state.
Persisted workflows resume their execution upon an event/request arrival.
DB should be self-cleaning
Events in combination with persistence is not 100% reliable solution - acceptable for DP1
Auditing (i.e. storing historical data about past workflows) is out of scope
Workflow versioning is out of scope - it's recommended to use version as part of workflow identifier
- changing a workflow without updating workflow id can have unexpected behaviour with the already active workflows
- account is impacted by
-
KOGITO-7206 A process with two activities is executed with errors
- Closed
- incorporates
-
KOGITO-6987 [KSW-Guides] Guide to help DB Admins to understand Kogito Workflow persistence
- Resolved
-
KOGITO-7301 [KSW-Guides] Persistence with PostgresSQL databases
- Resolved
-
KOGITO-7309 [KSW-Guides] Integration tests with PostgreSQL
- Resolved
-
KOGITO-6783 Enhance PostgreSQL persistence addon to support correlation
- Resolved
- is blocked by
-
KOGITO-6982 Kogito Persistence addon for Postgresql breaks Serverless Workflow process into infinite loop
- Resolved
-
KOGITO-4015 Any Async Workitemhandler won't work with persistence enabled
- Resolved