Cloudflare Developers•3y ago

I guess that's true as long as my rate limiting only cares about a window of 10 seconds or less

Jjohtso I guess that's true as long as my rate limiting only cares about a window of 10 ...

DaniFoldi•3/11/23, 2:12 PM

*30, DOs stick around for 30 seconds after a request

johtsoOP•3/11/23, 2:13 PM

good to know, I think the docs say a minimum of 10s

johtsoOP•3/11/23, 2:13 PM

"In the absence of failures, in-memory state should not be reset after less than 10 seconds of inactivity."

johtsoOP•3/11/23, 2:14 PM

but I guess that's the pessimistic number

johtsoOP•3/11/23, 2:15 PM

I wonder if it's better to implement a rate limiter as a proxy or just as an api that returns whether a request should be allowed..

johtsoOP•3/11/23, 2:15 PM

I guess a proxy would be more efficient

johtsoOP•3/11/23, 2:16 PM

but probably only very marginally?

johtsoOP•3/11/23, 2:25 PM

@skye_31 hold on a minute, if I hosted my website in a DO wouldn't everyone's requests block every time I made a fetch to another DO / worker?

johtsoOP•3/11/23, 2:25 PM

or is that input output gate stuff only for storage operations?

johtsoOP•3/11/23, 2:26 PM

which I guess I can turn off with

allowConcurrency

allowConcurrency

and

allowUnconfirmed

allowUnconfirmed

johtsoOP•3/11/23, 2:26 PM

no worries

Jjohtso @skye_31 hold on a minute, if I hosted my website in a DO wouldn't everyone's re...

DaniFoldi•3/11/23, 2:30 PM

You're correct in that if the input gate is closed, no new requests will come in. The input gate is opened whenever you make an external async request, such as fetch another DO/worker - so that should open the input gate and allow other requests to be processed in the meantime.

johtsoOP•3/11/23, 2:42 PM

just trying to get my head around what the deal is if every request needed to increment a value in storage, and making the get and then put atomic

johtsoOP•3/11/23, 2:44 PM

I feel like it just works, but I'd love to understand why

johtsoOP•3/11/23, 2:44 PM

I think I just need to read the blog post 10 more times until it all clicks

johtsoOP•3/11/23, 2:47 PM

and probably do some more reading on how javascript concurrency works

johtsoOP•3/11/23, 2:51 PM

"Any other events will be deferred until such a time as the object is no longer executing JavaScript code and is no longer waiting for any storage operations"

johtsoOP•3/11/23, 2:51 PM

I think this is the bit I was missing!

johtsoOP•3/11/23, 2:53 PM

new events wont be delivered while code is executing, only when the event loop is idle

johtsoOP•3/11/23, 3:03 PM

@skye_31 another potential issue. say my DO needed to calculate some expensive hashing function when a user logs in, that would block all other requests

johtsoOP•3/11/23, 3:03 PM

where as with a worker the other requests would get handled by another instance?

Original message was deleted

johtsoOP•3/11/23, 4:09 PM

so I guess you'd just have to be extra careful to have short execution time, and defer anything that might be cpu intensive to another worker/do

johtsoOP•3/11/23, 4:23 PM

@skye_31 I guess I just liked the idea that my entry point would be colocated with my other DOs so communicating between them would be faster, and things like a rate limit check could even be stored locally to avoid an extra request for each user request

johtsoOP•3/11/23, 4:24 PM

but yeah, premature optimisation

johtsoOP•3/11/23, 4:25 PM

yeah, it did seem like you could get pretty far with that!

Original message was deleted

johtsoOP•3/11/23, 4:28 PM

the one rule limit is kind of restrictive though

johtsoOP•3/11/23, 4:30 PM

probably enough though when I think about it

johtsoOP•3/11/23, 6:08 PM

can durable objects not have cron triggers?

DaniFoldi•3/11/23, 6:12 PM