- OpenVidu Enterprise High Availability architecture
- How to deploy your OpenVidu Enterprise High Availability cluster
- Beta limitations
OpenVidu Enterprise High Availability architecture 🔗
OpenVidu Enterprise offers a high availability deployment option in AWS, with replication of all nodes and load balancing for clients. It is made up of 2 different AWS Auto-Scaling groups, managing the 2 different types of nodes of OpenVidu's Master-Worker architecture.
The main difference between a regular OpenVidu Pro deployment and a high availability OpenVidu Enterprise deployment is the replication of Master Nodes. In the image below, on the left a regular OpenVidu Pro deployment and on the right a high availability OpenVidu Enterprise deployment:
The replication of Master Nodes achieves two objectives:
- In case of a Master Node failure the workload can be automatically distributed to other nodes, making the system fail-safe and preventing downtime upon a Master Node crash.
- An OpenVidu Enterprise high availability cluster is able to handle more clients at the same time, as Master Nodes are no longer a bottle neck.
A more accurate architectural description is available in the image below. As can be seen, an AWS Load Balancer is used to evenly distribute the client load, and an AWS ElastiCache database is used to manage shared information between different Master Nodes. All Master Nodes may communicate with all Media Nodes. Two clients connected to the very same OpenVidu session will be connected to the same Media Node, but might be connected to different Master Nodes.
How to deploy your OpenVidu Enterprise High Availability cluster 🔗
OpenVidu Enterprise High Availability is only available in AWS. Go to Deploying OpenVidu Enterprise in AWS to learn how.
Beta limitations 🔗
- Recording is not available yet in OpenVidu Enterprise High Availability. This requires further work to be completely supported, which will be in an upcoming release.
- Sessions are not automatically rebuilt upon a Master Node or Media Node crash or removal. This doesn't mean that sessions cannot be rebuilt, but your application must take care of it. Take a look to openvidu-high-availability demo application to see how to easily do it.
- All API REST requests beginning with
/apiare no longer supported. All requests using this deployment must use
openvidu/api/instead. These REST API requests was announced as deprecated since version 2.16.0