Cluster Architecture
Cluster Overview
Cluster component
This section describes various cluster components.
Load balancer
A load balancer is a device / application that acts as a reverse proxy and distributes network or application traffic across a number of servers.
It is recommended to use a non-sticky session in order to distribute the load evenly among servers.
Server
Physical or virtual device that dedicated for running Codebeamer
Local file system
A file system controls how data is stored and retrieved. Codebeamer only stores static data on a local file system. For instance, a compiled Java file of Codebeamer.
Shared file system
A shared file system uses a storage area network (SAN) to allow multiple servers to gain direct disk access. Codebeamer stored all non-static data on shared files system.
Database server
A database server is a server which uses a database application that provides database services to Codebeamer servers.
You can find our supported databases here: General System Requirements.
Email server
A server that uses an email application to send and receive emails.
Cluster with installed Codebeamer
A single node installation is sufficient for most small and medium size deployments. You need clustering when
• You need high availability with active-active cluster.
• You need to scale for large number of concurrent users.
You can find a detailed guide about installing Codebeamer onto a server here: Codebeamer configuration
Cluster with docker
You can find a detailed guider how to start and configure Codebeamer container here: Docker and How to start docker container for cluster environment.
We also recommend using an auto heal solution along Codebeamer. It will restart your instance in case of Codebeamer container's health changed to unhealthy. Following container is recommended: https://hub.docker.com/r/willfarrell/autoheal/