MSAMM
Back to course

Oracle Integration Cloud: Building Integrations That Survive Production · Module 10 · Business events and publish/subscribe

OIC events between integrations

Lesson 107 of 175 · 2 min

Decoupling your own flows with published events. What it buys, and the traceability it costs when a chain spans four integrations. WHAT IT BUYS is genuine and worth having. One flow publishes; several subscribe. Adding a consumer does not touch the producer, which is the thing that makes an estate extensible rather than increasingly brittle. Different consumers can fail independently, retry independently, and be deployed independently. WHAT IT COSTS IS THE ONE PROPERTY THIS COURSE HAS BEEN BUILDING SINCE MODULE 2: being able to find the run. In a direct chain, one instance shows you the whole story. With events between four integrations, a single business transaction is four instances with no link between them — and answering "what happened to this order" means finding four runs and correlating them by timestamp and payload contents. THE FIX IS A CORRELATION IDENTIFIER CARRIED THROUGH EVERY EVENT AND LOGGED BY EVERY SUBSCRIBER.

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.

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 10 · Business events and publish/subscribe

  1. 1Event-driven versus polling
  2. 2Fusion business events, in practice
  3. 3Subscribing without losing events
  4. 4Ordering, and why you cannot rely on it
  5. 5At-least-once delivery
  6. 6OIC events between integrations
  7. 7What breaks: three event failures
  8. 8Lab briefing · Subscribe, drop, and catch up