El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.
- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Before You Start
- Permissions Management
-
Exclusive ServiceComb Engine
- Creating a ServiceComb Engine
-
Managing ServiceComb Engines
- Viewing ServiceComb Engine Information
- Obtaining the Service Center Address of a ServiceComb Engine
- Obtaining the Configuration Center Address of a ServiceComb Engine
- Viewing the Instance Quota of a ServiceComb Engine
- Viewing the Configuration Item Quota of a ServiceComb Engine
- Configuring Backup and Restoration of a ServiceComb Engine
- Managing Public Network Access for a ServiceComb Engine
- Viewing ServiceComb Engine Operation Logs
- Upgrading a ServiceComb Engine Version
- Deleting a ServiceComb Engine
- Changing ServiceComb Engine Specifications
- Managing Security Authentication for a ServiceComb Engine
- Managing Tags
- Using ServiceComb Engines
- Registry/Configuration Center
- Key Operations Recorded by CTS
-
Best Practices
- CSE Best Practices
-
ServiceComb Engines
-
ServiceComb Engine Application Hosting
- Hosting Spring Cloud Applications Using Spring Cloud Huawei SDK
- Hosting a Java Chassis Application
-
ServiceComb Engine Application Hosting
- Registry/Configuration Centers
-
Developer Guide
- Overview
- Developing Microservice Applications
- Preparing the Environment
- Connecting Microservice Applications
- Deploying Microservice Applications
- Using ServiceComb Engine Functions
- Appendix
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Examples
-
CSE API
- API Calling
- Dynamic Configuration
-
Engine Management
- Querying Flavors Supported by a Microservice Engine
- Querying the Microservice Engine List
- Creating an Exclusive Microservice Engine
- Querying Details About a Microservice Engine
- Deleting a Microservice Engine
- Querying Details About a Microservice Engine Job
- Retrying an Exclusive ServiceComb Engine
- Upgrading an Exclusive ServiceComb Engine
- Changing Microservice Engine Specifications
- Updating the Configuration of an Exclusive Microservice Engine
-
Microservice Governance
- Querying the Governance Policy List
- Creating a Dark Launch Policy
- Querying a Dark Launch Rule of a Microservice
- Deleting a Dark Launch Policy
- Changing a Governance Policy
- Deleting a Governance Policy
- Querying Governance Policy Details
- Creating a Governance Policy
- Querying the Governance Policy List of a Specified Kind
- Nacos API
-
ServiceComb API
- API Calling
- Authentication
-
Microservice
- Querying Information About a Microservice
- Deleting Definition Information About a Microservice
- Querying Information About All Microservices
- Creating Static Information for a Microservice
- Deleting Static Information About Microservices in Batches
- Modifying Extended Attributes of a Microservice
- Querying the Unique Service or Schema ID of a Microservice
- Schema
-
Microservice Instance
- Registering a Microservice Instance
- Querying a Microservice Instance Based on service_id
- Deregistering a Microservice Instance
- Querying Details About a Microservice Instance
- Modifying the Extended Information About a Microservice Instance
- Modifying Status of a Microservice Instance
- Sending Heartbeat Information
- Querying a Microservice Instance by Filter Criteria
- Querying Microservice Instances in Batches
- Dependency
- Configuration Management
- Appendixes
- Change History
- SDK Reference
-
FAQs
- Precautions When Using Huawei Cloud CSE
- Nacos Engines
-
ServiceComb Engines
- How Do I Perform Local Development and Testing?
- How Can I Handle a Certificate Loading Error?
- What If the Header Name Is Invalid?
- What Is the Performance Loss of Mesher?
- Why Is "Version validate failed" Displayed When I Attempt to Connect to the Service Center?
- Why Is "Not enough quota" Displayed When I Attempt to Connect to the Service Center?
- What Should I Do If the Service Registration Fails After IPv6 Is Enabled for the Exclusive ServiceComb Engine with Security Authentication Enabled?
- What Is Service Name Duplication Check?
- Why Do I Have to Define Service Contracts?
- Why Are Microservice Development Framework and Netty Versions Unmatched?
- What Do I Need to Know Before Upgrading an Exclusive ServiceComb Engine?
- What Must I Check Before Migrating Services from the Professional to the Exclusive Microservice Engine?
- Why Is "Duplicate cluster name" Displayed?
- Error Message "the subnet could not be found" Is Displayed When the Access Address Fails to Be Processed During Engine Creation
- Why Is Error "does not match rule: {Max: 100, Regexp: ^[a-zA-Z0-9]{1,160}$|^[a-zA-Z0-9][a-zA-Z0-9_\-.]{0,158}[a-zA-Z0-9]$}"}" Reported?
- What Should I Do If SpringCloud Applications Fail to Connect to the Configuration Center of ServiceComb Engine 2.x?
- Why Could My the Global Configuration Not Be Modified?
- Obtain Configurations Failed
- Videos
- General Reference
Copied.
Pay-per-Use
Pay-per-use allows you to use resources before paying for them. It is recommended when you do not want to pay in advance or do not need the resources for long. This section describes the pay-per-use billing rules of exclusive ServiceComb engines.
Scenario
Pay-per-use is suitable for applications or services that cannot be interrupted when facing temporary or sudden traffic increases or unpredictable demands, such as e-commerce flash sales, testing, and scientific computing.
Billing Items
Select ServiceComb engine specifications based on the total number of microservice instances to be hosted. You will be billed for specifications you selected. The following items can be billed on a pay-per-use basis.
Billing Item |
Description |
---|---|
Unit price of ServiceComb engine instance specifications (price per hour) |
You are billed for your selected engine instance specifications. ServiceComb engines support 100, 200, 500, or 2000 microservice instances. For details, see Pricing Details of Exclusive ServiceComb Engines. |
Example: When you purchase an exclusive ServiceComb engine that supports 100 microservice instances, fee details are at the bottom of the purchase page, as shown in Figure 1.
The prices are for reference only. Actual prices are subject to those in Pricing Details of Exclusive ServiceComb Engines.
Billing Cycle
In pay-per-use mode, exclusive ServiceComb engines are billed by second and settled by hour (UTC+08:00). After the settlement is complete, a new billing cycle starts. The billing starts when an engine is created, and stops when the engine is deleted.
For example, you purchased an exclusive ServiceComb engine at 08:05:00 and deleted it at 08:55:00. The billing cycle is from 08:00:00 to 09:00:00. You need to pay the fees generated from 08:05:00 to 08:55:00. There is a total of 3000s.
Billing Example
You purchased an exclusive pay-per-use ServiceComb engine (that supports 100 microservice instances) at 09:59:30 on April 18, 2023 and then deleted it at 10:45:46 on the same day.
- The first billing cycle is from 09:00:00 to 10:00:00. You need to pay the fees generated from 09:59:30 to 10:00:00. There is a total of 30s. The fee in this billing cycle is 1.83/3600 x 30 = $0.02 USD.
- The second billing cycle is from 10:00:00 to 11:00:00. You need to pay the fees generated from 10:00:00 to 10:45:46. There is a total of 2746s. The fee in this billing cycle is 1.83/3600 x 2746 = $1.40 USD.
You need to pay for each billing cycle. Table 2 lists the billing formula. The price of a resource listed in the product pricing details is per hour, so divide it by 3600 to obtain the price for each second.
Resource |
Billing Formula |
Unit Price |
---|---|---|
Exclusive ServiceComb engines |
Unit price of instance specifications x Billing duration |
For details, see Pricing Details of Exclusive ServiceComb Engines. |
The prices are for reference only. Actual prices are subject to those in Pricing Details of Exclusive ServiceComb Engines.
Arrears Impact
For the lifecycle of exclusive pay-per-use ServiceComb engines, see Figure 2. Once purchased, resources run within the billing cycle. This is their validity period. If your account is in arrears due to automatic fee deduction, your resources enter the grace period and then the retention period.
Arrears Alert
The system will deduct fees for pay-per-use resources at the end of each billing cycle. You will be notified by email, SMS, or internal messages when your account is in arrears.
Arrears Impact
Your account may be in arrears due to automatic fee deduction for exclusive ServiceComb engines. However, your resources will not be stopped immediately; instead, they enter the grace period. You will need to pay for the fees incurred during the grace period, which you can see on the Billing & Costs > Billing Center > Overview page of the Huawei Cloud console. Huawei Cloud will automatically deduct this amount when you top up.
If you do not pay the arrears within the grace period, your resources will enter the retention period and become frozen. You cannot perform any operations on the pay-per-use resources during this period.
If you do not pay the outstanding amount after the retention period expires, your engines will be deleted and their data cannot be recovered.
Both the grace and retention periods are 15 days.
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