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

[core] Domain-specific data correlation between workflow and events (stretch goal)

XMLWordPrintable

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

      Motivation

      Knative Eventing is a serverless platform that enables developers to create event producers and consumers for their applications. Knative Eventing uses standard HTTP POST requests to send and receive events between event producers and consumers. These events conform to the CloudEvents specification, which enables creating, parsing, sending, and receiving events in any programming language.

      Goal

      Enable events to trigger specific workflows based on its payload

      Scenarios

      As a developer, I need to address workflow(s) via domain-specific values in data when sending an event so that the event is consumed only by active workflows which contain that domain-specific value in data.

      Expected outcomes

      Workflow instances are correlated with incoming events via workflow identifier or workflow data
      Correlation attributes are set only using events, i.e. a workflow instance has to have event state as a start

      Correlation of events (between events) is out of scope - that’s for complex event processing
      Setting correlation attributes using a REST request (e.g. when the operation state is a start) is out of scope

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

              Created:
              Updated:
              Resolved: