Room Scaling and End-to-End encryption

[Nicholas Clark]

We are currently evaluating Medooze and MediaSoup for our project. We really like the architecture, scalability, and great support that MediaSoup has, but it doesn't yet have true E2EE. 

We have been looking at Medooze, which seem to be quite similar, but we had some questions:

1. Are we able to pipe media between media server instances so that we can horizontally scale?

2. I saw a recent tweet that mentioned Medooze as having E2EE using the recently implemented Insertable Streams and SFrames, but I see PERC listed still. Is the readme just out of date?

3. How out of date are the docs and exported Typescript types? We'd hate to get started using this in our app, only to spend most of our time fiddling with out of date docs.

4. Finally, if we need support, it appears you offer commercial support. Is that correct? That's a good thing for us down the road. In the meantime, hopefully, you're still able to answer an occasional question?

Thanks so much for your time!

[Sergio Garcia Murillo]

Hi Nicholas!

First note that the SFU publicly on the repo is just a demo for the
Medooze media server, you can use it as reference to build your own one
and modify it at will.
Find my answers inline.

Best regards
Sergio

On 07/04/2020 23:09, Nicholas Clark wrote:
> We are currently evaluating Medooze and MediaSoup for our project. We
> really like the architecture, scalability, and great support that
> MediaSoup has, but it doesn't yet have true E2EE.
>
> We have been looking at Medooze, which seem to be quite similar, but
> we had some questions:
>
> 1. Are we able to pipe media between media server instances so that we
> can horizontally scale?

Yes, you can pipe data between Endpoints in different media servers.

> 2. I saw a recent tweet that mentioned Medooze as having E2EE using
> the recently implemented Insertable Streams and SFrames, but I see
> PERC listed still. Is the readme just out of date?

The SFU supports PERC-lite, which we developed as a PoC for the IETF
group. We have full Sframe support for native clients as per :

https://webrtcbydralex.com/index.php/2020/03/30/secure-frames-sframes-end-to-end-media-encryption-with-webrtc-now-in-chrome/

but the implementaion of the demo SFU just does a naive usage of the
insertable mediastreams to show that all required pieces needed to
implement them are available. We still don't know if we will be
implementing and open sourcing the js version fo Sframe as it would
require some sponsor paying for the development time.

> 3. How out of date are the docs and exported Typescript types? We'd
> hate to get started using this in our app, only to spend most of our
> time fiddling with out of date docs.

Up to date documentation is available in:

https://medooze.github.io/media-server-node/

Unfortunately the typescript bindings was a contribution from an outside
developer that has not maintained it since then.

> 4. Finally, if we need support, it appears you offer commercial
> support. Is that correct? That's a good thing for us down the road. In
> the meantime, hopefully, you're still able to answer an occasional
> question?

Yes, we provide commercial support and consulting services. Questions on
the group will be answer on a best effort base


Best regards

Sergio

[Nicholas Clark]

Thanks for the fast reply! Those answers help a lot. 

We use Typescript extensively, so the lack of typings is a holdback for us, but if we decide on Medooze, we may just add our own. Typings make developing a new app from a library such as this much faster and more discoverable.

Thanks again!

[Sergio Garcia Murillo]

The ts file should be quite recent, so shouldn't be very outdated as API has been quite stable lately. Some methods may be missing tough.

--
You received this message because you are subscribed to the Google Groups "medooze" group.
To unsubscribe from this group and stop receiving emails from it, send an email to medooze+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/medooze/77ec96c7-c03f-4a86-ac57-aeff3e83a022%40googlegroups.com.