Batch processing
The processing of work in grouped sets, typically on a schedule, rather than handling each item individually the moment it arrives.
In more detail
Batch processing collects work into groups and processes them together, usually on a schedule, rather than handling each item the instant it arrives. Running the payroll for everyone at once, reconciling the day's transactions overnight, or importing a file of records are classic batch jobs. The approach is efficient when immediate results are not required.
The contrast is with real-time or stream processing, which handles each item as it comes. Batch trades latency for throughput and simplicity: it is easy to reason about and efficient at volume, but nothing happens until the batch runs. Choosing between them is a question of whether the work needs to be immediate or can wait for the next scheduled run.
Where this shows up at Ceven
Ceven workflows can run in batches on a schedule or react to events one at a time, depending on what the process needs. High-volume work that does not need to be instant can be processed in scheduled runs across the connected tools, with fan-out handling the items in parallel and the whole batch recorded in the audit trail.