This topic describes the application scenarios of ApsaraDB for MyBase.

Typical scenarios

  • Scenario 1: ApsaraDB for MyBase ensures data compliance and security by protecting your data against external and internal security threats to the cloud platform. ApsaraDB for MyBase isolates your resources from the resources of other users.
  • Scenario 2: ApsaraDB for MyBase meets extremely high performance requirements. Assume that you need to use dedicated physical resources and connect to existing monitoring and O&M systems. You can maintain your database O&M experience and add instance resources to cope with peak-hour traffic. For more information, see Configure resource scaling for instances to handle peak-hour traffic.
  • Scenario 4: ApsaraDB for MyBase helps you improve the CPU and storage utilization and reduce the costs of using cloud-based databases. For more information, see Configure resource overcommitment to reduce costs.

Use cases

  • Use case 1

    Problem description:

    If you use other ApsaraDB services, some of your resources are not used when the loads are low. This results in a low resource utilization rate and is not cost-effective.

    Solution:

    Use ApsaraDB for MyBase to create multiple overcommitted hosts of the same specifications for your instances. This improves CPU utilization and reduces resource costs. For more information, see Configure resource overcommitment to reduce costs.

  • Use case 2

    Problem description:

    During online shopping festivals, such as 618 and Double 11, you may need to upgrade the specifications of your instances to improve performance. However, the specifications cannot be downgraded after these events. This increases costs.

    Solution:

    The elastic scaling feature allows you to upgrade instance specifications to improve performance for a short period of time. The instance specifications include memory and CPU. After the specified period of time ends, ApsaraDB for MyBase automatically restores the instance specifications to the status before the elastic scaling. For more information, see Configure resource scaling for instances to handle peak-hour traffic.