This topic describes the system architecture of OceanBase Cloud Platform (OCP).
The figure below shows the system architecture of OCP.
In the figure:
OCP-Server and OCP-Agent are OCP components.
MetaDB, MonitorDB, and OBProxy are databases or services that OCP depends on.
The alert channel interconnects with external alert platforms. OCP pushes alerts to external alert platforms through the alert channel based on client calls.
Notes
OCP and its managed targets must be deployed in interconnected networks. The targets may include OceanBase clusters, OBProxy clusters, and backup and recovery clusters.
The following table describes the modules in the system architecture.
| Module | Description |
|---|---|
| OCP-Server |
|
| MetaDB | MetaDB stores metadata that OCP-Server depends on. In the production environment, we recommend that you deploy MetaDB as a multi-replica OceanBase database. |
| MonitorDB | MonitorDB stores monitoring data and performance data collected by OCP. Such data includes performance metrics and the statistical and diagnostic information of hosts, clusters, tenants, sessions, and SQL statements. |
| OBProxy | Both MetaDB and MonitorDB are deployed as OceanBase clusters. OCP-Server accesses MetaDB and MonitorDB through OBProxy. |
| OCP console | The OCP administrator accesses the OCP console through a browser. |
| Alert channel |
|
| OCP-Agent | To manage targets, OCP-Agent needs to be installed on the hosts of managed targets. OCP-Agent is used to collect monitoring data and run O&M commands. The host management module of OCP-Server automatically deploys and maintains OCP-Agent. |