DO is location bound because they are serialized and they migrate location. Look at CF examples with conceptual implementation of the rate limiters. I’d suggest to remove rate limiters for now and allow CF do the protection, or you’ll end up paying more for rate limiting than if you would have allowed the request to pass 🐶🐾🫡

Reply to this note

Please Login to reply.

Discussion

Appreciate you taking a peek! That rate-limiting is more for the websocket messages and KV ops. That way, it keeps it within the 1000/second limits of CF's API. 🤞

Makes sense, and perhaps that will help a little to do not blow over KV limits 🐶🐾🫡