Comments on: WebRTC Flow: How Media and Signaling flows look like https://bloggeek.me/media-signaling-flows-look-like-webrtc/ The leading authority on WebRTC Tue, 29 Nov 2022 14:21:32 +0000 hourly 1 By: Tsahi Levent-Levi https://bloggeek.me/media-signaling-flows-look-like-webrtc/#comment-118632 Mon, 19 Sep 2016 20:02:03 +0000 https://bloggeek.me/?p=10538#comment-118632 In reply to Aswath Rao.

Aswath,

That’s a good question with many answers:

* Not co-locating works best if you want to keep each process/box do as little as possible (microservices)
* It also enables you to scale them separately, as they might not need to take the same loads
* You might want to deploy TURN closer to the users to improve latency and quality
* The media server may be optional and relevant only to some of the sessions in your service, so the TURN servers will be used for other scenarios as well

At the end of the day, the idea is to decide on the architecture based on the exact needs of the use case.

]]> By: Aswath Rao https://bloggeek.me/media-signaling-flows-look-like-webrtc/#comment-118631 Mon, 19 Sep 2016 19:50:49 +0000 https://bloggeek.me/?p=10538#comment-118631 For #5/#7, couldn’t the media server include “TURN/TCP” & “TURN/TLS” connect info as ICE candidates and be ready to accept media traffic at theose end-points? Why go through an external TURN server or incorporate TURN functions?

]]>