Oracle Integration Cloud: Building Integrations That Survive Production · Module 6 · Orchestration patterns
Synchronous versus asynchronous
Lesson 65 of 175 · 2 min
Whether the caller waits. That is the whole distinction, and it decides the timeout, the response and the design. SYNCHRONOUS: the caller holds the connection until the flow finishes and gets the result. Simple, immediate, and bounded by a timeout that is not yours — the caller's, the network's, or the platform's, whichever is shortest. ASYNCHRONOUS: the caller gets an acknowledgement immediately and the work happens afterwards. The caller is not waiting, so a slow flow is not a caller's problem. THE PATTERN THAT TURNS A SLOW FLOW INTO A FAST ACKNOWLEDGEMENT is the reason this lesson matters: accept, acknowledge, then process. The caller gets a reply in milliseconds and the work is done properly rather than under a clock. Where the caller needs the outcome, they poll or receive a callback — which is the Fusion module's long-running-operation lesson from the other side. THE FAILURE TO UNDERSTAND IS 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