3 ms·
Are you planning on releasing any of the architectural details behind this service? If you’re truly replicating to every PoP that’s quite a fan-out and I can s
by ryanworl 8y ago
Are you planning on releasing any of the architectural details behind this service?
If you’re truly replicating to every PoP that’s quite a fan-out and I can see why you’re limited to 1 write per second per key!
- jgrahamc 8y agoYes, we will. This is something we built internally and we'll talk about architecture at some point.
- Serow225 8y agoThank you! Lots of super cool stuff coming out of CF these days, the pace is hard to keep up! Not that it's a bad thing necessarily :)
- kentonv 8y agoOne interesting implementation detail is that this product is itself implemented as a worker. We're finding that the Workers platform is the easiest way to build first-party Cloudflare features.
- zhobbs 8y agoI was wondering if it is lazily replicated to PoPs via KV gets. Would be interested in clarification on that though.
- kentonv 8y agoAt present, yes, lazy propagation. But we're also exploring ways to do proactive propagation where desirable.