Simple Message Queue (formerly MNS) provides API operations for two messaging models: queues (point-to-point) and topics (publish/subscribe). You can call these operations by using client SDKs.
Queue messaging
Queue messaging uses a producer-consumer pattern. A producer sends messages to a queue, and a consumer receives and processes them.
API operation | Description | Call method |
Sends a message to a queue. | SMQ console or OpenAPI Explorer | |
Sends multiple messages to a queue in a single request. | OpenAPI Explorer | |
Receives a message from a queue (destructive read). The message enters the Inactive state and becomes invisible to other consumers until the inactive period expires. | SMQ console or OpenAPI Explorer | |
Receives multiple messages from a queue in a single request. Each message enters the Inactive state. | OpenAPI Explorer | |
Deletes a consumed message from a queue. Call this operation after you process a message received through ReceiveMessage. | SMQ console or OpenAPI Explorer | |
Deletes multiple consumed messages from a queue in a single request. | OpenAPI Explorer | |
Reads a message from a queue without changing its state (non-destructive read). The message remains visible to other consumers. | OpenAPI Explorer | |
Reads multiple messages from a queue without changing their state. | OpenAPI Explorer | |
Modifies the inactive period of a consumed message. Use this operation to extend processing time or release a message early for other consumers. | OpenAPI Explorer |
Topic messaging
Topic messaging uses a publish/subscribe pattern. A publisher sends messages to a topic, and the topic delivers copies to all subscribed endpoints.
API operation | Description |
Publishes a message to a topic. The topic delivers the message to all subscribed endpoints. |