Normal messages are the basic message type in ApsaraMQ for RocketMQ. Unlike specialized types such as scheduled, delayed, ordered, and transactional messages, normal messages have no timing constraints, ordering guarantees, or transaction support. Use normal messages when your application needs straightforward message delivery without these additional semantics.
Each topic supports only one message type. A topic created for normal messages can only send and receive normal messages. Do not mix message types within a single topic. Mixing message types can cause operational issues, such as loss of scheduled messages during an endpoint change or instance migration.
TCP client SDK sample code
HTTP client SDK sample code
ApsaraMQ for RocketMQ supports RESTful HTTP communication. The following table lists the available HTTP client SDKs.
| Language | Release notes |
|---|---|
| Go | SDK for Go |
| Python | SDK for Python |
| Node.js | SDK for Node.js |
| PHP | SDK for PHP |
| Java | SDK for Java |
| C++ | SDK for C++ |
| C# | SDK for C# |
For HTTP SDK sample code, see the ApsaraMQ for RocketMQ HTTP SDK samples repository on GitHub.
For a complete list of HTTP client SDK versions, see Release notes.