Scalability and PipeTransport

Honeyside · November 23, 2020, 12:49am

Hello everyone!

Let me start by telling you that I LOVE mediasoup. Thank you for making this library available!

I am trying to create a scalable solution that will pipe between different routers on different hosts. I have my own signaling and I think I understand everything, but would like confirmation before moving forward with the development, just to be sure that I won’t waste effort.

In my understanding:

Host 1 has a router1.
Core app tells host 2 to prepare to receive incoming stream, router2 is created.
Both router1 and router2 create a PipeTransport.
The two hosts exchange their PipeTransports.
Hosts connect to each other.
Now they can consume and produce.

Is this correct?

ibc · November 23, 2020, 10:39am

Yes, exactly the same flow as when things happen in the same host (in this case no network signaling is needed obviously):

github.com

versatica/mediasoup/blob/v3/src/Router.ts#L683


		// Emit observer event.
		this._observer.safeEmit('newtransport', transport);
		return transport;
	}
	/**
	 * Pipes the given Producer or DataProducer into another Router in same host.
	 */
	async pipeToRouter(
		{
			producerId,
			dataProducerId,
			router,
			listenIp = '127.0.0.1',
			enableSctp = true,
			numSctpStreams = { OS: 1024, MIS: 1024 },
			enableRtx = false,
			enableSrtp = false
		}: PipeToRouterOptions

Topic		Replies	Views
$$$ for a snippet of code for horizontal scaling using pipeTransports Job Opportunities 💰	8	1263	June 22, 2021
Anyone done server-to-server router pipe impl yet? mediasoup libraries	3	657	July 9, 2020
[ router.pipeToRouter ] no rtp packets in consumer when trying to do something like router.pipeToRouter did using pipeTransports mediasoup libraries	4	685	February 8, 2022
PipeTransport Clarification mediasoup libraries	8	814	November 9, 2022
createPipeTransport on diffrent nodes mediasoup libraries	2	693	July 5, 2021

Scalability and PipeTransport

Related topics