BatchProcessing
Processing large volumes of data in scheduled or triggered batches rather than per-request.
Why we need this / what value this brings
Some work (nightly aggregation, payout calculation) doesn't need to happen per-request and is cheaper/simpler done in bulk on a schedule.
When to use this
Work that's naturally periodic or can tolerate delay, and would be wasteful or complex to do per-request.
How to use or implement this
Trigger via a scheduler/cron, make the job idempotent (safe to re-run if it fails partway), and log its outcome for monitoring.
Research questions
- Any batch jobs Localz needs (nightly provider payout calculation, report generation)?
Empty folder — drop notes, links, and findings here as you research.