iwf
iwf copied to clipboard
iWF is a WorkflowAsCode microservice orchestration platform offering an orchestration coding framework and service for building resilient, fault-tolerant, scalable long-running processes
Looks like the images published on docker hub under iworkflowio/iwf-server-lite and iworkflowio/iwf-server are "all-in-one" images, which are 500MB+, but looking at `docker-compose/docker-compose.yml`, it pulls in temporal separately, so there's no...
Sometimes user would put `http://localhost:8080/iwfWorker/` as URL which will have errors, because it will be appended to the state APIs, like : ``` http://localhost:8080/iwfWorker//api/v1/workflowState/start ``` Because common to run into...
Optional to use for api service config https://github.com/indeedeng/iwf/pull/368 https://github.com/indeedeng/iwf/pull/370 TODO: https://github.com/indeedeng/iwf/blob/5debdce14a8bd195557e3fb728904eac7a85bc85/service/interpreter/globalVersioner.go#L21 has a bug for continueAsNew. The continuedAsNew run will inherite the SAs from previous, but they may have call...
Allow providing the delay duration at workflow options on start so that user code doesn’t need to use wait until
The current implementation uses a sub workflow: https://github.com/indeedeng/iwf/pull/345 requires to provide `WaitingForCompletionStateExecutionIds` on starting workflow which is cumbersome to use. It's required because we want minimize the initiation of these...
1. more accurate to use relative time 2. easier for unit test 3. cleaner and easier to read the history events
Start with only LoadAllNoLock persistence in both current and next states. in the future, we may change to not read persistence in waitUntil Optional to enable this feature in SDK