6.32Batch processing vs For Each

Don't confuse Mule Batch Jobs with For Each.

For Each:

collection already in flow
      ↓
iterate over it

Batch processing:

large data processing workload
      ↓
records processed in stages
      ↓
better suited to substantial volumes

You'll see Mule Batch when processing:

large migrations
nightly imports
data synchronization

We'll touch it more in the bulk/async module.

For now:

small/normal collection logic
→ For Each

large ETL-style workload
→ consider Batch / Bulk API / async architecture