Benefits of the Pexip Infinity distributed architecture
Pexip Infinity is built on top of a distributed architecture which provides:
- Centralized management of any number of Conferencing Nodes in any number of locations.
- Ability to deploy conferencing resources where and when required, without service outage.
- Ability to deploy dedicated Proxying Edge Nodes to handle all external connections, and leave the conference media processing to privately-addressed Transcoding Conferencing Nodes.
- Significant WAN bandwidth savings in conferences that span locations.
- Consistent user experience, independent of the number of Conferencing Nodes.
- Increased resilience to temporary network outages.
- Ability to use Conferencing Nodes as gateways for person-to-person calls, thus avoiding hairpinning of media back to a centralized datacenter.
- Allocation of licenses from a central pool.
Pexip Infinity distributed architecture is purely software-based and virtualized, running on industry-standard servers. It consists of:
- A single Management Node. A Pexip Infinity deployment, regardless of size, has just one Management Node. The purpose of the Management Node is to create and manage Conferencing Nodes. The Management Node is in neither the signaling nor the media path of a conference.
- One or more Conferencing Nodes. Conferencing Nodes handle all aspects of the media and signaling connections to endpoints and other devices, and host the associated conferences. A minimal Pexip Infinity deployment has one Management Node and one Conferencing Node. However, most Pexip Infinity deployments will have multiple Conferencing Nodes.
A Management Node can run on the same host server as a Conferencing Node. Other Conferencing Nodes can run on host servers in the same or different locations, allowing you to create a globally distributed system. You can have two Conferencing Nodes running on the same host server, for example to ensure service continuity during upgrade of one of the Conferencing Nodes, and for maximum performance.
The Pexip Infinity platform can also be deployed as a cloud service via Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform, or Oracle Cloud Infrastructure, with private, public or hybrid deployment options.
Configuration and provisioning data is pushed out from the Management Node to all the Conferencing Nodes, and diagnostics data and event information is sent from the Conferencing Nodes back to the Management Node. Administrators never have to manage a Conferencing Node directly. This centralized management ensures that the entire deployment is configured with a consistent data set – the entire deployment acts as a single application.
You can easily scale a deployment up by creating several Conferencing Nodes in the same location (i.e. the same datacenter). Capacity can even be added “on the fly” – Conferencing Nodes can be added in a couple of minutes if more capacity is needed. Alternatively, each location can be configured to overflow to another location if it reaches its capacity, including bursting to temporary resources on a cloud service.
A typical Pexip Infinity deployment consists of two or more locations. If a customer has three main offices such as New York, London and Tokyo, and a concentration of users in those locations, you would typically deploy Conferencing Nodes in all three locations. There is no limit on the number of locations in a Pexip Infinity deployment. Additional locations can be added “on the fly” while the system is operating, with no impact on service availability.
Application level resiliency greatly improves on a conference experience during for instance temporary network outages, as Pexip Infinity will automatically re-establish the conference when the network connection is re-established.