I was just curious about this behavior. Combining the two statements below, it would appear that Durable Objects can use KV with “nearly” zero latency?
I imagine there would be some race conditions introduced by mixing the two products.
Is there any documentation on this? Has anyone tried it in the wild? @gmckeon?
Changes are immediately visible in the edge location at which they’re made, but may take up to 60 seconds to propagate to all other edge locations.
Requests for a Durable Object id are routed by the Workers runtime to the Cloudflare point-of-presence that owns the Durable Object.