MSAMM
Back to course

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

What breaks: the integration that worked in test

Lesson 143 of 175 · 2 min

Test volumes are small and clean. Three ways a flow that PASSED UAT fails at production volume, and how to provoke each first. ONE: TIME. IT NO LONGER FITS IN ITS WINDOW. A flow processing 50 test records in 20 seconds processes 20,000 production records in over two hours — and the nightly window, or the next scheduled run, arrives before it finishes. Module 7's overlapping-run failure, caused by nothing but volume. Provoke it by timing a run and multiplying by the real record count before you believe the flow is fast enough. TWO: SIZE. THE MESSAGE NO LONGER FITS IN MEMORY. Lesson 4, and it presents as an intermittent failure at month end rather than as a size problem. Provoke it by running the largest file the business will ever produce — ask them what that is, because the answer is usually much larger than the sample they sent.…

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 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