The previous article covers the six mechanisms, what each is for, and how the benchmark corrected itself. This is what got cut from it: the code I removed for length, the debugging that only makes sense verbatim.
A UAT tester reported that not every selected row got processed. I could not inspect the APEX session in UAT, and SQL Developer cannot see an APEX collection because it is not part of the APEX session. I worked around it with a report region that only shows in debug mode.
Last time I wrote about this I had four mechanisms and a ranking: I saw a Go program fire twenty AI calls at once. Could I do that in PL/SQL?. Now I have six mechanisms and no ranking, because when I put them all on the same measurement basis
PL/SQL has no asynchronous HTTP. Every REST call blocks its session for the whole round trip, so N calls at once means N sessions, and every way of getting more sessions in Oracle is job-based.
I pasted the same Interactive Grid toolbar JavaScript into three applications over three years without ever reading it, because I was told it was the standard and it worked. A colleague who had never touched the block reviewed a story that included the script, pointed out some unused variables.