Oracle Integration Cloud: Building Integrations That Survive Production · Module 14 · Performance and throughput
Per-record calls versus batch
Lesson 138 of 175 · 3 min
A thousand records as a thousand CALLS or one FILE. The threshold where the second wins, and why it is LOWER than most people expect. Per-record calls are the natural way to write an integration and they are right for small volumes. Loop the records, call the target for each, handle each result individually. Every record is independently traceable and independently retryable, which is genuinely valuable and is what makes this the default. THE COST IS THE ROUND TRIP, AND IT IS PAID ONCE PER RECORD. Say a call takes 300 milliseconds — unremarkable for an ERP. A hundred records is thirty seconds and nobody notices. A thousand is five minutes. Ten thousand is fifty minutes, and the nightly window is four hours, so the flow is now a scheduling problem rather than a performance one. THE BATCH ALTERNATIVE PAYS THE ROUND TRIP ONCE. Build one file or one bulk…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Integration Cloud: Building Integrations That Survive Production, with a certificate on completion and a fourteen-day refund window.