Does it make sense to use cloudflare worker kv statestore for r2 uploads

[rverma-dev]

The examples only demonstrate usage of cloudflare kv state store for b2. Wondering whether we could get benefitted with using worker KV state store or the default worker cache is sufficient?

[Klowner]

The short answer is no, I would recommend using @tussle/state-memory-ttl with Cloudflare/R2.

I'll happily provide a long answer when I'm at my computer.

[Klowner]

The long answer:

• Workers KV is described as "low-latency" while R2 offers strong consistency guarantees.
• @tussle/storage-r2 requires a state provider to operate, but if an upload is absent from the attached state provider, the R2 storage adapter will reconstruct state from R2 on-demand (assuming the upload chunks are in the bucket) and write the rebuilt state back into the attached state service to accelerate subsequent read operations and minimize R2 API calls.

So with that in mind: using a transient in-memory state store with R2 means upload state and data are stored in a single point of truth (good!), and that point of truth has global strong consistency guarantees (also good!).