Product series
This topic describes the advantages, scenarios, and available specifications of ApsaraDB for OceanBase Standard Edition. The Standard Edition is available in four series: Standard Edition (Cloud Disk), Standard Edition (Local Disk), Standard Edition (Archive Database), and Standard Edition (Key-Value).
Introduction to the Standard Edition
Standard Edition (Cloud Disk)
Standard Edition (Cloud Disk) is the recommended high availability (HA) instance type. It offers a comprehensive range of specifications and deployment solutions, making it suitable for a wide variety of scenarios.
You can scale out the instance type and expand the storage capacity. For more information, see Modify storage capacity and Modify instance type.
When you expand storage capacity, the operation is performed in place and does not affect your services.
When you scale out the instance type, a transient disconnection occurs due to data migration. Perform this operation during off-peak hours.
In addition, if the primary database fails, the system automatically switches to the secondary database. Your service experiences a brief interruption, and data is recovered quickly.
Standard Edition (Local Disk)
Standard Edition (Local Disk) is a high availability (HA) instance type that uses local SSDs for storage. It is designed for scenarios that require high stability. Local disk storage provides low I/O latency and high performance, and avoids long-tail latency issues.
Standard Edition (Local Disk) only supports scaling out the instance type. When you scale out, both the instance type and storage capacity are upgraded, which involves machine migration. A transient disconnection will occur. Perform the scale-out operation during off-peak hours.
In addition, if the primary database fails, the system automatically switches to the secondary database. Your service experiences a brief interruption. Because data on the local disk needs to be recopied, the recovery time is longer.
Standard Edition (Archive Database)
As your business grows, your database system may accumulate a large amount of data that is accessed infrequently but still needs to be retained. To save costs, you can purchase the Standard Edition (Archive Database) to migrate this data to low-cost storage devices where it is stored as files. The Standard Edition (Archive Database) has the following features:
Large storage capacity. You can continuously save online data to the archive database without worrying about capacity constraints.
It uses the same access interface as the online database system. This ensures that your application can access both the online and archive databases without any code changes.
Low cost. It supports features such as compression to reduce disk space usage and uses low-cost storage media. This lets you store massive amounts of data at a lower cost.
It provides sufficient read and write capabilities to meet the needs of low-frequency access.
Standard Edition (Key-Value)
Standard Edition (Key-Value) is built on the OceanBase relational database (relational + SQL). It shares the same storage and ecosystem but provides simpler, more efficient non-relational APIs. It supports the storage and processing of various non-relational data models, leveraging the advantages of OceanBase's integrated architecture to meet diverse data requirements across different scenarios.
Standard Edition (Key-Value) uses OceanBase's Shared-Nothing architecture, where all nodes are peers. It features core attributes such as scalability, high availability, high performance, low cost, and a cloud-native design.
Deployment solutions
ApsaraDB for OceanBase Standard Edition (Cloud Disk), Standard Edition (Local Disk), and Standard Edition (Archive Database) support multi-data center, dual-data center, and single-data center deployment solutions. Standard Edition (Key-Value) supports only dual-data center and single-data center deployment solutions. For more information, see Deployment solutions.
Customers who require higher performance and multi-data center availability should choose the multi-data center deployment solution.
Available specifications
The available specifications vary among the ApsaraDB for OceanBase Standard Edition (Cloud Disk), Standard Edition (Local Disk), Standard Edition (Archive Database), and Standard Edition (Key-Value) series. Select the specifications that suit your business needs.
The supported node specifications vary by database version. For a list of supported options, see the purchase page.
You can expand the maximum storage capacity of an instance after purchase. For more information, see Modify storage capacity.
Standard Edition (Cloud Disk)
Specifications | CPU (Cores) | Memory (GB) | Storage Range (GB) |
Spec 1 Note This specification is available only when the instance type is Tenant Instance. It currently supports only MySQL mode and cannot be changed after selection. | 1 | 4 | The storage for this specification is pay-as-you-go. Storage fee = Metered GB × Duration × Hourly list price. For more information, see Billing methods by storage class. |
Spec 2 Note This specification is available only when the instance type is Tenant Instance. It currently supports only MySQL mode and cannot be changed after selection. | 2 | 8 | The storage for this specification is pay-as-you-go. Storage fee = Metered GB × Duration × Hourly list price. For more information, see Billing methods by storage class. |
Spec 3 Note Only OceanBase V4.x supports this specification. For other specifications, select OceanBase V3.2.x. | 4 | 16 | 50~5000 |
Spec 4 | 8 | 32 | 100～10000 |
Spec 5 | 14 | 70 | 200～20000 |
Spec 6 | 24 | 120 | 300~30000 |
Spec 7 | 30 | 180 | 400～40000 |
Spec 8 | 62 | 400 | 800～80000 |
Spec 9 Note To use this specification, submit a ticket to contact technical support. | 104 | 600 | 1000~40000 |
Spec 10 | 8 | 16 | 50~3000 |
Spec 11 | 16 | 32 | 100~5000 |
Spec 12 | 24 | 48 | 150~7500 |
Spec 13 | 32 | 70 | 200~10000 |
Spec 14 | 64 | 180 | 400~20000 |
Standard Edition (Cloud Disk) supports scaling out the instance type and expanding the storage capacity separately. For more information, see Modify storage capacity and Modify instance type.
Standard Edition (Local Disk)
Specifications | CPU (Cores) | Memory (GB) | Storage Size (GB) |
Spec 1 | 16 | 70 | 3000 |
Spec 2 | 32 | 160 | 6000 |
Spec 3 | 64 | 380 | 12000 |
When you scale out a Standard Edition (Local Disk) instance, you must upgrade both the instance type and storage capacity at the same time. For more information, see Modify storage capacity and Modify instance type.
Standard Edition (Archive Database)
Specifications | CPU (Cores) | Memory (GB) | Storage Size (GB) |
Spec 1 | 20 | 32 | 40000 |
Spec 2 | 40 | 64 | 80000 |
When you scale out a Standard Edition (Archive Database) instance, you must upgrade both the instance type and the number of nodes. For more information, see Modify instance type and Scale in by deleting nodes. Because archive databases usually contain a large volume of data, scaling out involves data migration and may take a long time.
Standard Edition (Key-Value)
Specifications | CPU (Cores) | Memory (GB) | Storage Size (GB) |
Spec 1 | 4 | 16 | 50～5000 |
Spec 2 | 8 | 32 | 100～10000 |
Spec 3 | 16 | 70 | 200～20000 |
Spec 4 | 24 | 120 | 300～30000 |
Spec 5 | 32 | 180 | 400～40000 |
Spec 6 | 8 | 16 | 50~3000 |
Spec 7 | 16 | 32 | 100~5000 |
Spec 8 | 24 | 48 | 150~7500 |
Spec 9 | 32 | 70 | 200~10000 |
Spec 10 | 64 | 180 | 400~20000 |
Standard Edition (Key-Value) supports scaling out the instance type and expanding the storage capacity separately. For more information, see Modify storage capacity and Modify instance type.
Currently, only OceanBase Database V3.2.x, V3.3.x, and V4.x support Standard Edition (Key-Value). To use other database versions, contact OceanBase technical support.
Currently, the 4-core 16 GB, 8-core 32 GB, 16-core 70 GB, and 24-core 120 GB configurations for the Standard Edition (Key-Value) series are available only in the China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Zhangjiakou), and China (Shenzhen) regions.