Cloudflare

`export async function doRequests(requests) {
  const responses = await Promise.all(requests.map(request => fetch(request)))
  const responseData = await Promise.all(responses.map(response => response.json()))
  return responseData
}`

I would assume that you're not reaching `responseData` until all of the `responses` have been resolved?

Likely?  I'm trying to determine how to have the requests processed as soon as they're complete.  First attempt at this and I see numerous examples out there.  Coming from a non-event loop language, this is a bit of a learning curve.

You could maybe do 
```js
const responseData = await Promise.all(requests.map(request => fetch(request).then(r => r.json()))
```

so it'll read each body as soon as the request completes, opening up the next one to go ahead

Thanks for the input!  Let me experiment with that and see if that works.

Progress!  I think you're onto something <@312617227490951168> .  Thank you!

```
Trace: CompileError: WebAssembly.instantiate(): Wasm code generation disallowed by embedder
```

Am I not allowed to do this?

```typescript
await initialize(fetch("https://unpkg.com/svg2png-wasm/svg2png_wasm_bg.wasm"));
```

Yeah thats blocked, WASM has to be included with the worker

How to solve the problem of sending agents and being walled

MongoDB Realm "performance and speed" 🤡

what does `wrangler publish` use to build the typescript app before uploading? is it esbuild?

image

We're on Bundled, how come it goes above 50ms?

can it just "be maybe killed if we need the resources" after 50ms?

pretty much. It's a little variable to allow for spikes and such

So you can go over if other requests are under

As long as you're on average below, you're good

Both from a CF workers perspective as well as an architecture design, how would you recommend implementing a tracker for number of requests per second

Maybe expiring KV keys? I have been playing with a workers / kv project lately. https://hottakesdictionary.com/

Depends what your requirements are - KV comes with eventual consistency and writes-per-second constraints, DO comes with strong consistency but latency because of that global uniqueness, etc

<#981314061268578304> would be the way I go for tracking requests 🤔

Although I guess not suitable for displaying stats publicly given extreme rate limiting on read end

Interesting, haven't looked at this before. I might just avoid it and try to keep my project currently scoped to KV, DO, and Pages with Functions

Its already a lot of moving parts, my first app from ground up using CF only