KV has really good docs on how it works: <https://developers.cloudflare.com/workers/learning/how-kv-

KV has really good docs on how it works:
https://developers.cloudflare.com/workers/learning/how-kv-works/
The Cache API doesn't have any docs like that but it is a lot simpler, just a per-colo (keeping in mind some Cloudflare PoPs have more than one colo) cache. It doesn't replicate, tiered caching/reserve cache settings don't apply to it, and it's response-based. Main upside is that the Cache API is completely free, but there's no guarantees on how long it will stick around (TTL is a "at most" not a guarantee)
KV is an actual data store, cached at every edge from two central stores (the link above explains all of that fully), and it is eventually consistent. KV has it's own internal cache once it is requested. Cloudflare Pages uses it for all of the static assets, it scales well.

CChaika KV has really good docs on how it works: <https://developers.cloudflare.com/work...

rodrigo•1/7/23, 11:09 PM

So I think I read somewhere that you don't have to worry about Cache API if we use KV ... just go with KV. Is it so? what kind of improvements could you get with Cache API over KV?
Because, what improvements does Flareutils provide? There is no doc about it.

kian•1/7/23, 11:10 PM

KV cached reads are billable

kian•1/7/23, 11:10 PM

Cache API reads aren't

CChaika KV has really good docs on how it works: <https://developers.cloudflare.com/work...

Hello, I’m Allie!•1/8/23, 10:34 AM

Basically, BetterKV does what the KV Cache does, just for free.

CChaCha Hi all, quick question, is KV reliable reading and writing to multiple times in ...

Hello, I’m Allie!•1/13/23, 9:29 AM

I would recommend coallescing writes into a single variable, and then actually pushing that write at the end. For example:

await env.KV.put("some", "val");
// ...
await env.KV.put("some", "thing");
// ...
await env.KV.put("some", "one");

await env.KV.put("some", "val");
// ...
await env.KV.put("some", "thing");
// ...
await env.KV.put("some", "one");

could be replaced with this:

let tempStore = "val";
tempStore = "thing";
// ...
tempStore = "one";
// ...
await env.KV.put("some", tempStore);

let tempStore = "val";
tempStore = "thing";
// ...
tempStore = "one";
// ...
await env.KV.put("some", tempStore);

This also saves you from paying 3 times as much for billable writes.

Hello, I’m Allie!•1/13/23, 4:41 PM

!remind 2hr kv

Flare•1/13/23, 4:41 PM

I will remind you in 2 hours at Jan 13, 2023 at 18:41 UTC

Flare•1/13/23, 6:41 PM

Reminder for @HardAtWork: kv
Set January 13, 2023

CChaCha This was closer to my use case (not exact though) Main thing is I wrote a few he...

Hello, I’m Allie!•1/13/23, 7:37 PM

You could do this to maintain the same pattern, while coalescing reads/writes:

const updates = new Map();
const update = async (key, patch) => {
  let current = updates.get(key)
  if(!current) {
    current = await env.KV.get(key, {
      type: "json"
    });
  }
  const next = { ...current, ...patch };
  updates.set(key, next);
  return next;
};
const flush = async () => {
  for(const [key, value] of updates.entries()) {
    await env.KV.put(key, JSON.stringify(value));
  }
};

const key = "event-xxx";
const event = makeEvent();

// Store initial record that event occured
await update(key, event);

// Procedure 1
const {
  complete,
  data,
  error
} = await proc1(); // (this can fail)
if (complete) {
  await update(key, data);
} else {
  throw error
};

// Procedure 2 (uses data returned from procedure 1)
const {
  complete: complete2,
  data: data2,
  error: error2
} = await proc2(data); // (this can also fail)
if (complete2) {
  await update(key, data2)
} else {
  throw error2;
}

const updates = new Map();
const update = async (key, patch) => {
  let current = updates.get(key)
  if(!current) {
    current = await env.KV.get(key, {
      type: "json"
    });
  }
  const next = { ...current, ...patch };
  updates.set(key, next);
  return next;
};
const flush = async () => {
  for(const [key, value] of updates.entries()) {
    await env.KV.put(key, JSON.stringify(value));
  }
};

const key = "event-xxx";
const event = makeEvent();

// Store initial record that event occured
await update(key, event);

// Procedure 1
const {
  complete,
  data,
  error
} = await proc1(); // (this can fail)
if (complete) {
  await update(key, data);
} else {
  throw error
};

// Procedure 2 (uses data returned from procedure 1)
const {
  complete: complete2,
  data: data2,
  error: error2
} = await proc2(data); // (this can also fail)
if (complete2) {
  await update(key, data2)
} else {
  throw error2;
}

CChaCha I like this solution a lot 🙂 Thanks 🤘

Hello, I’m Allie!•1/13/23, 9:47 PM

Happy to help!

AAlCalzone My self-rolled caching didn't actually work on CF either, just locally, so I mig...

Hello, I’m Allie!•1/16/23, 4:41 PM

It’s really weird, because it was fiddling with some unrelated systems, and got it to work, still with the fake hostname. Not 100% sure what the issue is then…

Victor•1/16/23, 7:49 PM

Is there a wrangler command for

put

put

but

--local

--local

instead of live?

FFrancis0xf Hello, I’m using kv for storing score people make in a game. should every score ...

tombyrer•1/16/23, 9:29 PM

New records would allow neat analytics; show trends in scoring, time, etc. & allow a roll-back eaiser.
But might be overkill.
You could A/B test, or just do both & see what you like better?

Kkian KV cached reads are billable

rodrigo•1/17/23, 11:11 PM

Cache API reads are not billable, but if in a same request we hit the cache multiple times (reads), will it be billable as multiple worker requests (or subrequests) ?

kian•1/17/23, 11:12 PM

Subrequests aren't billable, only limited on how many you can do per request.

kian•1/17/23, 11:12 PM

i.e free/bundled 50, unbound 1,000

VVR Architect I feel that fact should be added to the limits documentation.

Hello, I’m Allie!•1/18/23, 2:13 PM

I believe it is intended, in the sense that while you running a list is only a list op, in the dash, it is also a read, since it displays the values alongside the keys.

Hello, I’m Allie!•1/18/23, 2:13 PM

So the Docs are fine, but the Dash is weird.

IdkWhatever69•1/20/23, 2:20 PM

guys is KV reliable enough for storing account states?

IIdkWhatever69 guys is KV reliable enough for storing account states?

Isaac McFadyen•1/20/23, 3:31 PM

Reliable: yes, KV is reliable. However KV is not consistent, changes may take 60 seconds (or longer in case of failure scenarios) to sync across the world.

Isaac McFadyen•1/20/23, 3:32 PM

The second point means if you write in one location and then write in another the first write will be overwritten.

VVR Architect I feel that fact should be added to the limits documentation.

tombyrer•1/21/23, 2:34 AM

All the docs are on Github AFAIK; they take PRs.

Original message was deleted

tombyrer•1/21/23, 2:37 AM

Benefit of Astro; you can mix & match frameworks, React for 1 page, Vue for another, SolidJS, MDX, etc...

rob•1/21/23, 5:50 AM

is it ok to use KV for long storage too?

zegevlier•1/21/23, 5:55 AM

Sure. It's a bit more expensive than r2 per gb, but yea there's no reason you wouldn't be able to use it for that.

rob•1/21/23, 6:16 AM

You should also consider the data size when storing in KV, the data store has a limit of 10MB per key-value pair.

rob•1/21/23, 6:16 AM

is this still the limit on it ?

Rrob You should also consider the data size when storing in KV, the data store has a ...

zegevlier•1/21/23, 6:59 AM

It's 25mb, but yes.

zegevlier•1/21/23, 6:59 AM

Oh sorry misread your question, no the limit is 25mb.

IIsaac McFadyen Reliable: yes, KV is reliable. However KV is not consistent, changes may take 60...

IdkWhatever69•1/21/23, 8:40 AM

is the following achievable with KV?

i want to store:
data: {
  name: "Adam",
  nick: "goodDude45",
  ...otherFields
}

sometimes i want to queary data by `name` and sometimes by `nick`

i want to store:
data: {
  name: "Adam",
  nick: "goodDude45",
  ...otherFields
}

sometimes i want to queary data by `name` and sometimes by `nick`

if not i would be really grateful if you could suggest a good DB for this.
i was using mongoDB atlas up until now but read speeds are very slow ~1 sec
i desperately need a solution

zegevlier•1/21/23, 8:42 AM

Have you checked out #d1-open-alpha ? That might be exactly what you're looking for

Zzegevlier Have you checked out #d1-open-alpha ? That might be exactly what you're looking ...

IdkWhatever69•1/21/23, 9:30 AM

D1 was exactly what i needed. thanks.

IdkWhatever69•1/21/23, 9:31 AM

i did not know cloudflare had sql db

zegevlier•1/21/23, 9:32 AM

It's currently still in Alpha. If you can work with the size limit and can accept the increased latency, it's perfectly usable for hobby projects right now (imo).