indeedeng / iwf Goto Github PK

What we can do more than Cadence Temporal web ui:
Two pages as mvp:
Page one: search for workflow , and click on to the workflow page

page two is workflow page :
1: show histories by workflow state execution
2: show internal info of commands and pending data
3. Allow reset by state and state execution id

Need to evict cache when history event id changed

long running activities are super powerful in Cadence Temporal as it allow using local machine memory and disk for executing.

However, This will not be considered into V2 of IWF. Because today’s pushing to execute task’s won’t work for long running task. So this requires to implement the polling mechanisms to execute tasks.

Workaround 1 is to use workflow instead but which means you may have to upload the large amount of states into other storage like s3

workaround 2 is combining IWF and Cadence Temporal. Use IWF to start a Cadence Temporal workflow, which just executes a long running activity.

Potentially IWF v1 can just schedule a Cadence Temporal activity and let user to execute the activity by using Cadence SDKs. But this will leak the implementation details of Cadence Temporal to IWF users so it’s considered as a “Hack” and will not be a good idea.

the hack is from https://github.com/indeedeng/iwf/pull/72/files

a private query attribute cannot be queried, we may consider renaming query attribute to something else.

SharedAttribute

Or just Attribute

Or generate default command id on server side

maybe workflow/get API? as it can be retried from describe workflow.

Add link to design doc

This will be more generic and more useful

Sdk: rename state local attributes to state local.
method : set/get attributes
RecordEvent

change README to use docker only because Temporalite doesn’t support search attributes

need to test and verify

{
  "message": "500 Internal Server Error",
  "source": "GoSDK",
  "stackTrace": "",
  "cause": null,
  "applicationFailureInfo": {
    "type": "GenericOpenAPIError",
    "nonRetryable": false,
    "details": null
  }
}

This won't be useful enough to debug

Running, completed, failed, timeout , canceled

This will be more friendly to use than cadence temporal Java sdk to wait for results

the template is commented out today: https://github.com/indeedeng/iwf/blob/main/config/config_template.yaml

See example of how to use it https://github.com/cadence-oss/cadence-notification/blob/master/Dockerfile#L26

It's missing Cadence and other setup, also need to use templating command to converting the value from template into config files

This will help removing deprecating code

It should return 400 as defined in swagger

It's hardcoded to 10s today.

1. In memory matching only. Activity task will wait for match and return , only wait for 1-2 sec to reserve the activity timeout for APIs
2. Test only
3. Disabled by default
4. IwfWorkflowType as queue name

This will be more friendly to use than cadence temporal reset

Idea 1

• any query / search attributes has changed to a certain value. Query attributes are not readable by server so we may only support watching whether or not a query attribute has changed
• easy to implement but not friendly to use

Idea 2

• workflow defines an internal data channel. Any state can listen to it, or wait for results
• hard to design/implement but easy to understand/use)