MSAMM
Back to course

Oracle Integration Cloud: Building Integrations That Survive Production · Module 14 · Performance and throughput

Payload size and memory

Lesson 140 of 175 · 3 min

The limits you WILL meet, how they present when you exceed them, and the streaming alternative. OIC holds a message in memory while it processes it, and there are limits on how large that message may be. The exact figures depend on the platform version and on the adapter, so read the current ones rather than trusting a number from a course — what matters is that a limit exists and that you will meet it, because file sizes only ever grow. HOW IT PRESENTS IS THE PART WORTH KNOWING, BECAUSE IT DOES NOT SAY "TOO BIG". The instance fails with a memory error, or a generic processing error, or occasionally by simply not completing. And crucially it fails on the LARGE file while succeeding on every small one, so it presents as an intermittent problem: the flow works every day and fails at month end. THAT PATTERN — works,

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 14 · Performance and throughput

  1. 1Where the time actually goes
  2. 2Per-record calls versus batch
  3. 3Parallel processing, and its cost
  4. 4Payload size and memory
  5. 5Message packs and cost per run
  6. 6Throttling and back pressure
  7. 7What breaks: the integration that worked in test
  8. 8Lab briefing · Ten times the volume