HipChat Data Center architecture

HipChat Data Center allows you to deploy more HipChat nodes for greater deployment scale and availability. HipChat Data Center also externalizes the data stores that were previously included in a single virtual host, allowing greater flexibility for your organization.

A HipChat Data Center deployment consists of:

  • one, or three HipChat Data Center nodes
  • a load balancer or reverse proxy that handles SSL termination and directs connections to the HipChat node(s)

    Load balancer vs. Reverse proxy

    Load balancer or Reverse proxy?

    In both deployment scale options, clients access the HipChat node(s) through a service which terminates SSL. This is required regardless of which deployment type you choose.

    In an Enterprise-scale deployment this service is a load balancer which distributes client connections among the HipChat nodes. In a small-scale deployment all connections go to a single HipChat node, so this service can be just a reverse proxy.

    Several services (such as NGINX or Apache) can function as both a load balancer and a reverse proxy. If you use one of these, you can quickly scale up your deployment later by adding more HipChat nodes.

  • a Postgres database
  • a Redis server
  • a shared NFS file system
  • optionally, a "jumpbox" or management endpoint inside the cluster

You can learn more about the technical details of these requirements in the deployment options and sizing guidelines, and read more about the configuration requirements.

An Enterprise-scale deployment of HipChat Data Center

A small-scale deployment of HipChat Data Center

Last modified on Sep 5, 2017

Was this helpful?

Provide feedback about this article

Not finding the help you need?

Ask the community

Powered by Confluence and Scroll Viewport.