Scalability and Load balancing

CXO-Cockpit can be scaled out to multiple servers to increase the system responsiveness and/or to implement failover scenarios. This article explains how to install the CXO-Cockpit on multiple servers.

Load balancing for the CXO-Cockpit Web Applications

CXO-Cockpit web applications can be installed on several servers. There should be a load balancer provided by the destination infrastructure that passes the HTTP(s) requests from the clients through to one of the available CXO-Cockpit servers. The only requirement to the load balancer is that it must implement "sticky sessions" scenario: all subsequent requests from a certain client must end up to the same CXO-Cockpit server as the first request from that client. The most typical implementation of this scenario is "Cookie-based Persistence". In this scenario the load balancer appends a cookie to the first client's request that is used later on to identify the server all the subsequent requests should be forwarded to.

Scalability of other components

CXO-Cockpit is delivered as an IIS web application and a couple of Windows applications. The following table shows which components should be installed in the multi-server setup.