poro Comments - Answer Overflow

poro

•Created by poro on 6/27/2024 in #workers-help

Worker orchestration idea might be overkill

the queue could still be helpful when it comes to long delays, as i can imagine worker up-time has some restrictions and costs, but beyond that i see no point.

5 replies

CDCloudflare Developers

•Created by poro on 6/27/2024 in #workers-help

Worker orchestration idea might be overkill

yeah i've dug deeper in the docs. i'm still not convinced its the way to go for my requirements: My requests need to be handled on a caller-id basis. Meaning that all POST from foo should be batched & delayed separately from POST from bar. I don't see a clear and clean way to do that with queues. I would have to track state for each caller-id (which is ok) and set delays manually like that: await env.YOUR_QUEUE.send(message, { delaySeconds: 600 }) and finally set max_batch_size to 1 ( or max_batch_timeout to 0) which pretty much make the queue pointless.

5 replies

CDCloudflare Developers

•Created by poro on 6/27/2024 in #workers-help

Worker orchestration idea might be overkill

just ran quickly through the docs of queues. it seems to be appropriate for my timeout based batching. but if i ever need to trigger processes along an arbitrary sequence of time : 2s-10s-25s for example, im not sure it can cover it. i need to dig deeper in documentation

5 replies

CDCloudflare Developers

•Created by poro on 4/26/2024 in #general-help

nameservers changed +24hr ago. Cloudflare status still pending.

it could be that i didnt disable it before changing the nameservers.

8 replies

CDCloudflare Developers

•Created by poro on 4/26/2024 in #general-help

nameservers changed +24hr ago. Cloudflare status still pending.

oh! i see DNSSEC nowhere on their interface

8 replies

CDCloudflare Developers