- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Getting Started with MAS
- Modules
- Namespace
- Multi-Active Instances
- Application Management
- Monitor Management
- Credential Management
- Event Monitoring
- Audit Logs
- Permissions Management
-
FAQs
-
MAS FAQs
- Is MAS a Product or Solution?
- Does MAS Synchronize Data in Addition to Controlling Access from Applications to Databases?
- Is MAS Like a Management Channel for Which I Need to Configure Automatic Switchover Policies?
- What Is the Automatic Switchover Mechanism? How Does MAS Implement Switchovers in Seconds?
-
Multi-Active DR Solution FAQs
- In the Single- or Dual-Instance Data Layer Architecture (Same Region, Multi-AZ, Traffic Distribution with API Gateway), Which Components Are Provided by MAS and Which Ones Should I Prepare?
- Can I Implement the Active-Active Solution on Any Other Services in Addition to Self-Built Cloud Services?
- How Do I Implement Database Dual-Write?
- Does the Multi-Active Architecture Have Any Requirements on My Services?
- What Are the RPO and RTO of the Multi-Active DR Solution?
- Does the Multi-Active DR Solution Have Any Network Requirements? Will Incorrect Switchover Occur If the Network is Unstable or Jitters?
- How Do I Configure Monitoring for Multi-AZ Deployment in the Same Region?
- Will MAS and API Gateway Be Deployed on Both Huawei Cloud and Our Cloud?
- MAS Usage FAQs
-
MAS FAQs
- General Reference
Show all
Copied.
Overview
Pay-per-use and yearly/monthly billing modes are supported.
- Yearly/Monthly is a prepaid mode. You need to pay first, and will be billed for your subscription period. The longer the period, the larger the discount. This mode is suitable for long-term, stable services.
- Pay-per-use is a postpaid mode. You use the service first, and will be billed afterwards for the instance usage and duration. This allows you to adjust resource usage easily. You neither need to prepare for resources in advance, nor end up with excessive or insufficient preset resources. This mode is suitable for scenarios with traffic bursts, such as e-commerce.
Table 1 compares the two billing modes.
Billing Mode |
Yearly/Monthly |
Pay-per-use |
---|---|---|
Payment |
Prepaid Billed by the required duration specified in your order |
Postpaid Billed by the multi-active instances, function modules, nodes, and usage duration |
Billing Cycle |
Billed by the required duration specified in your order |
Multi-active instances are billed by hour, and function modules and nodes are billed by day. |
Billing Mode Change |
Not supported |
Not supported |
Specifications Change |
Not supported |
Not supported |
Billed Item |
Multi-active instance |
Multi-active instance, function module, and node |
Application Scenario |
Recommended for long-term use. Suitable and price-friendly for scenarios where the resource usage duration can be estimated. |
Recommended if you want more flexibility. Suitable for scenarios where resource demands fluctuate. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot