Oracle Integration Cloud: Building Integrations That Survive Production · Module 14 · Performance and throughput
Where the time actually goes
Lesson 137 of 175 · 2 min
Network, target system, mapping and platform overhead. MEASURING BEFORE OPTIMISING, because the guess is usually wrong. An integration is slow and everybody has a theory before anybody has a number. The mapping is too complex. The platform is slow. There is too much data. All three are plausible and, in most real cases, all three are wrong. THE TIME IN A TYPICAL FLOW IS OVERWHELMINGLY SPENT WAITING FOR OTHER SYSTEMS. A call to the ERP takes as long as the ERP takes. A thousand of them take a thousand times that, and no amount of mapping optimisation moves the figure at all — because the mapping is microseconds and the call is hundreds of milliseconds. SO THE MEASUREMENT IS THE FIRST STEP AND IT IS AVAILABLE WITHOUT ANY TOOLING. Open an instance in the console. The activity stream carries timings per step. Read where the seconds are. Almost always one…
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.