MSAMM
Back to course

Oracle Integration Cloud: Building Integrations That Survive Production · Module 6 · Orchestration patterns

App-driven versus scheduled

Lesson 59 of 175 · 2 min

Two integration styles, and the requirement decides which rather than your preference. APP-DRIVEN means something ELSE starts the flow. A caller hits an endpoint you exposed, a business event fires, a file lands where the adapter is watching. The trigger is external and the timing is not yours. SCHEDULED means OIC starts it on a frequency you configure. Nothing outside has to know the integration exists. THE REQUIREMENT SHAPES THAT FIT EACH. App-driven fits "when X happens": a payment is confirmed, an order arrives, an approval completes. Latency is low and volume follows the business rather than a clock. Scheduled fits "every day", "every hour", and everything measured in batches: extracts, reconciliations, file processing, catch-up runs. It is also the honest answer to a great many requirements described as real-time, because "we need it during the day" is usually a schedule, and a schedule is cheaper, simpler and easier to…

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.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 6 · Orchestration patterns

  1. 1App-driven versus scheduled
  2. 2Invokes, and the shape of a flow
  3. 3Switch, and branching honestly
  4. 4Loops over collections
  5. 5Local variables and assignment
  6. 6Sub-integrations and reuse
  7. 7Synchronous versus asynchronous
  8. 8Stitching in a database or file step
  9. 9When an orchestration is too big
  10. 10What breaks: three orchestration failures
  11. 11Lab briefing · Build a four-step flow