You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- All components are containerized with Docker and will be orchestrated with Kubernets.
34
+
- Horizontal scaling is supported based on GPU availability and number of concurrent WebSocket clients.
35
+
- Logging and monitoring are provided through Prometheus and Grafana integrations.
36
+
37
+
### Design Rationale
38
+
39
+
The choice of WebSocket for metadata streaming ensures low-latency, browser-native communication [1] without the complexity of WebRTC DataChannels, which are faster in general but much harder to deal with in (future) cloud environments like Kubernetes, since it uses UDP Peer-to-Peer connections [2][3]. Load balancing in this case is also not trivial [4].
40
+
41
+
### References
42
+
43
+
1. Ably, "WebSockets explained: What they are and how they work", [link](https://ably.com/topic/websockets)
44
+
45
+
2. VideoSDK, "WebSockets vs WebRTC: Key Differences and Best Use Cases Explained", [link](https://www.videosdk.live/developer-hub/developer-hub/webrtc/websockets-vs-webrtc-differences)
46
+
47
+
3. Medium, "Kubernetes: The next step for WebRTC", [link](https://medium.com/l7mp-technologies/kubernetes-the-next-step-for-webrtc-fb8d8a33f24e)
0 commit comments