a
Example Architectures
AltioLive can be implemented in various different architectures. Three possible alternatives are given below:
A single Presentation Server is deployed to communicate with a number of clients. The Presentation Server may be deployed on the same physical Server as the back end system or on a separate one. In the latter case it would need to use a clustered Application Server in order to preserve the user's session information.
For resilience, two Presentation Servers are deployed. These operate independently and utilize the load balancing of the Application Server to route connections to one or other Presentation Server. Both are designated as Master Presentation Servers. A clustered Application Server environment is required for this environment.
For handling large number of connections, multiple Presentation Servers are deployed in conjunction with clustered Web Servers in a Master-Slave configuration. The clustering/load balancing will connect users to any of the Slave Presentation Servers, which then connect directly to one or other of the Master Presentation Servers. Whilst it can be configured so that clients also can connect directly to a Master Presentation Server, this is not recommended.
The communication mechanism of the Slave Presentation Server with the Master Presentation Server for transferring data updates can be set to HTTP polling, streaming or socket. If the polling mechanism is used, the number of concurrent requests handled by the Master Presentation Server limits the number of Slave Presentation Servers able to be connected to a Master Presentation Server. The preferred mechanism is Socket as this does not require an HTTP connection and is the most efficient.