Scenario
In the following scenarios, the Kafka billing mode needs to be changed from pay-as-you-go to yearly/monthly:
When you use Kafka, you may need to change the billing mode from pay-as-you-go to yearly/monthly, for example:
l Message accumulation: If there is a large message accumulation in Kafka, the consumption speed can be out of pace with the production speed, which affects the performance and stability of the system. To solve this problem, you can change the billing mode from pay-as-you-go to yearly/monthly to package a certain number of messages into a batch for consumption, so as to improve the consumption efficiency and throughput.
l Fluctuating business traffic: In some business scenarios, the traffic may be volatile. The message production speed is fast in one time period and slow in another. To better adapt to fluctuations in business traffic, you can change the billing mode from pay-as-you-go to yearly/monthly to flexibly consume messages in batches based on actual message production.
l System resource optimization: When Kafka consumer resources are limited, you can change the billing mode from pay-as-you-go to yearly/monthly to optimize resource utilization. By packaging a certain number of messages into a batch for consumption, you can reduce consumer competition and context switching, improving the concurrency processing capacity.
l Message processing latency optimization: In some scenarios, the requirements for real-time performance are low, and you can change the billing mode from pay-as-you-go to yearly/monthly to optimize the message processing latency. Packaging a certain number of messages into a batch for consumption reduces the number of times the messages are processed, thus reducing the message processing latency.
It should be noted that when you change the billing mode from pay-as-you-go to yearly/monthly, you should make adjustments based on your actual business requirements and system conditions. At the same time, factors such as the importance of messages, the processing power of consumers, and the resource constraints on the system should be considered to ensure the stability and performance of the system.
Procedure
(1) Log in to the management console.
(2) Go to the Kafka console.
(3) In the operation column of the instance list page, click More in the target instance row, and click Change to Pay-as-you-go upon Expiration or Change to Yearly/Monthly.
(4) Change to pay-as-you-go upon expiration.
(5) Change to yearly/monthly.
(6) Click Change to Yearly/Monthly, and a new page will open. Select the duration of the subscription, and the system will calculate the price, click Pay Now to jump to the payment page.
