Deployment Solutions
openGauss can be deployed in standalone mode or with one primary node and multiple standby nodes. openGauss does not provide the CM. Therefore, the high availability solution in the subsequent description is achieved based on the cluster management, arbitration, and recovery provided by users.
Common Concepts
Standalone
There is only one database instance.
Primary/Standby
There are primary and standby database instances in the system. The primary instance supports read and write, and the standby instance supports read-only.
Hot/Cold backup
Cold backup: There is only a simple backup set that cannot provide services.
Hot backup: Backup databases can provide services for external systems.
Deployment Modes
For details about the standalone and primary/standby deployment modes, see Table 1.
Table 1 Deployment modes in openGauss
Hardware and Software Specifications
openGauss supports the following CPUs and OSs:
Table 2 openGauss software and hardware specifications
Introduction to Deployment Solutions
The overall deployment solutions can be classified into two types: standalone and primary/standby.
Standalone deployment
The standalone deployment does not ensure reliability or availability. There is only one data copy. Once data is damaged or lost, only physical backup can be used to restore data. Therefore, this deployment mode applies to scenarios such as experiencing databases and commissioning syntax functions in the test environment. You are not advised to use this mode on the commercial live network.
Figure 1 Standalone deployment
Primary/standby deployment
The primary/standby mode is equivalent to two data copies, one for the primary node and the other for the standby node. The standby node receives logs and plays back the logs.
