4 ms·
WebRTC is designed for client to client architecture. We want to use it in a dedicated server architecture. WebRTC is not designed to integrate into kubernetes.
by nightowl_games 5y ago
WebRTC is designed for client to client architecture. We want to use it in a dedicated server architecture. WebRTC is not designed to integrate into kubernetes. Ultimately, this has pushed us to stay on websockets and try to handle TCP congestion. We have theorized a network architecture that could use webrtc in our cluster, but it involves routing data out to a TURN/STUN server and back in, which would cost a lot more due to paying double for egress/ingress.
Overall, WebRTC is a poorly designed protocol which will be quickly obsoleted.
- saurik 5y agoWhat does WebRTC--or any protocol for that matter--have to do with your container solution? When I develop a protocol now, do I have to "design it to integrate into kubernetes"?! FWIW, WebRTC works great for client-to-server deployment, as using it like that means you don't have to worry at all about the oft-cited peer-to-peer NAT incompatibility issues.
- nightowl_games 5y agoThe issues that we ran into were related to the port range that WebRTC attempts to use. If I understand it correctly, WebRTC requires you to open a range of thousands of ports and kubernetes load balancers are designed to forward individual ports to individual services. https://github.com/pion/webrtc/issues/639 https://github.com/pion/webrtc/issues/639 https://github.com/pion/webrtc/wiki/Big-Ideas#single-port-mode https://github.com/pion/webrtc/wiki/Big-Ideas#single-port-mo...