Deno Deploy - Nested Fetch And Other Recursive Serverless Patterns Are Not Possible

[janwilmake]

Hi, yesterday did some experiments to see how performant the Deno deploy serverless is and how easy it is to perform 1000 fetch requests in parallel. I found that there is an undisclosed limit of 100 parallel fetch requests. This is quite high, but unfortunately this seems to also be capped across multiple independent requests to the same 100.

Cloudflare has the same problem, and this makes it required to use a queue rather than just using workers that call themselves in a nested way. Also, with Deno Deploy I get a LOOP_DETECTED error which forbids me to call my worker from the same worker. Why? I think creating recursive patterns (with good base cases) could be a great way to create patterns for server less to do more powerful things.

I thought the idea of serverless was that a single execution of a serverless function gets a predetermined amount of compute and memory but it seems there are some other limits in place.

My experiments can be found here

Has anyone else tried things in this type of way? Any solutions? My goal would be to pretty much execute 10.000 fetch requests within a second and get all results back in a single response, so starting up a queue would be undesirable.