MSAMM
Back to course

Oracle Integration Cloud: Building Integrations That Survive Production · Module 3 · Connections and adapters

One connection or several

Lesson 29 of 175 · 2 min

Sharing a connection makes rotation easy and blast radius wide. Splitting them reverses both. The trade, decided per system rather than as a rule. SHARE where the credential is the same and the flows have the same standing. Ten integrations reading Fusion under one service account: one connection, one rotation, one place to see what talks to Fusion. The cost is that they fail together, which is usually acceptable because they would anyway — the account is the same. SPLIT where the flows differ in a way that matters. Three cases are worth it. DIFFERENT PRIVILEGE: a flow that only reads should not use a connection whose account can write, because a connection is a security boundary and every integration inherits the whole account. DIFFERENT CRITICALITY: the interface that pays suppliers and the one that syncs a reference list should not share a failure. DIFFERENT OWNER: two teams, two rotation…

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 3 · Connections and adapters

  1. 1What a connection is
  2. 2Choosing an adapterFree preview
  3. 3The REST adapter
  4. 4The SOAP adapter
  5. 5The FTP adapter
  6. 6The database adapter
  7. 7Testing a connection properly
  8. 8One connection or several
  9. 9Connectivity agents, and when you need one
  10. 10What breaks: four connection failures
  11. 11Lab briefing · Three connections, three systems