A system is as resilient as its weakest link. As such, it is recommended to deploy BriefCam in a high availability architecture to ensure business continuity even when some components fail.

The basic principle for high availability is to construct failover clusters for the different parts of the system. This means adding redundant nodes to your system to prevent a single point of failure (SPOF). If one component becomes unavailable, the system can continue running properly with the remaining nodes.

However, adding redundant nodes comes with the price of buying extra hardware and increasing the deployment complexity. Therefore, designing the right solution for your production environment requires balancing between cost and complexity and the risk you are willing to take that the system will become unavailable.

BriefCam uses standard and well-known high availability (HA) technologies and processes to reduce complexity and ease the system’s maintenance.

This document presents the basic principles for achieving clustering and redundancy.

When designing a highly available and robust production system, you should consult with BriefCam’s solutions engineers.