This topic explains the billing differences between the RocketMQ Serverless legacy Standard/Professional mode and the shared pay-as-you-go mode. It also describes how to identify your instance type, view billing rules, and smoothly upgrade to the shared edition.
Legacy Standard and Professional Editions
The Serverless edition has evolved as follows:
Legacy instances: The shared pay-as-you-go billing mode no longer distinguishes between Standard and Professional editions. Both are consolidated into a single shared pay-as-you-go billing model.
New instances: Three billing modes are available: shared pay-as-you-go, shared reserved + elastic, and dedicated reserved + elastic.
How to Identify Whether Your Instance Is a Legacy Standard/Professional Edition
On the RocketMQ console, go to Instances > Instance Details > Basic Information and check the following fields:
If Primary Edition displays Standard or Professional, the instance is a legacy Standard/Professional instance.
If Primary Edition displays Shared, the instance is a new shared instance. In this case, check the Capacity Type field to determine whether the billing mode is pay-as-you-go or reserved + elastic.
Billing for Legacy Standard/Professional Editions
For billing details of legacy Standard/Professional editions, see Billing for legacy Serverless Standard and Professional Edition instances.
Feature comparison
Comparison Item | Standard/Professional Edition | Shared/Pay-as-you-go |
PrivateLink fees | Additional fees apply. Billing is handled by the PrivateLink service. | No additional fees. This significantly reduces costs for PrivateLink traffic processing. |
Billing method | Cumulative Amount |
|
Instance fee | None | Instance fees apply only to Shared instances that use the pay-as-you-go billing method. |
Resource fees |
|
|
Number of concurrent online clients | None |
Note Avoid abnormal usage patterns, such as creating a new producer instance for each message sent. This can lead to an excessive number of online clients. |
How to upgrade from a Standard/Professional Edition to the Shared Edition
Upgrade the instance to the Shared Edition: On the Instance Details page, click the Upgrade button. Set Primary Edition to Shared, and then confirm the upgrade.
Switching endpoints after upgrading to the Shared type:
When you upgrade an instance to the Shared type, the payer for PrivateLink changes from the service consumer to the service provider. This change causes the endpoint address to change. To ensure a smooth transition for sending and receiving messages and to avoid unnecessary PrivateLink fees, follow these steps:
After the upgrade, identify the endpoints:
After the upgrade is successful, you will see two endpoints for the VPC in the Endpoint and Network Information section on the Instance Details page.
The endpoint marked (Deprecated): This is the old endpoint from the service consumer billing model. This endpoint will be deprecated.
The unmarked endpoint: This is the new endpoint for the service provider billing model. Switch to this endpoint.
Switch the client configuration and restart:
Modify the configuration for all your producer and consumer applications.
Replace the old endpoint address (the one marked (Deprecated)) with the new service provider endpoint address.
Restart these applications one by one to apply the new configuration.
Note: Both endpoints point to the same RocketMQ instance during the switch. The process is seamless and does not interrupt the service.
Delete the old endpoint (critical step):
After you confirm that all producer and consumer applications have successfully switched to the new endpoint and are running stably, return to the Instance Details page.
Find and delete the old endpoint marked (Deprecated).
ImportantIf any client continues to use the old endpoint, fees for PrivateLink traffic will continue to be generated.
Even after all clients have switched, PrivateLink instance fees will continue to be generated until the old endpoint is deleted.