Between DNS, WireGuard, and http/3 our workloads are overwhelmingly UDP. But our scale isn’t earth shattering to matter much.
Pinning traffic to VMs does help. I just hope all edge servers don’t send traffic to the same VM. It would be cool for edge to distribute the load as in a consistent-hashing / maglev-hashing scheme. Some day…
-
Still: We could impl such a router in our VMs to steer traffic as we please via fly’s 6pn, hashing on client’s ip-port, say. But: Is the assumption that edge servers preserve client ip-port when forwarding packets, true?
-
Do gossip over 6pn within the same region count towards egress bandwidth?