I feel like I have a (somewhat) simple use case involving Durable Objects + Queues. So my durable o
I feel like I have a (somewhat) simple use case involving Durable Objects + Queues.
So my durable object is an orchestrator for my project. Every 10 seconds it runs a new "poll". It runs on a forever loop until my customer shuts it off.
During that "poll" I need to make 1000~ fetch requests to a third party api, and the durable object needs the responses for those 1000 fetch requests.
The problem is durable objects only support 6 open connections, so I have to iterate over the 1000 fetch requests, and it can take a while to iterate over that many async requests. I need these 1000 requests to resolve as quickly as possible.
My thinking is maybe queues could help with this? But my concern is queues won't resolve these requests fast enough since the consumer worker needs to iterate over the queues.
So my durable object is an orchestrator for my project. Every 10 seconds it runs a new "poll". It runs on a forever loop until my customer shuts it off.
During that "poll" I need to make 1000~ fetch requests to a third party api, and the durable object needs the responses for those 1000 fetch requests.
The problem is durable objects only support 6 open connections, so I have to iterate over the 1000 fetch requests, and it can take a while to iterate over that many async requests. I need these 1000 requests to resolve as quickly as possible.
My thinking is maybe queues could help with this? But my concern is queues won't resolve these requests fast enough since the consumer worker needs to iterate over the queues.
