For each works on single thread. I still did not understand how parallel processing is achieved in this example. Can you please clarify if I missed something?
Thanks for detailed explanation with use case. Can you please let us know, i which kind of scenario we have to use so that it give us a clue... :) thanks again.
Hi Smita - The Batch component is for asynchronous and Fire-and-forget pattern. This Splitter-Aggregator is for real-time processing where the performance can be improved slightly by parallel execution of mutually exclusive tasks. So, the 2 components are for completely different purposes. Please feel free to let me know if you need more use-case examples.
Hi Smita - Technically handling large amount of data depends on infrastructure. You need to either vertically or horizontally scale for large data or split it to smaller chunk of data.
@@sivathankamanee-channel : when you say "where the performance can be improved slightly by parallel execution of mutually exclusive tasks" , I didn't exactly get where is parallel execution happening, for each execution takes place sequentially and not parallel as far as i know, please correct me if I am wrong.
Thanks for the videos. They are great. Regarding for-each I have the following confusion. 1 Regular For-each basically is used for iterative/ sequential processing . 2. Parallel For-each is used for parallel processing. 3. Regular For-each with batch-size is used to split the processing into batches of mule messages and does parallel processing. 4. Scatter gather does parallel processing. 5. Batch Job is parallel processing. I feel its an overkill by Mule 4 to provide so many overlapping activities for processing in parallel. When to use what and how exactly they differ is getting difficult to understand. Also when we say parallel processing for for-each ( with batch size) and parallel for -each - are we saying they are going to spawn multiple threads ? Can you help create a video to explain 1. differences in each of these 2. the way threads are spawned in each of these ? This will hugely benefit many of us learning and working on mule. Thanks again for your wonderful series of Mule learning vidoes. Appreciate it and enjoying them thoroughly.
Very helpful on my new role as an Mulesoft Developer. Thank you!
Excellent explained. I liked the way you are explaining the topics.
My aggregation is incompelete that's why the setting of variable on "Aggregation complete" is not working.
Very useful Info. Thanks for sharing
For each works on single thread. I still did not understand how parallel processing is achieved in this example. Can you please clarify if I missed something?
We can set the batchSize to vars.size in order to achieve parallel processing. Please refer to the example below:
@@pratikpriyadarshi8910 : in this case why would you need for each then, as you are sending complete incoming data as it is without splitting
Thanks siva. Very interesting topic
Thanks for detailed explanation with use case. Can you please let us know, i which kind of scenario we have to use so that it give us a clue... :) thanks again.
Hi siva,
Can this be achieved by Batch Scope and Batch Aggregator? If yes then then how does it differ?
Thank You,
Smita
Hi Smita - The Batch component is for asynchronous and Fire-and-forget pattern. This Splitter-Aggregator is for real-time processing where the performance can be improved slightly by parallel execution of mutually exclusive tasks. So, the 2 components are for completely different purposes. Please feel free to let me know if you need more use-case examples.
@@sivathankamanee-channel Can large amount of data be handled by Splitter-Aggregator pattern? or will have to consider Batch component in this case?
Hi Smita - Technically handling large amount of data depends on infrastructure. You need to either vertically or horizontally scale for large data or split it to smaller chunk of data.
@@sivathankamanee-channel : when you say "where the performance can be improved slightly by parallel execution of mutually exclusive tasks" , I didn't exactly get where is parallel execution happening, for each execution takes place sequentially and not parallel as far as i know, please correct me if I am wrong.
Nice video please do more videos on mule 4
Nice videos sir
Nice and intresting .Could you please explain spliiter and gather for xml or json payload
Hi SwethaReddy - I have already added the video for Splitter-Gather. Please check this out: th-cam.com/video/gpgn7yQg26I/w-d-xo.html
sir we need admin classes ... please provide us the sessions on mule admin
Awesome
great
Thanks for the videos. They are great. Regarding for-each I have the following confusion.
1 Regular For-each basically is used for iterative/ sequential processing .
2. Parallel For-each is used for parallel processing.
3. Regular For-each with batch-size is used to split the processing into batches of mule messages and does parallel processing.
4. Scatter gather does parallel processing.
5. Batch Job is parallel processing.
I feel its an overkill by Mule 4 to provide so many overlapping activities for processing in parallel. When to use what and how exactly they differ is getting difficult to understand.
Also when we say parallel processing for for-each ( with batch size) and parallel for -each - are we saying they are going to spawn multiple threads ?
Can you help create a video to explain 1. differences in each of these 2. the way threads are spawned in each of these ? This will hugely benefit many of us learning and working on mule.
Thanks again for your wonderful series of Mule learning vidoes. Appreciate it and enjoying them thoroughly.