Hi Alvaro, thank you for the question. This restriction is new to me and does seem to be enforced. I used a load test tool called siege to simulate 30 concurrent users calling a public page that has 3 small reports on it 5 times each for a total of 150 requests. I got similar results running over customer-managed ORDS and the out-of-the-box URL. I started receiving 503 errors.

Siege command was similar to this: siege -c30 -r5 "example.com/ords/prod/r/cloudnueva/website/home&q… --no-parser

Customer Managed ORDS 12 503 errors out of

150 requests:
Transactions:                 138 hits
Availability:               92.00 %
Elapsed time:               10.34 secs
Data transferred:           10.46 MB
Response time:                1.28 secs
Transaction rate:           13.35 trans/sec
Throughput:                1.01 MB/sec
Concurrency:               17.05
Successful transactions:         137
Failed transactions:              12
Longest transaction:            8.40
Shortest transaction:            0.45

Standard URL ORDS 32 503 errors out of 150 Requests

Transactions:                 118 hits
Availability:               78.67 %
Elapsed time:                8.43 secs
Data transferred:           20.99 MB
Response time:                1.27 secs
Transaction rate:           14.00 trans/sec
Throughput:                2.49 MB/sec
Concurrency:               17.74
Successful transactions:         117
Failed transactions:              32
Longest transaction:            5.99
Shortest transaction:            0.44

I suspect I got fewer errors from my customer-managed ORDS URL because it runs faster than the standard URL. With a concurrency of 5, I got 0 errors, so the limit seems to be there.

In conclusion, 5 simultaneous users could still support hundreds of actual users, just not if they all hit Go simultaneously.

Hi Jim, My approach requires setting up a Virtual Machine (VM) and running ORDS on that VM. That way, you can point your Domain to a specific public IP Address. The wallet comment relates to how ORDS connects to the Autonomous Database. To be honest, my approach is pretty labor-intensive and requires no small amount of maintenance.

If you are still interested, Scott and by reference Dimitri's blog posts have more details on the how. spendolini.blog/front-man-using-nginx-to-proxy-re…