You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Flow and Workload are tightly coupled as workload are defined inside of a flow definition
This has a few drawbacks
You can't scale only a specific workload
Changing a workload will touch the whole flow definition
Workload can't be shared across other flows
To solve this issue GoFlow will support a special kind of Operation called ApplyExternal() like Apply()
It will take a unique ID of the workload that need to be called
Node('n2').ApplyExternal('task1')
To define a workload user need to use the GoFlow Library and Register a Workload using the unique ID
fs.Register('task1', PerformTask1)
fs.StartWorkload(['myflow']) // start workload will take the list of flows
s8sg
changed the title
Allow GoFlow workload to be completely independent to the flow
[GoFlow-4] Allow GoFlow workload to be completely independent to the flow
Jun 25, 2023
Currently Flow and Workload are tightly coupled as workload are defined inside of a flow definition
This has a few drawbacks
To solve this issue GoFlow will support a special kind of Operation called
ApplyExternal()
likeApply()
It will take a unique ID of the workload that need to be called
To define a workload user need to use the GoFlow Library and Register a Workload using the unique ID
Workload will have the same signature
The text was updated successfully, but these errors were encountered: