←back to thread

292 points kixelated | 1 comments | | HN request time: 0s | source
Show context
englishm ◴[] No.44988596[source]
Hi! Cloudflare MoQ dev here, happy to answer questions!

Thanks for the award, kixelated. xD

replies(6): >>44989011 #>>44989230 #>>44989615 #>>44989828 #>>44990875 #>>45005783 #
combyn8tor ◴[] No.44989828[source]
Is the load balancing of the relays out of scope? It doesn't seem to be addressed in the write up unless I missed it.
replies(2): >>44989922 #>>44990368 #
kixelated ◴[] No.44989922[source]
EDIT: Sorry I just noticed this was directed to Cloudflare. They're using the same architecture as Cloudflare Realtime, their WebRTC offering.

`relay.moq.dev` currently uses GeoDNS to route to the closest edge. I'd like to use anycast like Cloudflare (and QUIC's preferred_address), but cloud offerings for anycast + UDP are limited.

The relays nodes currently form a mesh network and gossip origins between themselves. I used to work at Twitch on the CDN team so I'd like to eventually add tiers, but it's overkill with near zero users.

The moq-relay and terraform code is all open source if you're super curious.

replies(2): >>44990267 #>>44993026 #
bushbaba ◴[] No.44993026[source]
Anycast can have serious reliability challenges. It was common at GCP for a small QPS user of anycast to have their Load Balancers nuked in a given pop as it was backed by a single machine. But BGP showed it as still the best route. The major DNS based offerings don't have such issues.
replies(2): >>44993132 #>>44993182 #
1. wbl ◴[] No.44993132{3}[source]
I work for a CDN that does DNS steering. DNS record lifetimes are nonzero and can be surprisingly long. But you do get some very fine control over where data goes if resolvers cooperate.