@syblackwell I’ve interpreted it as that reads are “eventually consistent” while writes are not written at the node but centrally. Though, I’m going to test this very soon to see how it actually performs.
What you’d want to do, if you write from a worker and the want to read the value directly - is make sure that you compare the value to the value you’ve written so you know what to expect and if it doesn’t match - retry in a few seconds (CF claim max 30 sec global consistency, usually <10 sec).
And you’d want to do this validation in the same request where you write the value…
If you validate it on a second request, you don’t have a state to hold on to (no global variable for example) because you might call a completely different node on the next request (which cannot be fixed). And neither KV or Cache is immediately consistent.
Which means that you the only way to validate the written data on the next request is by caching the value on the browser/client.