3 ms·
This is an excellent initiative, thank you for building it! Signalling for me has always been handled on a cheap box in some specific AWS regions. The tricky t
by starwatch 4y ago
This is an excellent initiative, thank you for building it!
Signalling for me has always been handled on a cheap box in some specific AWS regions. The tricky thing was that there was always more latency than I'd like in the initial establishment of the connection. Reducing that latency always played second fiddle to other issues. CF workers is an elegant solution as all signalling would be handled at the edge.
I'm looking forward to taking this for a spin!
- gfodor 4y agoSure thing, glad you like it!
- tyingq 4y agoI'm not sure if this would be lower latency, since it depends on the R2 service, which seems to be centralized. I suspect this didn't use the distributed KV store since the free plan limits are much lower than R2.
- gfodor 4y agoThe issue with KV is the write propagation delays across nodes can be up to 10s, so for a back and forth like this that needs to happen quickly it doesn’t work. My original version supported KV but I dropped it because it often failed to connect due to these delays.
- tyingq 4y agoAh. There's also "durable objects", which route requests to the kv POP where it was created, so no propogating, but they can only hold 32kb.
- gfodor 4y agoAh yep. I guess you could do http polling with a durable object - would have to do the math to see if that had lower expected costs. Websocket are prohibitively expensive.