Yep, that’ll do the trick.
This could go sideways if you’re dealing with heavy volumes coupled with large files, so be sure to follow the usual guidelines -
- Use the “Scope” property to limit the pipeline replications/handoffs of the file content (transformers are another option, but use what suits your design best) to child services
- Explicitly cleanup obsolete variables at appropriate places throughout the flow, and not just at the end
- If you are dealing with large files, then follow large-file handling principles, test for performance and benchmark the throughputs
- Gauge and make necessary resource (cores, heap) adjustments, based on #3
KM