Overview
Some workloads do not require an immediate response. They can be submitted in bulk and processed later.
Batch processing groups many requests together. The provider can run them during periods of lower system demand. The user accepts a delay in exchange for lower cost.
This is useful for:
- Large-scale classification.
- Bulk extraction.
- Delayed enrichment.
- Non-urgent report generation.
- Processing large lists.
The logic is load balancing. Demand rises and falls during the day. Delay-tolerant work can be shifted to quieter periods rather than competing with immediate interactive requests.
Batching is therefore a time-cost trade-off. It should be used when speed is less important than efficiency.