Types of Deployment
Helix TeamHub can be deployed in a number of ways, including: Combo, Cluster, or High Availablity Cluster. This section explains the major differences between the types of deployment and depending on the installation environment.
|Time to setup||Minutes||Hours||Days|
Combo deployment is the easiest to deploy. It's quick to setup, and doesn't require provisioning multiple servers, or worrying about inter-server firewalls and advanced configuration.
The entire Helix TeamHub technology stack is bundled in a single operating system package ready to be deployed virtually anywhere- whether it's a bare metal server, cloud computing instance, or a local virtual machine.
The biggest drawbacks of this setup are the required downtime during hardware failures, and the migration to a clustered setup if necessary.
The Bottom Line: Choose Combo deployment for the fastest setup, without a large up-front investment in hardware or IT resources.
Cluster deployment splits Helix TeamHub into two roles: Helix TeamHub Web (application) and Helix TeamHub DB (database). Therefore, Cluster deployment needs at least two servers to operate. Since Helix TeamHub Web connects to Helix TeamHub DB, this type of deployment usually requires tuning the network firewall to allow inter-server communication (see firewall requirements).
Helix TeamHub is then delivered in two standalone packages:
hth-db. As described in Versioning, the major versions need to be kept in sync.
Cluster setup shares similar drawbacks to Combo. However, it has an advantage of being future-proof for highly-available and redundant cluster (see below). Moreover, the physical separation of the server roles increases security and eases maintenance.
The bottom line: Choose the Cluster deployment for a highly available and redundant Helix TeamHub environment that is scalable, without a large up-front investment.
High Available deployment is the most comprehensive and advanced. It requires a bigger up-front investment in hardware and IT resources. However, the benefits of high available deployment include: on demand scalability, zero-downtime maintenance, and maximum availability of Helix TeamHub.
This type of deployment resembles Cluster setup in terms of the packages and server roles, however it requires additional components and redundancy. For instance, SSL is offloaded by the hardware or software Load Balancer (see How to setup HAProxy), which distributes load to a number of Helix TeamHub Web servers (we recommend at least 3), where each in turn uses a number of Helix TeamHub Database servers. Additionally, the shared storage is utilized to have the same data across the cluster nodes.
The bottom line: Choose the High Available type of deployment for maximum availability of Helix TeamHub service and full control over its capacity.