Hi everyone, I've not actually got access yet just theory crafting out my usecase... as far as I und
Hi everyone, I've not actually got access yet just theory crafting out my usecase... as far as I understand it, in order to have say thousands of requests/pages without immediately bankrupting myself I would need to go the Durable Object route and that basically instantiates a browser that I can re-use but need to keep alive with alarms? I could then queue up my requests to the DO-Browser so that I don't get any issues with puppeteer etc. I've seen further up this thread @Pedro mention that in the future there will be a built-in way to do this? Would this essentially mean that if I had enough traffic to justify it in the future I would be able to keep 1 or more Browser instances running at all times that are being fed requests by a queue, and that way I wouldn't incur the 10c charge per session or require too many concurrent sessions? Thanks!
