Hacker News Reader

Deno KV has a maximum record size of 64Kib [1] which is pretty severe. Compare with 25Mib for Cloudflare Worker KV [2]. It can be worked around, but it will make your design more complex if you have potentially large textareas, let alone images. Hopefully it will be raised by the time Deno KV gets out of beta.

[1] https://deno.land/api@v1.43.2?s=Deno.Kv

[2] https://developers.cloudflare.com/kv/platform/limits/

View on HN

I big issue with Cloudflare KV (and Workers too) is that values do not persist at the edge. They are copied on demand much like a CDN and then expired after some time. This works great when you have a ton of traffic but sucks when you want consistent good performance with erratic traffic.

I wish CF had a premium tier where both Workers and KV would persist the the edge.

Durable Objects persist at the edge.

so when you make a change it's replicated to all regions?

No. A DO only exists in a single edge location. That's the entire point of Durable Objects.

D1 will replicate soon, but doesn't do so yet. My understanding is that it will replicate to ~5 locations and keep these locations fresh.

It's weird because all their marketing says it's distributed but it's not really

Distributed for thee but not for me

* An edge,

Reply on news.ycombinator.com