MSAMM
Back to course

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

Sub-integrations and reuse

Lesson 64 of 175 · 2 min

Calling one integration from another. The maintenance argument, the versioning trap, and the depth beyond which debugging becomes archaeology. THE MAINTENANCE ARGUMENT is the same one this catalogue makes everywhere. A supplier lookup used by four flows, written once, is one thing to change. Written four times it is four, and three of them will be missed. THE VERSIONING TRAP is specific to this product and it is severe. A sub-integration has callers, and editing it changes what all of them do, at once, with no version boundary — which is Module 2's edit-versus-clone lesson applied to something several flows depend on. A change tested against one caller is deployed to four. Clone to a new version and move callers deliberately, or accept that every change is a change to everything. THE DEPTH LIMIT IS ABOUT TWO, and the reason is diagnostic. A flow that calls a sub-integration is easy…

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