How does RocketMQ compare to Kafka?

Both handle high-throughput messaging. RocketMQ has stronger transactional message support and natively-supported delay queues, which are useful for specific patterns. Kafka has a broader ecosystem and is more common outside China. Alibaba Cloud also offers managed Kafka if you need Kafka-specific features.

What's an ordered message?

Ordered messages are delivered to consumers in the same order they were published — within a partition. This is useful for workloads where event order matters (e.g., order state transitions). The trade-off is reduced parallelism: ordered consumption per partition means single-threaded processing per partition. Use ordered only when you actually need the order guarantee.

Alibaba Message Queue Config Builder

ServerlessAlibaba Cloud

Build Message Queue configurations with topics, consumer groups, message types, and retry policies.

Last verified: May 2026

Alibaba Cloud Message Queue for Apache RocketMQ Configuration

Build Message Queue configurations with topics, consumer groups, message types, retry policies, and VPC networking.

Required Fields

instanceNametopics

{
  "instanceName": "prod-mq-instance",
  "instanceType": "STANDARD",
  "regionId": "cn-hangzhou",
  "topics": [
    {
      "topicName": "order-events",
      "messageType": "NORMAL",
      "description": "Order lifecycle events",
      "maxMessageSize": 65536,
      "tags": [
        { "key": "Domain", "value": "orders" }
      ]
    },
    {
      "topicName": "payment-events",
      "messageType": "TRANSACTION",
      "description": "Transactional payment messages"
    },
    {
      "topicName": "scheduled-tasks",
      "messageType": "DELAY",
      "description": "Delayed and scheduled task messages"
    }
  ],
  "consumerGroups": [
    {
      "groupId": "GID_order_processor",
      "consumeModel": "CLUSTERING",
      "subscriptions": [
        {
          "topic": "order-events",
          "expression": "created || updated || cancelled",
          "expressionType": "TAG"
        }
      ],
      "retryPolicy": {
        "maxReconsumeTimes": 16,
        "groupRetryPolicy": "DefaultRetryPolicy"
      }
    },
    {
      "groupId": "GID_payment_processor",
      "consumeModel": "CLUSTERING",
      "subscriptions": [
        {
          "topic": "payment-events",
          "expression": "*",
          "expressionType": "TAG"
        }
      ]
    }
  ],
  "networkConfig": {
    "vpcId": "vpc-bp1qpo0kug3a20qqe****",
    "vSwitchId": "vsw-bp1s5fnvk4gn2tws0****",
    "enableInternetAccess": false
  }
}

Generated Output

Output will appear here...

See It in Action

Your e-commerce platform has a long-standing dual-write problem: orders sometimes commit to the database but the downstream notification never goes out (or vice versa). You introduce transaction messages — the message is staged with the database commit, and only confirmed for delivery after the commit succeeds. Within a sprint, the dual-write data inconsistencies stop and the team has a reusable pattern for similar problems.

What This Tool Does

Alibaba Cloud Message Queue offers RocketMQ-based messaging — topics, consumer groups, message types (normal, ordered, transaction, delay), and retry policies. The Message Queue Config Builder generates topic and consumer-group configurations including message type, partition count, retention, and consumer behavior. Output is Terraform-ready and matches `alicloud_ons_topic` and related resources.

Technical Details

The builder collects instance, topic name, message type (Normal, Order, Transaction, Delay), retention, and consumer group configuration. It validates the message type against the consumer group's expected behavior and emits `alicloud_ons_instance`, `alicloud_ons_topic`, and `alicloud_ons_group` Terraform resources.

Common Use Cases

1Provisioning a new RocketMQ topic for an application's event stream with appropriate partition count for consumer parallelism.
2Setting up a consumer group with the right max retry count and retry interval for the workload's failure tolerance.
3Using transaction messages to coordinate database commits with event publishing — solving the dual-write problem.
4Configuring a delay queue for scheduled work (process this message 5 minutes from now) without a separate scheduler.

Common Questions

How does RocketMQ compare to Kafka?: Both handle high-throughput messaging. RocketMQ has stronger transactional message support and natively-supported delay queues, which are useful for specific patterns. Kafka has a broader ecosystem and is more common outside China. Alibaba Cloud also offers managed Kafka if you need Kafka-specific features.
What's an ordered message?: Ordered messages are delivered to consumers in the same order they were published — within a partition. This is useful for workloads where event order matters (e.g., order state transitions). The trade-off is reduced parallelism: ordered consumption per partition means single-threaded processing per partition. Use ordered only when you actually need the order guarantee.

Expert Tips

TIP

Match partition count to your peak consumer parallelism. A topic with 8 partitions and a consumer group with 16 consumers wastes half the consumers — there's no way to consume one partition with multiple consumers.

TIP

Use transaction messages for the dual-write problem (commit to database + publish event must both succeed or both fail). They're harder to get right than they look in isolation but solve real problems.

Was this tool helpful?

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.