Cloudflare Developers•2y ago

No, both can be slow. If you are able to spawn a DO nearby, then they are pretty fast

No, both can be slow. If you are able to spawn a DO nearby, then they are pretty fast

HHello, I’m Allie!No, both **can** be slow. If you are able to spawn a DO nearby, then they are pr...

Alvee•2/10/24, 11:52 AM

can select regions no?

AAlvee can select regions no?

Hello, I’m Allie!OP•2/10/24, 11:53 AM

Yes, but you aren't guaranteed to actually spawn in said region. See https://where.durableobjects.live/region

Where Durable Objects Live

Regions | Where Durable Objects Live

Tracking where Durable Objects are created, wherever you are in the world.

HHello, I’m Allie!No, both **can** be slow. If you are able to spawn a DO nearby, then they are pr...

Alvee•2/10/24, 12:05 PM

but it's faster then traditionals databse right? like planetscale

Alvee•2/10/24, 12:06 PM

normal was going to use that to store but my db will be blown I feel like

Alvee•2/10/24, 12:08 PM

hmm in memory or transactional

AAlvee but it's faster then traditionals databse right? like planetscale

Hello, I’m Allie!OP•2/10/24, 12:11 PM

In terms of raw query speed(for key value stuff), probably. But again, speed from Worker to response is all about where it spawns

Hello, I’m Allie!OP•2/10/24, 12:12 PM

As for the state, I would recommend using the Transactional Storage API, as In-Memory state is not guaranteed to persist between requests

Hurby•2/12/24, 12:55 PM

export const createSession = async (user: any, databaseConfig: KVNamespace) => {
    let absoluteExpiration = 30 * 24 * 60 * 60;
    let expiration = new TimeSpan(10, 'd');
    const sid = generateRandomString(60, alphabet('a-z', '0-9'));

    const SessionBody = {
        email: user.email,
        email_verified: user.email_verified,
        expires_at: expiration,
    };
    try {
        await databaseConfig.put(sid, user.id, { metadata: SessionBody, expirationTtl: absoluteExpiration });
    } catch (error) {
        throw new Error('Error creating session');
    }

    return sid;
};

export const createSession = async (user: any, databaseConfig: KVNamespace) => {
    let absoluteExpiration = 30 * 24 * 60 * 60;
    let expiration = new TimeSpan(10, 'd');
    const sid = generateRandomString(60, alphabet('a-z', '0-9'));

    const SessionBody = {
        email: user.email,
        email_verified: user.email_verified,
        expires_at: expiration,
    };
    try {
        await databaseConfig.put(sid, user.id, { metadata: SessionBody, expirationTtl: absoluteExpiration });
    } catch (error) {
        throw new Error('Error creating session');
    }

    return sid;
};

Why does value appear as "undefined" in the kv? Also, when I try to get with metadata, it returns null for it.

HHurby ```ts export const createSession = async (user: any, databaseConfig: KVNamespace...

Hello, I’m Allie!OP•2/12/24, 1:02 PM

Can you log

user

user

and see what it sows?

HHello, I’m Allie!Can you log `user` and see what it sows?

Hurby•2/12/24, 1:06 PM

HHurby Click to see attachment

Hello, I’m Allie!OP•2/12/24, 1:07 PM

That looks like the issue. The Value you are putting is

user.id

user.id

, and

[ Object ].id

[ Object ].id

undefined

undefined

HHello, I’m Allie!That looks like the issue. The Value you are putting is `user.id`, and `[ Object...

Hurby•2/12/24, 1:07 PM

it seems like yea, I will try to fix it

Hurby•2/12/24, 1:07 PM

Paul Shriner•2/13/24, 1:48 PM

Unable to access KV value from a TypeScript.

I have been spinning my wheels on this for a couple of days. I have a Worker (Auth) running Typescript and I reference a linked module.

import { GetGuid, CheckAuth } from '../../util/Util';

import { GetGuid, CheckAuth } from '../../util/Util';

When I call CheckAuth (and pass in the "env" variable, I can see the KV Namespaces, but when I attempt to get a value from the namespace, it just fails silently and moves on.

export async function CheckAuth(env, walletID){
    console.log(walletID)
    console.log(env.SESSION.get)
    try{
        const sid = await env.SESSION.get(walletID)
        console.log(sid)
    }
    catch(ex){
        console.log(ex)
    }
    console.log("SID")
}

export async function CheckAuth(env, walletID){
    console.log(walletID)
    console.log(env.SESSION.get)
    try{
        const sid = await env.SESSION.get(walletID)
        console.log(sid)
    }
    catch(ex){
        console.log(ex)
    }
    console.log("SID")
}

What am I doing wrong?

PPaul Shriner Unable to access KV value from a TypeScript. I have been spinning my wheels on ...

Matt Silverlock•2/13/24, 9:23 PM

* Does

console.log(env)

console.log(env)

output anything? It should be a map of your bindings.
* What type is

walletID

walletID

- ?
* Are you doing this locally in dev? With a deployed Worker? Is it possible you're writing locally and trying to fetch a result from production?

MMatt Silverlock * Does `console.log(env)` output anything? It should be a map of your bindings. ...

Paul Shriner•2/14/24, 2:28 PM

console.log(env)

console.log(env)

outputs exactly what you woudl think, a map of the bindings.
* walletID is any, but in fact a string.
* This is in a deployed worker, I don't do anything local on the project to keep it simple.

PPaul Shriner * ```console.log(env)``` outputs exactly what you woudl think, a map of the bind...

Matt Silverlock•2/14/24, 3:33 PM

Got it. Are you positive the keys are the same? Can you write a minimal example — in a

fetch

fetch

handler without any wrapper functions.

It's likely

.get

.get

is "failing" silently because it's just returning

null

null

MMatt Silverlock Got it. Are you positive the keys are the same? Can you write a minimal example ...

Paul Shriner•2/14/24, 3:35 PM

When I make the exact same call from the worker itself, i can get the value from key. I am using the the itty-router-openapi as well, that is probably also important information.

PPaul Shriner When I make the exact same call from the worker itself, i can get the value from...

Matt Silverlock•2/14/24, 3:38 PM

Yeah, I can't speak to

itty-router-openapi

itty-router-openapi

and what's happening there. If

env

env

is logging the bindings within that function then

get

get

should work, as it's a method on the binding type.

MMatt Silverlock Yeah, I can't speak to `itty-router-openapi` and what's happening there. If `env...

Paul Shriner•2/14/24, 3:45 PM

Yeah, that is the confusing part. Thanks for your help.

Befus•2/15/24, 9:33 PM

Hey, I was wondering we have a good amount of KV's with a lot of data inside of them on a specific account, would it be possible to move this to a different account with the data? By contact support, etc?
It would be a tedious process of making a scraper that fetches all the data and then makes it again on the new account

BBefus Hey, I was wondering we have a good amount of KV's with a lot of data inside of ...

Matt Silverlock•2/16/24, 11:23 AM

If you are an enterprise customer open a ticket (this doesn’t mean we can do it, this just isn’t the forum to do it). Otherwise we don’t move data across accounts as a policy as it is non-trivial and likely to break things downstream.

MMatt Silverlock If you are an enterprise customer open a ticket (this doesn’t mean we can do it,...

Befus•2/16/24, 12:12 PM

Currently not an enterprise customer, would you still recommend opening a ticket?

BBefus Currently not an enterprise customer, would you still recommend opening a ticket...

Matt Silverlock•2/16/24, 2:00 PM

Yes. We can at least take a look. Just setting expectations here though

Ɽ

ⱤØ₥₳₦•2/17/24, 4:40 AM

Is kv just like d1? Or like worker?

Ɽ

ⱤØ₥₳₦•2/17/24, 4:41 AM

And how long would it take to propagate key values throughout the globe?

kian•2/17/24, 4:45 AM

It doesn't do propagation, it's pull-based caching with a 60 second minimum.

Kkian It doesn't do propagation, it's pull-based caching with a 60 second minimum.

Ɽ

ⱤØ₥₳₦•2/17/24, 4:48 AM

What does that mean? Where KV data gets stored?

Unsmart•2/17/24, 4:48 AM

Well it does and doesnt. Theres 2 locations of KV 1 US 1 EU data will be replicated to both but then its pull based after that

UUnsmart Well it does and doesnt. Theres 2 locations of KV 1 US 1 EU data will be replica...

Ɽ

ⱤØ₥₳₦•2/17/24, 4:49 AM

kian•2/17/24, 4:50 AM

https://developers.cloudflare.com/kv/reference/how-kv-works/

UUnsmart Well it does and doesnt. Theres 2 locations of KV 1 US 1 EU data will be replica...

Ɽ

ⱤØ₥₳₦•2/17/24, 4:52 AM

So can't use it for global production traffic

Unsmart•2/17/24, 4:53 AM

Um, you can?

UUnsmart Um, you can?

Ɽ

ⱤØ₥₳₦•2/17/24, 4:54 AM

Ɽ

ⱤØ₥₳₦•2/17/24, 4:59 AM

Ɽ

ⱤØ₥₳₦•2/17/24, 4:59 AM

the second screenshot is for firebase, holy cow, KV is 100x faster than firestore

Rronan(wighawag)Hey got a question on KV eventual consistency Does it means that if I make mult...

Hello, I’m Allie!OP•2/18/24, 12:28 PM

Yes, depending on how fast updates are pushed to the Core datacenters.

Hello, I’m Allie!OP•2/18/24, 12:29 PM

So like, if one datacenter that is farther away from core writes before one that is closer, the one that is farther away may overwrite it

Rronan(wighawag)ok, so timestamp at the edge is not considered and there is indeed the possibili...

Hello, I’m Allie!OP•2/18/24, 12:47 PM

Yes. If you need consistenly ordered writes, then I would recommend running them through a single Durable Object

flof.fly•2/18/24, 6:04 PM

Hi, does KV have ttl expiration on fields? Or key-value fields can stay there for-ever?

Santosh•2/20/24, 10:25 PM

@Marshall No I didnt, I created smaller objects and stored them in KV. And it made the problem go away.

Santosh•2/20/24, 10:28 PM

Now, I havent observed if tissue happens with second or subsequent update. And we definitely need another format, not Json alone, heres is my reason: With the overall envelope, it was about may be 8 to 10 levels deep. Once I broke it into smaller chunks, the Json depth is probably cut down by about 4. I just couldn't fathom(nor have the time) to see the depth is an issue, or the over all size is. And I wasn't anywhere close to KV limitation at all. I do have a DO that wakes up every 5 mins and refreshes it so the UI always has a certain dataset available, so it is quite possible that things are twisted making it even more difficult to find the root cause

Santosh•2/20/24, 10:32 PM

I concur that the input to KV when it is placed is perfectly fine. Reading back is the issue, but again if I cant read, the whole thing is useless

export const createSession = async (user: any, databaseConfig: KVNamespace) => { let absoluteExpiration = 30 * 24 * 60 * 60; let expiration = new TimeSpan(10, 'd'); const sid = generateRandomString(60, alphabet('a-z', '0-9')); const SessionBody = { email: user.email, email_verified: user.email_verified, expires_at: expiration, }; try { await databaseConfig.put(sid, user.id, { metadata: SessionBody, expirationTtl: absoluteExpiration }); } catch (error) { throw new Error('Error creating session'); } return sid; };

export async function CheckAuth(env, walletID){ console.log(walletID) console.log(env.SESSION.get) try{ const sid = await env.SESSION.get(walletID) console.log(sid) } catch(ex){ console.log(ex) } console.log("SID") }

No, both **can** be slow. If you are able to spawn a DO nearby, then they are pretty fast

Similar Threads

No, both can be slow. If you are able to spawn a DO nearby, then they are pretty fast