ApsaraDB for OceanBase supports two billing methods: Subscription and Pay-as-you-go, and three deployment solutions: multi-Internet data center (IDC) deployment, dual-IDC deployment, and single-IDC deployment.
High-availability edition
Multi-IDC deployment
In multi-IDC deployment, ApsaraDB for OceanBase is deployed on three nodes in three different zones to enable zone-level disaster recovery.
Each node in multi-IDC deployment is a full-featured replica. One replica is the leader that provides read and write services, and the other two are followers that provide read-only services. If the leader fails, a follower takes over the read and write services.
We recommend that you choose multi-IDC deployment if you have high requirements for performance and availability.
Dual-IDC deployment
ApsaraDB for OceanBase can be deployed across two IDCs:
In dual-IDC deployment, ApsaraDB for OceanBase is deployed on two nodes in two zones. One node provides read and write services and serves as the leader, and the other node provides read-only services and serves as the follower.
A log node is deployed in a third zone. This node is used only for log synchronization. It does not contain replicas of business data or provide read or write services, and is invisible to users.
Dual-IDC deployment provides IDC-level disaster recovery and is more cost-effective than multi-IDC deployment.
Single-IDC deployment
In single-IDC deployment, all ApsaraDB for OceanBase nodes are deployed in the same zone. This solution supports host-level disaster recovery.
Single-IDC deployment also has the following advantages:
Two full-featured replicas provide read and write services at the same time, which means higher database read and write performance.
In single-IDC deployment, data synchronization for write requests features low latency because the synchronization does not need to be performed across IDCs.
The log node in single-IDC deployment is invisible to users.
Differences between the deployment solutions
Deployment solution | Multi-IDC | Dual-IDC | Single-IDC |
Number of purchased nodes | 3 | 3 | 3 |
Number of full-featured replicas | 3 | 2 | 2/3 |
Number of log-only replicas | 0 | 1 | 1/0 |
Number of nodes that are visible to users | 3 | 2 | 2 |
In the 2F1L replica plan, the log-only replica is invisible to users. That is, although three nodes are purchased, only two nodes in the system are visible to users.