Post

Rob Sutter
@robsutter.dev

We've wanted to put Quicksilver in customers' hands for a long time now, and with this release we finally have! Workers KV Instant is built on top of Quicksilver, serves reads in around 2ms at p99, and pushes writes to every Cloudflare location in about 1/4 sec. blog.cloudflare.com/workers-kv-i...

blog.cloudflare.comIntroducing Workers KV Instant — powered by QuicksilverWorkers KV Instant delivers sub-2ms p99 read latencies and 250ms global replication across Cloudflare’s 300+ edge locations. KV Instant eliminates cold-read penalties and uses the familiar Workers KV ...
PDFops
@pdfops.dev

2ms p99 is wild for something globally replicated in a quarter second. curious how it behaves under read-after-write right after the replication window, that's usually where kv-style stores show their seams.

Rob Sutter
@robsutter.dev

It is wild! Strict read after write is not guaranteed by design with KV Instant as it's not meant for transactions or application data. It's more for feature flags, circuit breakers, and other application-level config.

0 reposts1 like

PDFops
@pdfops.dev

yeah that distinction gets missed a lot. same deal with most edge kv stores, eventual consistency is fine for a flag check but people reach for it as a database and then get surprised when two regions disagree for a few hundred ms.