Message Queue for Apache RocketMQ provides HTTP client SDKs for multiple programming languages. You can use the HTTP client SDKs to connect to Message Queue for Apache RocketMQ over the Internet. This topic describes the release notes for HTTP client SDKs for multiple programming languages.

SDKs for multiple programming languages

Message Queue for Apache RocketMQ supports RESTful HTTP communication and provides SDKs for seven programming languages. More features are developed for HTTP client SDKs to align with the features that are supported by TCP client SDKs. For more information about the differences between the features of HTTP client SDKs and TCP client SDKs, see the following topics:

Additional considerations

  • Only Message Queue for Apache RocketMQ instances can be accessed by using HTTP client SDKs. This is an enhanced feature that is provided by Message Queue for Apache RocketMQ. You cannot use HTTP client SDKs to access self-managed Apache RocketMQ instances.
  • Make sure that the resources that you want to access is in the same region as the HTTP endpoint that you use.

    For example, if your Message Queue for Apache RocketMQ instance is deployed in the China (Hangzhou) region, you can access the instance only by using an endpoint of the China (Hangzhou) region. You can access the instance in the following scenarios:

    • If your client is located in the China (Hangzhou) region, we recommend that you use the private HTTP endpoint of the instance to access the instance.
    • If your client is not located in the China (Hangzhou) region, make sure that your client can connect to the Internet and use the public HTTP endpoint of the instance to access the instance.
  • Messages can be transmitted between TCP and HTTP clients. The message information such as attributes, content, tags, and keys must comply with XML rules because HTTP uses XML serialization.
    Note For more information about XML rules, see XML syntax. You can also use the third-party tool xml_validator based on your business requirements to check whether your messages comply with XML rules. For more information about xml_validator, see XML Validator.

    If messages contain characters that do not comply with XML rules, the following errors may occur:

    • Messages fail to be sent over HTTP.
    • TCP messages fail to be consumed over HTTP.

    You can use Base64 to encode or decode messages that do not comply with XML rules.