This topic describes the best practices for using ApsaraDB for MyBase to create a database that supports independent O&M and auto scaling.
Before you migrate enterprise data to the cloud, you may focus on whether you can independently manage the database that stores your data. For example, you may want to use dedicated cloud resources, perform independent O&M, and obtain OS permissions. You may also want to use a database that meets the requirements for regulatory compliance, security, and high performance. If your business undergoes workload fluctuations, a database that supports auto scaling is preferred. This way, you can use scalable resources to meet business requirements. This reduces data and resource costs. ApsaraDB for MyBase enables dedicated cloud resources and resource overcommitment. ApsaraDB for MyBase also allows you to perform independent O&M and grant users some OS permissions and database permissions. ApsaraDB for MyBase is a dedicated database solution that provides a customized and optimized database service for enterprise users.
For more information about the best practices for ApsaraDB for MyBase, see Use ApsaraDB for MyBase to create a database that supports independent O&M and auto scaling.
Create a database
ApsaraDB for MyBase allows you to create a dedicated cluster so that you can schedule resources and manage hosts and instances in the dedicated cluster. For more information, see Create a dedicated cluster, Add hosts, and Create an instance. You pay only for the hosts that you create and for the enhanced SSDs that you use. You do not need to pay for dedicated clusters, instances, memory, or local disks. For more information, see Billing methods.
Enable auto scaling to handle workload fluctuations
- High elasticity: Auto scaling automatically creates and releases ECS instances based on your configuration. Manual operations are not required.
- High availability: Auto scaling automatically checks ECS instances, releases stopped ECS instances at the earliest opportunity, and then creates ECS instances.
Grant users database permissions
ApsaraDB for MyBase allows you to grant users the OS permissions. This way, you can independently manage your database. You can run the top or Isof command to view the process status. You can also create custom monitoring metrics based on your business requirements. For example, you can create a custom dashboard that displays monitoring metrics by line-of-business or by the importance of database instances.
A bastion host secures database connections and makes O&M and operational audits easy and efficient. All the operations performed on the bastion host are recorded in the operation logs. You can search for operation logs and view log details. For more information, see Create a bastion host, Access a Linux host from a bastion host, and Access a Windows host from a bastion host.
Create read-only instances and enable read/write splitting
ApsaraDB for MyBase allows you to create read-only instances and enable read/write splitting to meet growing business requirements. This way, you can improve the read capability of your database and offload the read requests from your primary instance. This allows your database to process a large number of read requests and increases the throughput of your application. For more information, see Create a read-only MyBase for MySQL instance
Enable auto scaling for a cluster with heavy workload
ApsaraDB for MyBase supports resource overcommitment when you create multiple instances of the same specifications in a dedicated cluster. You can monitor host performance and increase the number of hosts based on your business requirements. If the number of requests surges in a short period of time, auto scaling helps you handle traffic spikes. The elastic scaling feature can be enabled. This upgrades instance specifications to improve performance for a short period of time. The instance specifications include memory and CPU cores. After the specified period of time ends, ApsaraDB for MyBase automatically restores the instance specifications to those before the upgrade. For more information, see Configure resource scaling for instances to handle peak-hour traffic and Configure resource overcommitment to reduce costs.