T(Creating a thread to make the discussion easier to track across other messages).
That's helpful. Can you share you namespace ID?
That's helpful. Can you share you namespace ID?
TSend it via DM
TI don't think so, I'll verify, but for now DM should work (ie no one can access your namespace even if they have the id)
TAs in an IP address that is being reused by other Heroku dynos/droplets?
TPerhaps, can you share the full log of an error?
TIs it error code 429?
TYes, confirming this is rate limiting that is applied at the Cloudflare REST API level (this is not specific to KV). The shared IP hypothesis would make sense. Have you considered spinning up a simple Worker that provides the same REST API as what you would need?
TYou could bake in some type of secret to ensure only you have access.
TThat's obviously not a great solution, and we're working to remove all products from this general shared REST API and rate limits, but this would be an immediate solution
TIf you can provide more context around what you're trying to do, there might be a more straightforward approach. But I was thinking of creating a Worker that accepts a list of keys (up to 1000), and does 1000 parallel individual .get(), and returns the result
TFrom Heroku (where you presumably have some way of knowing what the content of those keys) and then reading from a Worker?
TI think that's a good plan
And like I said, long term, we're looking to provide per product instance limits that wouldn't be affected by IP address reusing on Heroku
And like I said, long term, we're looking to provide per product instance limits that wouldn't be affected by IP address reusing on Heroku
TExcellent, happy to hear that, you too!
