low-latency batch reads (eg. HMGET) would be a requirement
low-latency batch reads (eg. HMGET) would be a requirement
Mfast global replication also a must, i remember a couple of years ago reading that KV was up to 30 seconds, but there was a performance release a few months ago right?
Moh boyo, that 30 seconds is now 60 seconds :\
Mwhat is cloudflare kv used for? I thought it was intended to be a redis-like db, but the performance profile is too detached from what redis offers
IIt's always been 60 seconds except for a short time during a rollout that ended up being rolled back.
IKV is primarily designed for read-heavy workloads that rarely write.
IFor example, KV backs Cloudflare Pages and Workers Assets, where you deploy a site infrequently but people access often and quickly.
IKV caches at your nearest colo (that's why the 60 second limit), and future reads during the time it's cached will be very low-latency.
Cworth keeping in mind along with what Isaac said, KV doesn't replicate as much as it does cache: https://developers.cloudflare.com/kv/concepts/how-kv-works/
Two Central stores, US and EU, all the colos/data reads are behind cache and cacheTtl. It's not actively pushing, they're pulling
Two Central stores, US and EU, all the colos/data reads are behind cache and cacheTtl. It's not actively pushing, they're pulling
Cloudflare Docs
KV is a global, low-latency, key-value data store. It stores data in a small number of centralized data centers, then caches that data in Cloudflare's data centers after access.
NWhich is faster and has lower latency for random reads/writes: KV or D1?
ILikely KV because it's cached much more heavily than d1 (D1 is single-location), but updates may take up to 60s to be visible globally.
OI racked up 700K (free plan) delete operations testing worst case cleanup operations, then 1.27M with a paid plan.
The paid plan includes 1M deletes, so will I be charged fractionally for 270k deletes? Or rounded up to $5?
The paid plan includes 1M deletes, so will I be charged fractionally for 270k deletes? Or rounded up to $5?
Fhey Devs! I am bit confused with KV- encryption. The doc's are pretty clear data are encrypted on rest and transit. But when sending a new entry via Wrangler the value can be read and editetd without any encryption in the dashboard? I am planing to store API keys in KV so a encryption is necessary. I am pretty sure i am missing something?
WYeah, it's encrypted when stored and during transit. However, users should still be able to see their data so it's unencrypted before it's given back to you
I'd recommend encrypting yourself if you want to better control when the values are visible to you.
I'd recommend encrypting yourself if you want to better control when the values are visible to you.
Fthank you! I will do so 
SWe're experiencing consistently high latency (~1000ms) when using the Cloudflare KV REST API for basic key-value operations in our authentication flow. This seems excessive compared to the expected performance of KV storage.
Our implementation uses standard API calls following your documentation:
Our implementation uses standard API calls following your documentation:
- GET/PUT to
https://api.cloudflare.com/client/v4/accounts/{account_id}/storage/kv/namespaces/{namespace_id}/values/{key} - Authentication via X-Auth-Email and X-Auth-Key headers
- Small data payloads (<2KB)
IRest API latency is fairly expected because the REST API is located in a few core locations and all requests must travel through those locations before hitting the end service.
IIn the case of KV, a lot of the benefits come because of the caching done at the edge colos where the data is retrieved from, which doesn't happen with the REST API either iirc
IYour best bet might be creating a Worker that uses the KV binding (even if it's a single Worker that just services a similar API as the REST API does)
SWhat's the most efficient way to access Cloudflare KV from a Python backend application?
HWrite a Worker that implements an API for you to call
SThanks. Let me check.
O1febbc2176164bb28d7cd90ab661e862edit: the only fix was recreating the namespace
O
Chey everyone, I have a nextjs app that is a worker. I also have a binding for KV ready. How can I use it directly with binding in the app? KV store in NextJs App I decribed it in more details here
ZI don't think it's possible to do that. If your worker only does KV reads/writes, perhaps turning off the routes there could be a solution?
ZIf your worker does more, I don't really have a good solution for you :/
1Put auth on the Worker so a bad actor can't access it?
1Per user rate limiting of some kind then perhaps
1What do you mean? You said you wanted to avoid KV reads
Something like this depending on how much effort you want to go to: https://developers.cloudflare.com/durable-objects/examples/build-a-rate-limiter/
Something like this depending on how much effort you want to go to: https://developers.cloudflare.com/durable-objects/examples/build-a-rate-limiter/
1Then you'd need to implement something client-side, which doesn't render my suggestion useless, just wouldn't be using Workers to do so
1:bye:
BICMP doesn't invoke your worker if that's what you're implying
BI figured as much, was a just-in-case
1How is your site hosted, on CF with Workers/Pages? What is the KV storing, and how is the client-side accessing it?
1Sounds like you need to host the site on Static Assets which would be free unlimited requests if you are serving static HTML files
1Could you store in D1 for way more reads?
1What is the data on the pages?
