This topic describes the benefits, application scenarios, and specifications for sale of ApsaraDB for OceanBase Standard Edition. ApsaraDB for OceanBase Standard Edition provides four series: Standard Edition (Cloud Disk), Standard Edition (Local Disk), Standard Edition (History Database), and Standard Edition (Key-Value).
Standard Edition series
Standard Edition (Cloud Disk)
Standard Edition (Cloud Disk) is the recommended high-availability instance series that covers the most specifications and deployment solutions and supports a wide range of application scenarios.
Standard Edition (Cloud Disk) supports flexible scale-out of package specifications and storage space. For more information, see Modify the storage space and Modify package specifications.
Storage space scale-out can be performed on the current storage device for the cluster, which brings no impact on services.
Package specifications must be scaled out during off-peak hours because data migration will interrupt services.
When the primary database becomes faulty, the system automatically performs a primary/standby switchover. During the switchover, services will be interrupted instantaneously and data can be recovered quickly.
Standard Edition (Local Disk)
In this series, local SSD disks are used for storage. It applies to scenarios that require high stability. Local disks are characterized by low I/O latency, high performance, and zero long-tail latency.
Standard Edition (Local Disk) supports the scale-out of package specifications only. The specification and storage space scale-out for local disks involves data migration between servers, which will cause transient disconnections. Therefore, perform the scale-out during off-peak hours.
When the primary database becomes faulty, the system automatically performs a primary/standby switchover. During the switchover, services will be interrupted instantaneously. Data in local disks is recopied during the process and therefore the recovery may take a while. Please wait with patience.
Standard Edition (History Database)
As your business grows, your database stores a large and increasing amount of data that is necessary but infrequently accessed. To save storage costs, you can purchase a Standard Edition (History Database) instance and migrate such data to low-price storage devices where data is stored in files. A Standard Edition (History Database) instance has the following characteristics:
It provides a massive storage capacity that allows you to constantly migrate and store online data to the history database.
It uses the same APIs as the online database system to ensure that applications can access both the online and the history databases without code modifications.
It incurs low storage costs. For example, data can be compressed to reduce disk occupation, and low-price storage media can be used. This ensures that massive data can be stored at lower costs.
It supports low-frequency data reads and writes.
Standard Edition (Key-Value)
Standard Edition (Key-Value) is developed based on OceanBase Database (relational + SQL) and shares the storage and ecosystem. It provides simpler and more efficient non-relational APIs for you to bypass the SQL engine and directly read data from the storage engine. It supports various non-relational data models and leverages the benefits of the new architecture that integrates NoSQL with SQL to meet diversified data requirements in different scenarios.
Standard Edition (Key-Value) inherits the Shared-Nothing architecture of OceanBase Database. This architecture supports fully equivalent nodes and features high scalability, high availability, high performance, low costs, and cloud native.
Deployment solutions
Standard Edition (Cloud Disk), Standard Edition (Local Disk), and Standard Edition (History Database) support three deployment solutions: multi-IDC deployment, dual-IDC deployment, and single-IDC deployment. Standard Edition (Key-Value) supports dual-IDC deployment and single-IDC deployment. For more information, see Deployment solutions.
We recommend that you choose multi-IDC deployment if you have requirements for high performance and availability.
Specifications for sale
Standard Edition (Cloud Disk), Standard Edition (Local Disk), Standard Edition (History Database), and Standard Edition (Key-Value) have different specifications for sale. You can select a specification based on your business conditions.
Standard Edition (Cloud Disk)
Specification | CPU (core) | Memory (GB) | Storage space (GB) |
Specification 1 Note You can select this specification only for a tenant instance. At present, only the MySQL tenant mode is supported. After you select this specification, you cannot change it. | 1 | 4 | The storage fee for this specification is charged based on the following formula: Storage fee = Measured data storage size in GB × Storage duration × Catalog hourly price. For more information, see Billing by storage type. |
Specification 2 Note You can select this specification only for a tenant instance. At present, only the MySQL tenant mode is supported. After you select this specification, you cannot change it. | 2 | 8 | The storage fee for this specification is charged based on the following formula: Storage fee = Measured data storage size in GB × Storage duration × Catalog hourly price. For more information, see Billing by storage type. |
Specification 3 Note This specification is supported only in OceanBase Database V4.x. To select other specifications, we recommend that you use OceanBase Database V3.2.x. | 4 | 16 | 50 to 500 |
Specification 4 | 8 | 32 | 100 to 10,000 |
Specification 5 | 14 | 70 | 200 to 20,000 |
Specification 6 | 24 | 120 | 300 to 30,000 |
Specification 7 | 30 | 180 | 400 to 40,000 |
Specification 8 | 62 | 400 | 800 to 80,000 |
Specification 9 Note To use this specification, submit a ticket to contact ApsaraDB for OceanBase Technical Support. | 104 | 600 | 1,000 to 40,000 |
Standard Edition (Cloud Disk) supports separate scale-out of package specifications and storage space. For more information, see Modify the storage space and Modify package specifications.
Standard Edition (Local Disk)
Specification | CPU (core) | Memory (GB) | Storage size (GB) |
Specification 1 | 16 | 70 | 3000 |
Specification 2 | 32 | 160 | 6,000 |
Specification 3 | 64 | 380 | 12,000 |
Standard Edition (Local Disk) supports only simultaneous scale-out of package specifications and storage space. For more information, see Modify the storage space and Modify package specifications.
Standard Edition (History Database)
Specification | CPU (core) | Memory (GB) | Storage size (GB) |
Specification 1 | 20 | 32 | 40,000 |
Specification 2 | 40 | 64 | 80,000 |
Standard Edition (History Database) supports only simultaneous scale-out of package specifications and node quantity. For more information, see Modify package specifications and Add or delete nodes. Generally, a history database contains a large amount of data. Therefore, the scaling may take a long time because data migration is required.
Standard Edition (Key-Value)
Specification | CPU (core) | Memory (GB) | Storage size (GB) |
Specification 1 | 32 | 180 | 200 to 20,000 |
Specification 2 | 64 | 400 | 200 to 20,000 |
Standard Edition (Key-Value) supports separate scale-out of package specifications and storage space. For more information, see Modify the storage space and Modify package specifications.
At present, only OceanBase Database V3.2.3.3 supports Standard Edition (Key-Value). To use Standard Edition (Key-Value) in other versions, contact ApsaraDB for OceanBase Technical Support.