How does instant rollback work on Pages if the whole thing is backed by KV?
How does instant rollback work on Pages if the whole thing is backed by KV?
MEverything is versioned.
Dif my understanding is correct, it doesn't replace the assets, but rather the mapping between paths and KV entries, so an entry is only ever written to once
Vi see, my question was more about the latency / cache invalidation part, which I still don't really understand. Is there another database used for the mappings and if no how can kv instantly serve the old mappings?
KIt's unrelated to KV, really.
KIt's just how Pages has used KV - they have a mapping of
filename => asset and they can just update that mapping, since the old files are there for handling assets that no-longer exist in a new deployment (i.e users have a cached index.html pointing to an old JS bundle) and then the rollbacks just use an older deployment mapping.
Cwhy not a todo app? 
Cthat's how caching work, u need the exact key to get the latest value.
Cby
GET /todos you mean get list by prefix?CLet
/todos/[username] hold keys to all todos of username then there'll be no last minute delay.
USo for a todos app I assume you are using the list op to list all todos for a user? If so yeah that will have delay because each list op will be cached meaning it will take 60s for cache to expire and the list op to have the new item. Durable objects are a great durable KV store... I always default to using durable objects over KV because its just infinitely better tbh
UAfaik no you would need to know all of the keys so you have to list
CI already told u
CKV is very good if u can exploit it.
UWhenever you write to KV it does update the local datacenter cache so if your user always hits one datacenter it could be fine... but if the local cache fails on the write or if they bounce between dcs then you would have problems yeah
Urealistically its going to be impossible to guarantee you dont have either cache delay or writes that collide with something else on KV so DOs should be used
UDOs are also cheaper and can be faster if the datacenter the user hits is capable of running DOs 
C/todos/[username]/[timestamp]CcookiesUthen you'd be restricting your user to one device
Cthe point is, KV although seem very basic just key/value but its usage is unlimited and depends on your imagination.
UI mean KV is a very basic key/value thats kinda the point of it 
