I have a KV namespace with values like: ``` car:golf1.4 -> {brand: VW, power:...... } car:F150

I have a KV namespace with values like:

 car:golf1.4 -> {brand: VW, power:...... } 
  car:F150   ->  {brand: Ford, power: ...}

 car:golf1.4 -> {brand: VW, power:...... } 
  car:F150   ->  {brand: Ford, power: ...}

 car:golf1.4 -> {brand: VW, power:...... } 
  car:F150   ->  {brand: Ford, power: ...}

 car:golf1.4 -> {brand: VW, power:...... } 
  car:F150   ->  {brand: Ford, power: ...}

I'd like to be able to select by brand and randomly. What's the best approach?
To use an additional KV as index

    brand:VW - >  [golf1.4, ...]  
   brand:Ford -> [F150, ...]

    brand:VW - >  [golf1.4, ...]  
   brand:Ford -> [F150, ...]

    brand:VW - >  [golf1.4, ...]  
   brand:Ford -> [F150, ...]

    brand:VW - >  [golf1.4, ...]  
   brand:Ford -> [F150, ...]

Or to insert the brand in the key and then use the

list

list

list

list method:

  car:VW:golf1.4  ->   ..
  car:Ford:F150  ->

  car:VW:golf1.4  ->   ..
  car:Ford:F150  ->

  car:VW:golf1.4  ->   ..
  car:Ford:F150  ->

  car:VW:golf1.4  ->   ..
  car:Ford:F150  ->

But this is more expensive and cannot randomize them, right?

Rrodrigo I have a KV namespace with values like: ``` car:golf1.4 -> {brand: VW, power:...

Matt Silverlock•2/2/23, 1:36 AM

You can list by prefix and then you can randomize the results on the client side fairly easily?

Rrodrigo I have a KV namespace with values like: ``` car:golf1.4 -> {brand: VW, power:...

Matt Silverlock•2/2/23, 1:37 AM

https://developers.cloudflare.com/workers/runtime-apis/kv/#listing-by-prefix

KV · Cloudflare Workers docs

Workers 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 …

Rrodrigo I have a KV namespace with values like: ``` car:golf1.4 -> {brand: VW, power:...

Matt Silverlock•2/2/23, 1:41 AM

Specifically, just choose a random integer between 0 and lengthlength of your list -> then access that array item directly.

let idx = Math.floor(Math.random() * results.keys.length)
# where results is the array returned from list()
let val = results.keys[idx]

let idx = Math.floor(Math.random() * results.keys.length)
# where results is the array returned from list()
let val = results.keys[idx]

MMatt Silverlock You can list by prefix and then you can randomize the results on the client side...

rodrigoOP•2/2/23, 11:08 AM

Ok, it makes sense.
Btw, I've checked the flareutilsflareutils library and I see there's also a

list

list

method combining cache and kv.
https://github.com/helloimalastair/flareutils/blob/0aa471d/src/BetterKV.ts#L295
But I see it uses this URL cacheKey = new URL("https://list.better.kv");cacheKey = new URL("https://list.better.kv");
Do you know what this URL is about? Am I supposed to get the same results as using the KV alone? Thx

GitHub

FlareUtils/BetterKV.ts at 0aa471d84d83ce195d4d51e074fad439fff68643 ...

Contribute to helloimalastair/FlareUtils development by creating an account on GitHub.

Rrodrigo Ok, it makes sense. Btw, I've checked the `flareutils` library and I see there's...

Hello, I’m Allie!•2/2/23, 11:11 AM

That url is just there to uniquely identify the list operation in the cache. You can call it whatever you want, as long as it is unique

James•2/3/23, 12:46 AM

You won't be able to run something like axiosaxios on Workers, which is sounds like you're trying to do

James•2/3/23, 12:47 AM

You'll need to use

fetch

fetch

for HTTP calls in Workers. But in Workers, you don't need to do that You can use a KV binding: https://developers.cloudflare.com/workers/runtime-apis/kv/#kv-bindings

KV · Cloudflare Workers docs

Workers 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 …

James•2/3/23, 12:49 AM

axiosaxios uses Node's httphttp module, which doesn't exist in Workers. Workers run JavaScript via V8, but not Node.js

James•2/3/23, 12:51 AM

I'm not sure if there's any specific literature on KV + TS, but it's all built into @cloudflare/workers-types@cloudflare/workers-types. There's a KVNamespaceKVNamespace type which you can assign to env.KV_BINDINGenv.KV_BINDING or similar, which should work well

Walshy•2/3/23, 12:53 AM

fetch

fetch

is the future anyway especially now it's in Node!

Unsmart•2/3/23, 1:11 AM

its not a default of the runtime

Walshy•2/3/23, 1:24 AM

Axios a few years ago was great, these days

fetch

fetch

is the standard within browsers and runtimes. Having that consistency is really good and it's native!

James•2/3/23, 2:31 AM

Can you provide a reproduction? A link to your repo or something and the commands you’re running would be good

James•2/3/23, 2:34 AM

Sure. It’d probably make sense to move to #workers-help to condense this all

admin_way•2/7/23, 9:09 PM

hi, it seems there is nothing returned from kv put call. how do i know put is successful ?

Walshy•2/10/23, 10:28 PM

https://developers.cloudflare.com/workers/runtime-apis/kv/#parameters

Keys have a maximum length of 512 bytes.

ZZiga Zajc Suggestion: Option to delete all keys without deleting the whole KV (in Cloudfla...

Emilio•2/13/23, 5:28 PM

There's a cost-consideration to the customer. Delete operations are capped to 1k/day for free customers, and 1mm/month + 5$/million for paid accounts. Deleting a KV namespace is ~free~.

GuillaumeLakano•2/14/23, 10:17 AM

Hi !
The documentation ( https://developers.cloudflare.com/workers/learning/how-kv-works/ ) say « Frequent reads from the same location return the cached value without reading from a central data store, resulting in faster response times. »
There is a more precise answer of what is considered « frequent reads » please?
To known if using KV for us is big mistake for performances or not

How KV works · Cloudflare Workers docs

Workers 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 …

GGuillaumeLakano Hi ! The documentation ( https://developers.cloudflare.com/workers/learning/how-...

Hello, I’m Allie!•2/14/23, 10:29 AM

Unless you mess with the CacheTTL, reads will be cached at most 60 seconds

Hello, I’m Allie!•2/14/23, 10:30 AM

Derp

DaveJ•2/17/23, 7:01 PM

Is there anything cheaper than kvkv for super simple storage on Workers? Basically, we have a boolean that we need to toggle occasionally. The server is doing 10s-100s of millions of lightweight requests per day so KV is surprisingly expensive for this use case. We end up using an environment variable and flipping that variable every time we want to change the value.

Obviously, our current solution is not ideal as it requires a re-deploy to change environment variables. Any better solutions that are a bit cheaper than kvkv?

DaveJ•2/17/23, 7:02 PM

Perhaps we could put a cache layer in front of kvkv and then we could invalidate every minute or so? Would that be a good solution?

DaveJ•2/17/23, 7:03 PM

But you could automate the task of changing it quite easily

We need to re-deploy every time we change an

env

env

right? We can't do it on the fly?

Original message was deleted

DaveJ•2/17/23, 7:06 PM

Nice! Cache is basically free right? Or, to be more correct, we just pay for the increased duration of the function.

DaveJ•2/17/23, 7:07 PM

Cool, kvkv with a cache ttl seems like the right solution. Any thing I'm missing?

DaveJ•2/17/23, 7:08 PM

Perfect. Thanks @skye_31, appreciate your help.

VVitaVee if no expiration is given when storing an object in KV, will it remain stored th...

Hello, I’m Allie!•2/19/23, 2:49 PM

Indefinitely

DDaveJ Is there anything cheaper than `kv` for super simple storage on Workers? Basical...

JustinNoel•2/20/23, 5:49 PM

Perhaps D1? I know it's in alpha. If not that, then maybe PlanetScale? Their "Scaler" plan would give you 100 billion row reads/mo.

I have a KV namespace with values like: ``` car:golf1.4 -> {brand: VW, power:...... } car:F150

Similar Threads

Similar Threads

Similar Threads