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 instance management in the console between the two versions. This topic 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 create and use resources without the need to bind the instance to other cloud services. You can better understand this matter if you send and receive messages only by using the MQTT protocol.

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

Note You can check whether the version of your instance is V2.x.x or V3.x.x based on the value of the Kernel Version parameter on the Instance Details page in the console.

Operation changes in the console

Different from Message Queue for MQTT of V2.x.x, Message Queue for MQTT of V3.x.x implements independent storage. You do no need to bind a Message Queue for MQTT instance of V3.x.x with a Message Queue for Apache RocketMQ instance. Therefore, the instance creation processes for the two versions are different. The following figures show the screenshots of the different instance creation processes.

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

      After the instance is created, you must make further configurations to 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.

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

      Select the Message Queue for Apache RocketMQ instance that you want to bind.

      After the binding succeeds, you can view the following information including the endpoint of the Message Queue for MQTT instance.
      Note You can see the information that is framed in red 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. In addition, you can immediately obtain the endpoint of the Message Queue for MQTT instance and use the endpoint to send and receive messages.
    Note To exchange data between Message Queue for MQTT and other Alibaba Cloud services, you must use rules. For more information, see Exchange data across cloud services.

References

For more information about instance-related operations in the console, see Manage instances.