MWe use KV for application configuration. Most settings rarely change, but for certain data—such as a status change from A to B—workers must see the update immediately.
TCan you elaborate on which type of your configs need changes reflected immediately? You can DM me as well if you prefer
MOur product is paid. We store each user’s overdue status in KV; if they’re overdue, we return an error. After a user pays, the status is updated in central storage and synced to KV, but workers may read a stale overdue value and still return an error. We need a way for workers to read the latest status so users can access the product immediately after payment.
MOn the KV
getWithMetadatacacheStatusCloudflare Docs
To get the value for a given key, call the get() method of the KV binding on any KV namespace you have bound to your Worker code:
PIf a 60 second TTL is too long this sounds like an eventually consistent store is the wrong product over something immediately consistent like D1 or a DO
TOur product is paid. We store each
TConfiguration of this type is something we aim to support, and we are looking into providing more controls over eventual consistency. We will have more to share in the new year
Rhey, I recently got an email that I surpassed my KV worker limit for the free tier, but when checking the usage on my dashboard they weren't showing any numbers within the metrics, is this a known bug or is there another way to see specific kv worker details?
