Documentation (2024.2 Enterprise)

# Deployment types

Helix TeamHub can be deployed in Standard, Enterprise, or HA cluster. Standard deployments were formerly known as Combo deployments and Enterprise deployments were formerly known as Cluster deployments.

The following information explains the major differences between the deployment types, depending on the installation environment.

## Quick comparison

| Standard | Enterprise | HA (High Availability)
--- | --- | --- | ---
Time to setup | Minutes | Hours | Days
Complexity | Low | Moderate | High
Servers | 1 | 2 | 5+
Availability | Low | Moderate | High

## Standard

Standard deployment is the easiest to set up. It is quick to set up, it does not require the provisioning of multiple servers, and you do not need to worry about inter-server firewalls and advanced configuration. Standard deployment is suitable for bare metal servers, cloud computing instances, and local virtual machines.

The entire Helix TeamHub technology stack is bundled in a single operating system package. For details of the technology stack used by TeamHub, see System architecture.

The biggest drawbacks of Standard deployments are the downtime required during hardware failures and the effort needed if you ever want to migrate to a Enterprise deployment.

Bottom Line: Choose Standard deployment for the fastest setup, without a large up-front hardware or IT resources investment.

See Standard setup for details about using the Standard setup.

## Enterprise

Enterprise deployment splits Helix TeamHub into two roles:

- The Helix TeamHub application

- The TeamHub DB (database)

Enterprise deployment needs at least two servers to operate because Helix TeamHub Web connects to TeamHub DB. Enterprise deployments require tuning of the network firewall to allow inter-server communication. See firewall requirements.

Helix TeamHub is delivered in two standalone packages: `hth-web` and `hth-db`. The major versions must be kept in sync. See Releases.

Enterprise deployments share similar drawbacks to Standard deployments. However, Enterprise deployments have the advantage of being future-proof for high availability and redundant clusters (see below). The physical separation of the server roles also increases security and eases maintenance.

Bottom line: Choose Enterprise deployment for a highly available and redundant Helix TeamHub environment that is scalable without a large up-front investment.

See Enterprise setup for details about using the Enterprise setup.

## High Availability

HA deployment is the most comprehensive and advanced deployment, but it requires a more significant up-front investment in hardware and IT resources. The benefits of HA deployments are on-demand scalability, zero-downtime maintenance, and maximum availability of Helix TeamHub.

This type of deployment resembles the Enterprise deployment in terms of the packages and server roles, but it requires additional components and redundancy. For instance, SSL is offloaded by a hardware or software Load Balancer, which distributes the 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.

Bottom line: Choose HA deployment for maximum availability of the Helix TeamHub service and complete control over its capacity.

Your search for returned results

Your search for returned results