After a Message Queue for MQTT instance is upgraded from V2.x.x to V3.x.x, it does not need to be bound with a Message Queue for Apache RocketMQ instance. This topic describes the differences in console instance-related operations between the two versions. It also provides console screenshots for explicit comparison.

Change description

Message Queue for MQTT of V3.x.x implements independent message storage. In other words, after a Message Queue for MQTT instance is purchased and activated, you can directly create and use resources without binding the instance to any other cloud services. For this matter, you can better understand it if you send and receive messages only by using the MQTT protocol.

For more information about change description, see Changes in using resources.

Note You can determine whether your instance version is V2.x.x or V3.x.x based on the Kernel version field on the Instance Information tab of the Instances page in the console.

Console usage changes

The difference between V2.x.x and V3.x.x is that you do no need to bind a Message Queue for MQTT instance with a Message Queue for Apache RocketMQ instance, while Message Queue for MQTT implements independent storage. Therefore, the instance creation processes for the two versions are different. The following figures show the screenshots of some examples.

  • V2.x.x
    1. Create a Message Queue for MQTT instance.

      After the instance is created, you must make further configuration, that is, bind the instance with a Message Queue for Apache RocketMQ instance. At this point, you cannot obtain the endpoint of the Message Queue for MQTT instance.

    2. Bind the Message Queue for MQTT instance with a Message Queue for Apache RocketMQ instance.

      Select the Message Queue for Apache RocketMQ instance for binding.

      After the binding succeeds, you can view the following information including the instance endpoint.
      Note You can see the contents highlighted in red boxes only in V2.x.x.
  • V3.x.x
    In V3.x.x, after a Message Queue for MQTT instance is created, you do not need to bind it with a Message Queue for Apache RocketMQ instance. Instead, you can immediately obtain the corresponding endpoint for sending and receiving messages.
    Note To connect Message Queue for MQTT with other Alibaba Cloud services, you must follow relevant rules. For more information, see Data exchange across services.

References

For more information about instance operations in the console, see Instance management.