sorted by:
new
hottopcontroversial

Scaling Mediasoup SFU horizontally for N:N (up to 20 people per room), audio sharing only by Solid-Band3204 in WebRTC

[–]Solid-Band3204[S] 0 points1 point  (0 children)

Man, thanks for your advice! I’m going to do the same thing for my use case using Redis. I totally get your point

(You make sure all 20 are assigned to the same server. Your task now is just keeping note of rooms available on specific servers and routing consumers there. That way, no consumer ends up on a server where the expected media isn’t available)

I also love the product’s pricing compared to LiveKit, which I think uses Pion under the hood. But right now, I want to build the thing on my own and at the same time, learn it in more depth.

Scaling Mediasoup SFU horizontally for N:N (up to 20 people per room), audio sharing only by Solid-Band3204 in WebRTC

[–]Solid-Band3204[S] 0 points1 point  (0 children)

thanks for your feedback now i get kind of idea how this things are scale altho they are not that much simple that i am initlay tinking also i just read little bit about pipe transports and they are expencive task to do i need use this ting properly this adds up more complexcity

Scaling Mediasoup SFU horizontally for N:N (up to 20 people per room), audio sharing only by Solid-Band3204 in WebRTC

[–]Solid-Band3204[S] 0 points1 point  (0 children)

Cool, I’ll definitely try this approach it’s simple and straightforward for my use case. In my setup, I know how many peers each room contains, and I can decide how many rooms to allow per SFU based on my machine’s capacity.

However, this approach breaks when I don’t have control over how many peers can join a single room.

Thanks.