Typical scenarios
Data compliance and security isolation
If your workloads must meet strict data residency or compliance requirements, MyBase provides dedicated physical hosts where your resources are isolated from the resources of other users on the cloud platform. This architecture supports external and internal security requirements.
High-performance, dedicated resources
If your databases require consistently high performance and you need to integrate with existing monitoring and operations and maintenance (O&M) systems, MyBase lets you run instances on dedicated physical resources without contention from other users. When traffic spikes occur, you can add instance resources to the host to handle the load. For details, see Configure elastic scaling for instances to handle traffic spikes.
Improved resource utilization and lower costs
If you have underutilized hosts during off-peak periods, MyBase lets you enable resource overcommitment — deploying more instance capacity than the physical host's nominal CPU and storage — to increase utilization and reduce per-instance costs. For details, see Configure resource overcommitment to reduce costs.
Scenario four: Using open host OS and database permissions. MyBase can grant partial OS permissions for hosts, which lets you use custom scripts. For more information, see Use custom scripts.
Use cases
Low host utilization
*Problem*: Resources sit idle during low-load periods. Paying for unused capacity across multiple hosts is not cost-effective.
*Solution*: Use ApsaraDB for MyBase to create multiple overcommitted hosts of the same specifications for your instances. By allocating more virtual CPU and storage than the host's physical capacity, you increase utilization and reduce resource costs. For details, see Configure resource overcommitment to reduce costs.
Traffic spikes during peak events
*Problem*: During high-traffic events such as the 618 and Double 11 online shopping festivals, you may need to upgrade instance specifications (memory and CPU) to maintain performance. However, the specifications cannot be downgraded after these events, which increases costs.
*Solution*: Use the elastic scaling feature to temporarily upgrade instance specifications for the duration of the event. After the specified period ends, ApsaraDB for MyBase automatically restores the instance to its original specifications — so you pay for the extra capacity only when you need it. For details, see Configure elastic scaling for instances to handle traffic spikes.
Use case three
Problem:
Traditional ApsaraDB products do not provide backend access, which prevents you from connecting them to your own management center. When you have many instances, you cannot manage them centrally, which increases O&M costs.
Solution:
MyBase supports host logon and grants OS permissions. You can use a Bastionhost to log on to and manage the hosts where database instances reside. On the hosts, you can install custom scripts to collect system info and connect to your management center to meet custom requirements. For more information, see Use custom scripts.