Correct, every time you write to the key and include the `expirationTtl`, it will extend the ttl. So

Correct, every time you write to the key and include the

expirationTtl

expirationTtl

expirationTtl

expirationTtl, it will extend the ttl. So if I write to a key with

expirationTtl

expirationTtl

expirationTtl

expirationTtl set to 2 hours, wait 1 hour, then write to it again with the same ttl, then the expiration will be bumped to 2 hours from now

Burrito•12/19/21, 1:54 PM

With the eventual consistency caveat of KV, does that mean it's impossible to do "append" operations with them?

BBurrito With the eventual consistency caveat of KV, does that mean it's impossible to do...

Erisa•12/19/21, 3:44 PM

Yeah, pretty much. If one worker tried to append then it may be reading stale data and then another worker in a different location also tried to append and suddenly your count is completely wrong.

For counting or appending things reliably and consistently I believe #durable-objects are best suited

Burrito•12/19/21, 3:49 PM

But durable objects are being charged for its lifetime, no?

Burrito•12/19/21, 3:50 PM

I'm thinking doing a like system similar to most social media sites (users can like a content, and users can see how many likes a content has) and I'm feeling maybe serverless is not the way to go.

Erisa•12/19/21, 4:27 PM

im gonna go ahead and repost this here, it was incorrectly flagged

Erisa•12/19/21, 4:28 PM

though half of it is still missing i think

Burrito•12/19/21, 4:41 PM

True, serverless was the wrong word there.

Burrito•12/19/21, 4:43 PM

I'm not very good at backend or infrastructural stuffs, and my project does have global presence

Burrito•12/19/21, 4:45 PM

There are DBaaS with global replications, but I'm also trying to see if I could work CF into what I need.

BBurrito I'm thinking doing a like system similar to most social media sites (users can l...

aarhus•12/19/21, 5:02 PM

You would only be charged whilst they are doing things. So, in your case, the few milliseconds needed to add or retrieve a comment. It's only when you are using we sockets that they run all of the time

Burrito•12/19/21, 5:04 PM

I wasn't aware, that changes things.

Burrito•12/19/21, 5:06 PM

What are you guys thoughts regarding this (implementing a content like system with CF KV/durable objects, instead of a database)?

Burrito•12/19/21, 5:08 PM

I figure there should be far more reads (viewing a content) than writes (liking/unliking a content) and can benefit from global fast delivery, so CF KV seems like a natural good fit.

JJunx but for live environments checkbox system would still be useful

Erwin•12/21/21, 12:35 PM

Oh yeah.. that dashboard absolutely needs some love.. it needs a search box even more than it needs checkboxes (which it also very much needs tbh)

Aazz hey people! what backend database does workers KV use? does it use something cus...

zegevlier•12/21/21, 7:42 PM

I believe it's something custom

Aazz hey people! what backend database does workers KV use? does it use something cus...

Erwin•12/21/21, 8:25 PM

It is a mix of existing and custom build logic.

Walshy•12/21/21, 10:35 PM

they're replicated between the storage servers yes

Walshy•12/21/21, 10:35 PM

But the latency around AUS/Asia can be quite high for a cold read

Walshy•12/21/21, 10:39 PM

NA/EU high yes

Walshy•12/21/21, 10:39 PM

sadly

Erwin•12/22/21, 2:21 AM

I find they are usually in the 200-300ms range, which is probably about as bad as you can get.. South America might see slightly higher ones depending on where and network quality?

Erwin•12/22/21, 2:21 AM

I am in Australia btw

Walshy•12/22/21, 2:27 AM

Blog post on all this eventually

Erwin•12/23/21, 1:55 AM

Woohoo!

WWalshy Blog post on all this eventually™️

jersey•12/23/21, 1:59 AM

don't you mean soonsoontm

Jjanat08 The details are here, help me for the love of god: https://community.cloudflare....

janat08•12/28/21, 7:25 AM

Can someone help with this

Walshy•12/28/21, 8:30 AM

The getAssetFromKV should map the asset to the hashed one.
@cherryjimbo is best to answer but I can try until he's around

What I'd recommend first is just passing in the request you're given rather than making a new one. So, getAssetFromKV({ request: req })getAssetFromKV({ request: req })

I also see in the docs for kv-asset-handler it'd also like waitUntil (though not sure why exactly) so maybe try to pass that in too.

Then unrelated, your error is trying to get the request from the request. That should just be event.urlevent.url (the naming for that request is definitely confusing so I'd maybe suggest renaming it too)

SSilence is there any supported method to access a kv from one account on another account

Hello, I’m Allie!•12/30/21, 11:13 PM

Either via API calls, or through a Worker Proxy.

SSilence ok cool so it won't be like if i try to access on same account? basically all i ...

Erwin•12/31/21, 12:43 AM

No.. hopefully it is an entirely different experience..

And if you can do that, you should totally file a HackerOne bug bounty, and it would make you quite a nice bit of cash I am sure

Erwin•12/31/21, 12:44 AM

No, I mean between different accounts. Two workers on the same account is absolutely no problem and is supposed to work

SSilence hmm i will have to look at it more. I am newish to workers

Erwin•12/31/21, 12:50 AM

No worries, we are always here to help!

SSilence oh my thought with accessing the other workers kv store was to use an api key or...

Erwin•12/31/21, 3:29 AM

Yeah, you can't do that with the native KV namespace API. But you can use the API key through the Cloudflare API at https://api.cloudflare.com

Antonio32A•1/1/22, 12:33 PM

~~I'm trying to store strings which have special unicode characters in them but the encoding doesn't seem to support them and they all turn into � (question mark) characters.~~
~~Is there anything I can do about this other than convert the string to base64?~~
~~I guess I could use encodeURI and decodeURI. That seems to work for now.~~
Nevermind, this is not an issue with KV, instead this was an issue with how I'm sending the request to my worker.

Correct, every time you write to the key and include the `expirationTtl`, it will extend the ttl. So

Similar Threads

Similar Threads

Similar Threads