Elastic Compute Service
Billing method |
Billing method | ||||
Payment | Without paying for resources in advance, you can provision and release resources on-demand at any time. You can purchase Reserved Instances (RIs) for cost deduction and saving. For more information, refer to Preferential deduction for pay-as-you-go billing method. | Pay in advance to maximize cost savings; Applicable for scenarios where resources are required in a long term. | A unique Pay-as-you-go method that saves up to 80% of costs compared with standard Pay-as-you-go. However, the price fluctuates based on market supply and demand in real time, and this billing method may be reclaimed due to market price or inventory considerations. | A pre-scheduled, automatic delivery sales mode. For scenarios with elastic resource requirements, this method provides resource assurance, with cost-effectiveness much higher than Pay-as-you-go. |
Settlement cycle | Second-level billing: Settlement is done on an hourly basis. | Billing based on duration: Monthly or yearly subscription options are available. | Second-level billing: Settlement is done on an hourly basis. | Second-level billing: Settlement is done on an hourly basis. If the duration is less than one hour, billing will be made for one hour. If the instance is used for more than one hour, billing will be based on actual consumption. |
Price characteristics | The hourly unit price is higher compared with other billing methods. | Offers more favorable pricing compared to Pay-as-you-go, with additional discounts for yearly subscriptions. | Prices fluctuate with market supply and demand, and can be as low as 10% of the pay-as-you-go price. | Offers more favorable pricing compared to Pay-as-you-go, but slightly higher than the hourly unit price of monthly subscriptions. |
Applicable scenarios | Short-term business scenarios with significant growth, such as limited-time shopping events. | Stable long-term businesses. | Stateless application scenarios, such as stateless web site services, image rendering, offline analysis, and large-scale parallel computing. | Predictable one-off, cyclical elastic scenarios, such as e-commerce promotions, big data, online education/games, etc.; Elastic offline businesses that can wait, such as scientific computing and offline rendering. |
Changing instance type | Not supported. | Not supported. | ||
Changing billing method | Not supported. | Not supported. | ||
Stopping instance | If you stop an instance but do not release the ECS resources, the instance continues to incur charges. Instances with the Economical Mode enabled will not incur charges for compute resources after being stopped. | Billing continues even after the instance is stopped. The Economical Mode is not available. | If you stop an instance but do not release the ECS resources, the instance continues to incur charges. Instances with the Economical Mode enabled will not incur charges for compute resources after being stopped. | Charges continue even after the instance is stopped. The Economical Mode is not available. |
Deleting instance | You can delete an instance at any time. | When a subscription instance expires or you unsubscribe to it, you can manually delete the instance within the resource retention period. Instances that are not renewed will be automatically released. | You can delete an instance at any time. The system may automatically release the instance due to market price changes or insufficient instance inventory. | You can delete an instance at any time. |
Deduction method | Description | Payment |
Deduction method | Description | Payment |
A voucher with the ability to deduct and reserve, which can be used to deduct the bill for compute resources required by Pay-as-you-go instances (excluding spot instances). You can also use it to reserve resources to ensure a stable supply.
| Full prepayment, with all fees paid in a one-off purchase. |
Business scenario type | Scenario characters | Scenario example | Recommended billing method |
Business scenario type | Scenario characters | Scenario example | Recommended billing method |
Stability | Businesses are not interconnected and are overall stable, with no significant traffic fluctuations. | For example, multiple cloud exhibition projects that are not interconnected. |
|
Interconnection | Businesses are interconnected, and as traffic increases, the resource demands of each business grow simultaneously. | Stable online businesses, such as internal OA systems. | Pay-as-you-go + Reserved Instances (RI) |
Surge | Businesses are not interconnected and short-term burst activities are involved. | Scenarios such as hot events, limited-time shopping, virtual concerts, and holiday celebrations, where there can be thousands or even tens of thousands of concurrent users. |
|
Hybrid deployment | Multiple businesses with different requirements for computing power and priorities at different times. | Blue-green deployment, online/offline, and job-based hybrid deployments. |
|