...
Use the regular https://infozone.atlassian.net/wiki/x/IgMkEg definition using Dynamic Workflows to define how to package a scale-out. For instance: yOU HAVE TO MANUALLY DEFINE You need to define when these ECDs will activate.
A Collection Workflow scales with 1 extra Workflow per ECD.
A Processing Workflow scales with 3 extra Workflows per ECD.
Or combine the above into the same
...
ECD
...
.
Scheduling a scale-out configuration:
...
| Warning |
|---|
Questions: Assumedly a scaling solution will contain multiple workflows and based on the above these workflows can be scheduled to be started at specific times or based on metrics? How does it being based on metrics work? does this need to be configured somewhere? The key difference for customers is that scaling workflows are quicker/more efficient at processing data that regular workflows? It’s not more automated in general but it is automatic at being efficient. (that sounds weird, but I think I understand what I mean.) This is why the metric question is interesting.. because sometimes a customer won’t know what times they’ll need to scale workflows. |
| Info |
|---|
ECD from Chat GPT: In simple terms, an ECD is like setting up a workspace that’s fully equipped for a job, so the tasks can start and run without interruptions or missing tools. |