KV is eventually consistent so I'm not too sure it fits your use-case
KV is eventually consistent so I'm not too sure it fits your use-case
KWrites take some time to propagate, reads are cached, etc
Lhmm. good point.
D#durable-objects are much more suited for that - with KV the best you could do (not recommended) is to write a key on each request, and then list them 1000 at a time to count (again, not recommended, not scalable, just a way to abuse KV into what you want)
Lcool! will look into this
Lthanks @Dani Foldi @kian ! 
Lhmm are there any replication guarantees? like writes are replicated in the same order?
Llike if i find the key i’m looking for, every key i’ve written before will appear in a kv prefix scan
HThere is not
IAre you thinking of saving each sequence to a KV key?
IOk, so a read-heavy kind of design is perfect for KV (as long as the value is <25MiB, which seems the case here).
IYou'd need to be ok with a short propagation delay once the sequence updates.
IOk, then a single store makes sense.
IA Worker is better the smaller it is, even though the script is limited to 10MB so it would be fine, keeping it under 1MB would be ideal.
IDo note you are limited to 50 (or 1000 in Unbound) fetches per request, so 7500 wouldn't even work.
IA single KV key would be the way I'd go, personally.
IR2 might work, too, but it's slower on average and it requires more processing. D1 is not yet GA, but also costs per data processed.
IDOs are not worth it here.
MHi all 
does KV have something like Redis LRANGE?
does KV have something like Redis LRANGE?Mactually DO's look amazing for this use case. will give that a try
Lbut would fetching specific keys force replication?
UWrites are replicated when you write and its just a last writer wins and if there happens to be a mismatch between the data sometimes the read can push through a replication fix where it chooses one. But you are also only supposed to write once per second to a specific key so if your use case involves higher write throughput than that you probably should not be using KV.
TCould someone confirm that the dashboard numbers (operations) are for the last 24 hours but the limits are counted from 0:00 UTC?
Thanks
Thanks
TAnd if true, do we have anyway to know what have been used during the last period(s) / 0:00 - 23:59 UTC?
MIs there any way to bulk fetch KV values in a single request from a worker?
CYou should be able to use the GraphQL API to get that data
Li'm actually only writing once per key, but every now and then I'll need to write N things and a summary of what those N things are, like this:
Lwhat I still need to try is if the following read pattern will force replication of all the entries in the summary:
LIn the docs I also saw this:
but i'm not sure how this would look like in code?
One pattern is to send all of your writes for a given KV key through a corresponding instance of a Durable Object
but i'm not sure how this would look like in code?
Lyes
Limmutable as well
Lso there may be subsequent rquests to
summary:1 but it will never change once its writtenL(same for
entry:1, 2, 3, etc)Lcool!
Lwill give this a shot soon
Lthanks @skye_31!
JI made a VSCode extension to interface with KV right from VSCode that y'all might like. Has some benefits over the web UI like the a single uniform interface for Local, Preview, and Production environments, and the ability to view and edit metadata and expiration times. Anyways, it's free. https://marketplace.visualstudio.com/items?itemName=jaaxxx.cloudflare-vscode-devtools
Extension for Visual Studio Code - Interface with Cloudflare products (for now just KV, more to come?)
KR2 implements the S3 API to allow users and their applications to migrate with ease. When comparing to AWS S3, Cloudflare has removed some API …
JNo it's shelling out to the CLI. The latest versions of wrangler allow the
--local flag.JYou can always access KV via the HTTP API, that's what wrangler does.
KUThe KV dash really needs some love 
Its extremely slow to load because it tries to fetch all the values on a page and theres no batch get (I think showing metadata and giving an option to view value is better tbh). It also never shows all the values because a few of the keys always error out
Also really annoying when you want to try and delete some of the values because it reloads the view (but doesnt even get the next page its just the same values minues the deleted one). Would also be really nice if we could select multiple keys that we want to delete in one go.
Its extremely slow to load because it tries to fetch all the values on a page and theres no batch get (I think showing metadata and giving an option to view value is better tbh). It also never shows all the values because a few of the keys always error out
Also really annoying when you want to try and delete some of the values because it reloads the view (but doesnt even get the next page its just the same values minues the deleted one). Would also be really nice if we could select multiple keys that we want to delete in one go.
Ait appears that metadata is already sent to the browser, its just not displayed 
UI'm aware... im saying it should display the metadata instead of running 30 gets that are slow to return