Batch processing
Batch processing handles a defined set of data or jobs together in one run.
Process a defined set together
Batch processing groups data or jobs into one run. A schedule or a prepared dataset may trigger the start. It does not have to happen at night. What matters is the batch's selection and processing boundary.
In a fictional example, a product import contains records P-11, P-12 and P-13. If P-12 fails because of an invalid category, the others may already have been imported, depending on the method. A batch is not automatically an all-or-nothing transaction. Define the result per record, the retry unit and protection against duplicate imports. The run notification alone establishes neither complete success nor freshness between runs.
Sources
Related terms
- Change data captureChange data capture records database changes so that downstream applications can process them.
- IdempotencyAn idempotent operation has the same intended effect on system state when repeated identically as when performed once.
- Server-sent eventsServer-sent events carry text notifications from server to client over HTTP, for example about the progress of a background job.
- Entity tagAn ETag identifies a particular representation version of an HTTP resource and supports conditional reads or changes.
- Cross-Origin Resource SharingCORS controls browser access to responses across origin boundaries. It replaces neither API login nor permission checks.
- Electronic Data InterchangeEDI transfers structured business documents between systems. Format, partner profile, data mapping and responses need to agree.
Articles on this topic
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.