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

[use case] Orchestration-based SAGA pattern

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Critical
    • 1.24.0
    • None
    • serverless-workflow
    • None
    • False
    • None
    • False
    • 2022 Week 32-34 (from Aug 8)

    Description

      Motivation

      The Saga design pattern is a way to manage data consistency across microservices in distributed transaction scenarios. A saga is a sequence of transactions that updates each service and publishes a message or event to trigger the next transaction step. If a step fails, the saga executes compensating transactions that counteract the preceding transactions.

      Goal

      Enable orchestration-based SAGA pattern in Serverless workflows

      Scenarios

      As a developer, I need to ensure data consistency in a distributed system without tight coupling

      As a developer, I need to compensate if one of the operations fails.

      As a developer, I need to implement transactions that span services so that the application maintains data consistency without using distributed transactions.

      Example: https://github.com/kiegroup/kogito-examples/tree/stable/kogito-quarkus-examples/serverless-workflow-saga-quarkus 

      Example: https://github.com/Azure-Samples/saga-orchestration-serverless 

      Expected outcomes

      The orchestrator executes saga requests, stores and interprets the states of each task, and handles failure recovery with compensating transactions.

      Attachments

        Issue Links

          incorporates

          Task - Represents a small unit of work that is not end-user facing. KOGITO-6308 Saga example with Serverless Workflow

          • 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-6784 Incorporate correlation support in kogito process runtime

          • 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-6785 Serverless Workflow Correlation integration with runtime

          • 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-6806 [KSW-Guides] Serverless Workflow with the Saga example

          • 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-6971 Serverless Workflow Correlation example with Callback

          • 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

          Task - Represents a small unit of work that is not end-user facing. KOGITO-7411 [KSW-Guides] Orchestration-based SAGA pattern

          • 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.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. KOGITO-6991 Saga Serverless Workflow example with persistence and 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.
          • Closed

          Activity

            People

              tdolphin-1 Tiago Dolphine
              ibek1@redhat.com Ivo Bek
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: