Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 10 · REST and SOAP: calling Fusion, and being called
Bulk operations and rate limits
Lesson 104 of 177 · 2 min
Where REST stops being the right tool and a file load starts is a volume question, and the honest thresholds are lower than people expect. Below a few hundred records, REST is clearly right — immediate, per-record errors, no file handling. Above a few thousand, a file load is clearly right: one submission, one log, one reconciliation, and no per-call overhead. Between them is judgement, and the deciding factor is usually error handling rather than speed: a thousand REST calls produce a thousand potential failures somebody has to reconcile, and a file produces one report. THROTTLING ARRIVES BEFORE THE VOLUME LIMIT DOES. Fusion protects itself, and a loop firing calls as fast as it can will be slowed or refused — typically with a 429 or a service-unavailable response. That is not a defect and retrying immediately makes it worse. So any loop over a collection needs three things by…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 10 · REST and SOAP: calling Fusion, and being called
- 1What Fusion exposes, and what it does not
- 2REST vs SOAP: choosing without arguingFree preview
- 3Authentication and the service account
- 4Reading the REST API catalogue
- 5Your first call, and its error
- 6Payloads, child resources and partial updates
- 7Bulk operations and rate limits
- 8Fusion calling out: business events
- 9Idempotency and retries
- 10Versioning and surviving a quarterly update
- 11What breaks: five integration failures
- 12Lab briefing · Read, write and break an integration