ApsaraMQ for RocketMQ offers two Serverless instance editions with different billing models and feature sets:
Standard/Professional: Pay-per-use with separate PrivateLink billing.
Shared/Dedicated: Lower unit prices, free resource quotas, and built-in PrivateLink at no extra cost.
The following sections compare billing between the two editions and walk you through upgrading from Standard/Professional to Shared.
Before you upgrade
Review these billing and operational implications before starting the upgrade.
After the upgrade, the PrivateLink endpoint address changes. Update all producer and consumer applications to use the new endpoint.
If any application continues to use the old endpoint, PrivateLink traffic fees keep accruing.
Even after all applications switch to the new endpoint, PrivateLink instance fees continue until you delete the old endpoint.
Billing comparison
PrivateLink fees
| Edition | PrivateLink fees |
|---|---|
| Standard/Professional | Billed separately by the PrivateLink service |
| Shared/Dedicated | No additional fees. This significantly reduces costs for PrivateLink traffic processing. |
Billing methods
| Edition | Available billing methods |
|---|---|
| Standard/Professional | Cumulative amount |
| Shared/Dedicated | Cumulative amount, or Reserved + Elastic |
Instance fees
| Edition | Instance fee |
|---|---|
| Standard/Professional | None |
| Shared/Dedicated | Applies only to Shared instances that use pay-as-you-go billing |
Resource fees
| Edition | Billed resources | Unit price | Free quota |
|---|---|---|---|
| Standard/Professional | Topics only | Higher | None |
| Shared/Dedicated | Topics and consumer groups | Lower | 100 to 3,000 units. See Instance type limits. |
Concurrent online clients
| Edition | Unit price | Free quota |
|---|---|---|
| Standard/Professional | None | N/A |
| Shared/Dedicated | Lower | 500 to 100,000 clients. See Instance type limits. |
Avoid creating a new producer instance for each message sent. This pattern inflates the online client count and increases costs.
Upgrade from Standard/Professional to Shared
Step 1: Upgrade the instance
Open the Instance Details page.
Click Upgrade.
Set Primary Edition to Shared.
Confirm the upgrade.
Step 2: Switch to the new endpoint
When the edition changes to Shared, the PrivateLink billing model shifts from service consumer to service provider. This changes the VPC endpoint address.
After the upgrade completes, the Endpoint and Network Information section on the Instance Details page shows two VPC endpoints:
The endpoint marked To Be Unpublished -- the old endpoint under the service consumer billing model. This endpoint will be deprecated.
The unmarked endpoint -- the new endpoint under the service provider billing model. Switch to this one.
To switch:
Update the endpoint address in all producer and consumer application configurations. Replace the old address (marked To Be Unpublished) with the new endpoint address.
Restart each application to apply the change.
Both endpoints point to the same RocketMQ instance during the transition. Message sending and receiving are not interrupted.
Step 3: Delete the old endpoint
After all applications are running stably on the new endpoint:
Return to the Instance Details page.
Delete the endpoint marked To Be Unpublished.
Until you delete the old endpoint, PrivateLink instance fees continue to accrue -- even if no application uses it.
FAQ
Does the upgrade interrupt message sending or receiving?
No. During the transition, both the old and new endpoints point to the same RocketMQ instance. Message sending and receiving continue without interruption.
Can I keep using the old endpoint after the upgrade?
The old endpoint remains functional during the transition, but continued use generates PrivateLink traffic fees. Switch all applications to the new endpoint as soon as possible, then delete the old endpoint.
What happens to in-flight messages during the upgrade?
Both endpoints point to the same RocketMQ instance during the transition. The upgrade changes the billing model and endpoint address, so message sending and receiving continue without interruption.