OpenVidu AWS Multi-Region setup

Hi,

I have started using OpenVidu a few months back. I was able to setup everything and got it working reasonably quickly for the initial phase of my application. But now, I want a Multi-Region setup for OpenVidu where each user will be connected to its nearest server regardless of where the other end user’s server connection.

Example: I will set up two OpenVidu clusters, “us-east-1” and “eu-central-1”. If I have two UK and US users starting a session, the US user will join us-east-1, and the UK user will join eu-central-1 and have a seamless session.

For routing, I will be using the Route53 Geolocation feature, but I need help with server to server connection setup.

Thanks.

Hi,

Routing media connections across servers is not supported right now. You can choose a specific OpenVidu deployment were to initialize a particular Session, probably based on the location of the first user joining to it, but hosting a single session across multiple Kurento Media Servers is not contemplated. And building that feature is not trivial, as it would require connecting media servers, using a completely new logic.

@pabloFuente, are you guys planning to add support for it in near future? We have purchase OpenVidu Pro and if you are not going to add support for it then I would have to look for alternative solutions.

Thanks for the quick response.

We plan to allow spread sessions among media-nodes for scalability.

Maybe the feature can be used to connect users in different regions.

In any case, it is not in our short-term roadmap.

Regards

Ok, Thanks @micael.gallego @pabloFuente.

Nevertheless, let me clarify a few things related to this topic. The option of connecting users in different geographical areas using different media servers that communicate with each other may not provide a significant benefit in terms of latency. Both users have to communicate with their respective (nearest) media server, but then both media server have to communicate between them. This may even introduce a higher latency in the e2e communication, as packets have to be processed in each media server. The best solution is to assign a server at an intermediate geographical point. For that you would need to previously know the location of all the participants of the session, and then calculate the best possible OpenVidu deployment, so the total distance between all ends and the server is as little as possible. Of course this is all in theory, as the quality of the client’s network and other factors come into play. A connection between Europe and Australia with a high-performance server located at Bahrain and good networks at the client side in can be much better than a connection between two users in the same country with not-so-good networks.

2 Likes