Re:Notes on Zero-latency SQLite storage in every Durable Object
by tmikaeld on Monday October 14, 2024 @04:01AM
(#41835281)
You're right that reads and writes are immediate in the same client connection, this is how it works with CF KV as well - but not across the entire network.
On KV they expect up to 30 second latency before a write can be written everywhere, I expect similar here.
Re:Notes on Zero-latency SQLite storage in every Durable Object
by ec109685 on Monday October 14, 2024 @04:04AM
(#41835295)
Cloudflare ensures all operations on a DO happen on _the_ single instance of that DO, worldwide.
There’s no such thing as the read after wrote problem because only one host will ever do reads and writes (until that host dies).
Re:Notes on Zero-latency SQLite storage in every Durable Object
by dumbo-octopus on Monday October 14, 2024 @05:00AM
(#41835632)
Indeed. The entire purpose of DO’s is essentially to provide the consistency guarantees that KV cannot.
For another process (e.g. another DO or another worker) to access the data, they need to go through the DO which "contains" the data, so they'd be making a RPC or a HTTP request to the DO, and they'd get the latest information.
+ the hibernation happens after x seconds of inactivity, so it feels like the only time a data write to be unavailable as expected would be when the DO or worker crashes right after a write.