Uploaded image for project: 'Serverless logic'
  1. Serverless logic
  2. SRVLOGIC-3

[core] Workflow state persistent storage

    XMLWordPrintable

Details

    • Feature
    • Resolution: Done
    • Blocker
    • 1.24.0
    • None
    • serverless-workflow
    • None
    • False
    • None
    • False
    • 0
    • 0% 0%
    • 2022 Week 32-34 (from Aug 8)

    Description

      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

      Attachments

        Issue Links

          account is impacted by

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-7206 A process with two activities is executed with errors

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          incorporates

          Task - Represents a small unit of work that is not end-user facing. KOGITO-6987 [KSW-Guides] Guide to help DB Admins to understand Kogito Workflow persistence

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-7301 [KSW-Guides] Persistence with PostgresSQL databases

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-7309 [KSW-Guides] Integration tests with PostgreSQL

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-6783 Enhance PostgreSQL persistence addon to support correlation

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-6982 Kogito Persistence addon for Postgresql breaks Serverless Workflow process into infinite loop

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-4015 Any Async Workitemhandler won't work with persistence enabled

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Activity

            People

              cnicolai@redhat.com Cristiano Nicolai
              ibek1@redhat.com Ivo Bek
              Marian Macik Marian Macik
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: