Serverless ApsaraMQ for RocketMQ instances support quick resource scaling based on business workloads. For serverless ApsaraMQ for RocketMQ instances, resources are allocated and computing fees are billed based on your actual usage to reduce costs. This topic describes the working mechanism and benefits of serverless ApsaraMQ for RocketMQ instances. This topic also describes common scenarios in which serverless ApsaraMQ for RocketMQ instances can be used.
Background information
As an important part of the IT systems of modern enterprises, message-oriented middleware can help implement business decoupling and peak-load shifting.
To ensure business stability, resources in message-oriented middleware, including CPUs, memory, storage space, and network traffic, are configured based on peak business workloads. As a result, most resources in message-oriented middleware are idle during actual usage. This causes resource waste.
Serverless ApsaraMQ for RocketMQ instances help resolve the preceding issue by supporting quick resource scaling based on actual business workloads. This helps reduce resource waste. You are charged for serverless ApsaraMQ for RocketMQ instances based on your actual usage, which reduces your O&M workloads and usage costs.
The following figure shows the changes in the specification usage of non-serverless (subscription and pay-as-you-go) and serverless instances in scenarios in which business workloads fluctuate.
For information about the instance editions and specifications of ApsaraMQ for RocketMQ, see Instance specifications.
Benefits
Serverless ApsaraMQ for RocketMQ instances provide flexible resource scalability to meet resource requirements at different business stages. Serverless ApsaraMQ for RocketMQ instances provide the following benefits:
Out-of-the-box compatibility with open source Apache RocketMQ. When you use serverless ApsaraMQ for RocketMQ instances, you need to only focus on the development of core business code. This helps reduce your O&M costs.
Support for auto scaling. Resources on serverless ApsaraMQ for RocketMQ instances are dynamically adjusted and automatically scaled based on real-time business workloads. You do not need to estimate or configure instance specifications.
Billing based on actual usage. You are charged for serverless ApsaraMQ for RocketMQ instances based on your actual usage of messages, topics, network traffic, and storage space. Fees are settled on an hourly basis. This helps reduce costs.
Architecture of serverless ApsaraMQ for RocketMQ instances
Serverless ApsaraMQ for RocketMQ instances isolate resources among tenants to ensure the independent running of business on each instance.
All technical components of ApsaraMQ for RocketMQ are deployed in containers. This way, ApsaraMQ for RocketMQ can flexibly and easily assign underlying computing, storage, and network resources in the cloud.
Serverless ApsaraMQ for RocketMQ instances can quickly respond to changes in the resource requirements of each tenant and implement seamless auto scaling to meet your business requirements.
Common scenarios
Serverless ApsaraMQ for RocketMQ instances can be used in the following scenarios:
Scenarios in which message queue services are required by small and medium-sized businesses.
Development and test scenarios in which message queue services are infrequently used.
Scenarios in which business fluctuates or is unpredictable.
Limits
Serverless ApsaraMQ for RocketMQ instances are available only in the following regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Shenzhen), China (Chengdu), Singapore, Germany (Frankfurt), and US (Virginia).
Billing rules
For information about the billing rules of serverless ApsaraMQ for RocketMQ instances, see Billing of serverless instances.