Durable Objects aren't just durable, the...
I just read: https://blog.cloudflare.com/how-we-built-cloudflare-queues/
Also the part "Workers KV acts as a fast metadata store: our Worker can quickly look up the shard map to perform load balancing across shards"
How can they use KV for that, as KV has a 60 second delay to update after writing? Won't the entire infrastructure have a 60 second delay to understand what the state is and how would the be able to update that state?
Also the part "Workers KV acts as a fast metadata store: our Worker can quickly look up the shard map to perform load balancing across shards"
How can they use KV for that, as KV has a 60 second delay to update after writing? Won't the entire infrastructure have a 60 second delay to understand what the state is and how would the be able to update that state?
The Cloudflare Blog
Learn how we built Cloudflare Queues using our own Developer Platform and how it evolved to a geographically-distributed, horizontally-scalable architecture built on Durable Objects. Our new architecture supports over 10x more throughput and over 3x lower latency compared to the previous version.
