-
Notifications
You must be signed in to change notification settings - Fork 4
Supported Features
devsda edited this page May 7, 2019
·
3 revisions
- Nodes can be heterogeneous in nature in a single workflow.
- Explaining with e-commerce reversal use-case :
- In reversal workflow, the major involvements are :
- Collect already paid taxes from government.
- Give back product amount to customer.
- Collect shipment from Customer.
- Return/Collect money to/from seller.
- Do required ledgering.
- Above nodes together forms a single workflow. All these nodes can be individual teams, and they may have their codebase in different languages. At the same time, they have to collaborate with each other to complete reversal (return/replacement) for given end customer. For this use-case, workflow with heterogeneous node support is must.
- In reversal workflow, the major involvements are :
- Explaining with e-commerce reversal use-case :
- Supported workflows - Conditional and Unconditional workflow.
- Conditional workflow - Conditional workflow is a workflow that executes child node on the basis of parent node’s response (which is name of an edge)
- Unconditional workflow - Unconditional workflow is a workflow that executes all its child nodes once all parent nodes completed successfully. This type of workflow is very famous in data analytics. Ex -> ETL executions.
- Register Clients
- Add multiple endpoints
- Update endpoint details
- Retrieve client and endpoint details
- Execute workflow
- Resume Execution
- Restart Execution
- Kill Execution
- Retry given node with linear/exponential time-off
- Retrieve state of execution
- Notify client through AWS SNS/Azure Notification Hub.