ApsaraDB for MyBase allows you to have more permissions on MyBase for MySQL instances than the permissions on ApsaraDB RDS for MySQL instances. This topic provides an overview of MyBase for MySQL and introduces the related concepts.

MyBase for MySQL

MyBase for MySQL is developed based on the source code of ApsaraDB RDS for MySQL. MyBase for MySQL provides excellent performance and has proved its performance during Double 11. During each Double 11, MyBase for MySQL handles a large number of concurrent requests that involve a large volume of data. MyBase for MySQL provides basic features, such as the management of instances, accounts, and databases, backup and restoration, access control based on whitelists, transparent data encryption (TDE), and data migration. MyBase for MySQL also provides the following advanced features:

  • ApsaraDB for MyBase dedicated clusters: An ApsaraDB for MyBase dedicated cluster consists of multiple hosts, such as ECS instances of the ecs.i2.xlarge instance type and ECS Bare Metal instances. You can run instances on these hosts. For more information, see What is ApsaraDB for MyBase?
  • Read-only RDS instances: If the primary RDS instance is overwhelmed by a large number of read requests, your workloads may be interrupted. In this case, you can create one or more read-only RDS instances to offload read requests from the primary RDS instance. For more information, see Overview of ApsaraDB RDS for MySQL read-only instances. This scales up the read capability of your database system and increases the throughput of your application.
  • Read/write splitting: The read/write splitting function provides a read/write splitting endpoint. This endpoint connects to the primary RDS instance and all of the read-only RDS instances to establish an automatic read/write splitting link. For more information, see Read/write splitting. Your application can read and write data into your database system after it connects to this endpoint. ApsaraDB for RDS distributes write requests to the primary RDS instance and read requests to the read-only RDS instances based on the specified read weights. You can create more read-only RDS instances to scale up the read capability of your database system. In addition, you do not need to modify your application.
  • Dedicated proxy: You can use a dedicated proxy for your MyBase for MySQL instances. A dedicated proxy uses dedicated computing resources and provides more advanced features, such as read/write splitting, short-lived connection optimization, and transaction splitting. For more information, see What are dedicated proxies.
  • Database Autonomy Service (DAS): DAS supports intelligent diagnostics and optimization at the instance level based on various metrics. These metrics include SQL execution performance, CPU utilization, input/output operations per second (IOPS) utilization, memory usage, disk usage, number of connections, locks, and hotspot tables. For more information, see DAS overview. DAS allows you to identify existing and potential issues that may compromise the health of your database system. In addition, DAS provides details and solutions for the identified issues. This facilitates database maintenance.

Supported database engine versions and instance editions

Database engine version Instance edition
MySQL 5.6 High-availability Edition
MySQL 5.7
  • High-availability Edition
  • General Edition
    Note This edition is in public preview. To use this edition, join the DingTalk group: 32484333. Then, you can contact technical support to add your Alibaba Cloud account to the whitelist of users who can use this edition.
  • Basic Edition
MySQL 8.0
  • High-availability Edition
  • Basic Edition

Use MyBase for MySQL