Distributed installation

Learn about distributed installation on Analytics Content Hub.

The Analytics Content Hub architecture is flexible enough to handle the distribution of components across numerous servers to achieve different objectives. For redundancy or high availability, the following installation pattern might be used.

The previous diagram demonstrates a fault tolerant deployment type that consists of two full installations of Analytics Content Hub. Each server has Tomcat, the machine learning engine, multiple Elasticsearch nodes, and a PostgreSQL instance. The difference here is that one PostgreSQL instance serves as a primary with the other instance running in standby mode in case the first instance becomes unresponsive. Similar to the single-server deployment model, no proprietary reporting data is ever persisted within either PostgreSQL instance.

This diagram also represents a possible Cloud deployment and has an extra VPN component included in case access to an on-premises content system, residing behind a firewall, was required. To reduce management efforts, virtual machine images, or Kubernetes for Cloud deployments, ‘containers’ might be created for the automation of scaling activities.

Like the single-server installation, SSL communication is enabled. But to achieve the scalability, this type of installation would require the addition of a Load Balancer between the users and the Analytics Content Hub servers.