Oracle Integration Cloud: Building Integrations That Survive Production · Module 6 · Orchestration patterns
Stitching in a database or file step
Lesson 66 of 175 · 2 min
Mixing adapters inside one flow — read a file, call an API, write to a database — and the staging question: what lives in the payload and what lives somewhere durable. Mixing is normal and it is one of the strongest arguments for the platform. A flow that reads a file, enriches each record from Fusion and writes results to a database is three adapters and one design. THE STAGING QUESTION IS THE HARD PART. Everything in the payload is IN MEMORY and lives only for the run. Anything durable — a file, a database table — survives the run and can be inspected, resumed from and reconciled against. KEEP IN THE PAYLOAD: the current record, small lookups, values you need for the next step. PUT SOMEWHERE DURABLE: anything you would need after a failure, anything too large to hold, and anything you would want to reconcile against later. The…
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.
In this module: Module 6 · Orchestration patterns
- 1App-driven versus scheduled
- 2Invokes, and the shape of a flow
- 3Switch, and branching honestly
- 4Loops over collections
- 5Local variables and assignment
- 6Sub-integrations and reuse
- 7Synchronous versus asynchronous
- 8Stitching in a database or file step
- 9When an orchestration is too big
- 10What breaks: three orchestration failures
- 11Lab briefing · Build a four-step flow