Oracle Visual Builder: Applications That Outlive Their First Release · Module 15 · Performance
Too many calls
Lesson 150 of 176 · 3 min
A REQUEST PER ROW, A LOOKUP PER FIELD. Finding them, and THE PATTERNS THAT PRODUCE THEM WITHOUT ANYBODY NOTICING. Over-fetching is one large response. This is many small ones, and it is worse — because each request carries its own round trip and they frequently run one after another. THE CANONICAL PATTERN IS A CALL PER ROW, AND NOBODY EVER WRITES IT DELIBERATELY. A list is fetched, then something inside each row needs a value the list did not carry — a customer name for an id, a status description for a code — so the row fetches it. Twenty rows, twenty extra calls, and each row is individually reasonable. WHICH IS WHY IT IS INVISIBLE IN THE DESIGNER AND OBVIOUS IN THE NETWORK TAB. Nothing in the page says "twenty requests"; the tab shows twenty identical calls differing by one parameter — which is the signature, and once you…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Visual Builder: Applications That Outlive Their First Release, with a certificate on completion and a fourteen-day refund window.