Lightweight message queue (original MNS)

      Lightweight message queue (original MNS)

      Lightweight Message Queuing (formerly MNS) is a message queue service that is easy to integrate, highly concurrent, and elastically scalable. The lightweight queue model, pay as you go billing model, and the elastic scalability to automatically adapt to high concurrency enable developers to quickly build a distributed loosely coupled system at low cost and efficiently deliver data and notification messages.

      • Minimal queue model

        The simplest queue model, together with a lightweight HTTP RESTful interface and a multilingual SDK, facilitates efficient integration.
      • Message channel between cloud products

        Lightweight and easy to integrate, it is the preferred channel for reliable message transmission between cloud products and between cloud products and user applications.
      • Lossless release capability

        Ensure that when the product server restarts due to change, release, operation and maintenance and other reasons, the client is unaware and the request is error free.
      • Flexible pay as you go

        Easily respond to sudden high concurrency requests, pay as you go, and do not need capacity evaluation and reserved instances, reducing costs and increasing efficiency.
       Preview
      Product Introduction
       Product introduction pictures

      Lightweight Message Queuing (formerly MNS) is a message queue service that is easy to integrate, highly concurrent, and elastically scalable. It uses a simple queue/topic model, provides a standard HTTP RESTful API interface, and supports SDKs in multiple programming languages to ensure compatibility and flexibility. The availability of this service is up to 99.95%, and it supports high availability deployment across availability zones to ensure the stability of the business. Users only need to pay according to the actual usage, without reserving resources, and the system will automatically adapt to the high concurrency requirements, thus helping users reduce costs and improve operation and maintenance efficiency.

      Product advantages

      Lightweight message queue model

      Easy access and integration
      Provide simpler and lightweight message queues, and focus on building core capabilities in the message field. It provides a lightweight Queue/Topic resource model, which is simple and easy to use without complex model concepts; It provides a lightweight HTTP RESTful interface, which natively supports the HTTP protocol and is independent of the platform; Multi language SDKs: C++, Java, C #, Python, PHP, golang (the third party), Node.js (the third party).

      Lossless release capability

      Ensure that when the product server restarts due to change, release, operation and maintenance, the client is unaware and the request will not have errors
      When the product service restarts due to changes, releases, operation and maintenance and other reasons, realize a smooth transition of the service, ensure that the client has no awareness and requests without interruption or error reporting, ensure that the user's business remains stable, and truly realize a "seamless" experience of service restart.

      High flexibility and low cost

      Support sudden high concurrency requests, pay as you go, no capacity assessment, cost reduction and efficiency increase
      The lightweight message queue has a strong traffic scheduling capability, which can easily respond to sudden high concurrency requests. It uses the pay as you go billing method, without reserving any instance resources, and only charges according to the actual usage, out of the box, effectively reducing costs and improving operation and maintenance efficiency.

      Stable, safe and reliable

      Address service availability and security issues
      Service availability is up to 99.95%, supporting high availability of multi zone services; At the same time, it provides multi-layer security protection and anti DDoS attacks, and fully supports access control (RAM) to centrally manage service and resource access; Support multi-user isolation mechanism, and each user has an independent namespace.
      Product Functions
       Card Head Diagram
      Queue model
      The lightweight queue model provides a lightweight HTTP RESTful interface, supports multi language SDKs, and supports the configuration of message visibility timeout, save duration, timing time, long rotation training time and other attributes.
       Card Head Diagram
      Topic model and subscription channel
      The topic model supports adding subscription configurations for each channel. Messages in the topic can be pushed to five subscription channels: HTTP, queue, SMS, email, and mobile terminal. Messages of a topic can be pushed to different subscription channels through different tags.
       Card Head Diagram
      OSS event subscription
      You can push file change events in the object storage service (OSS, Object Storage Service) to the specified message subject or queue by configuring event subscription rules. Business applications can consume these messages to process corresponding file change events.
      Get started quickly

      Quick Start Lightweight Message Queuing (formerly MNS)

      Fast experience: create queues through the lightweight message queue (original MNS) console, send and receive messages, and realize one-to-one consumption mode; Then create a topic, deliver the message to the queue, and implement the one to many publish and subscribe mode.

      Best Practices
      Hands on Practice

      Use lightweight message queue (original MNS) subscription object to store OSS events for real-time processing of file changes

      When you need to perform real-time processing, synchronization, listening, business triggering, logging and other operations on file changes in AliCloud object storage OSS, you can customize the files of interest by setting OSS event notification rules, and push OSS events to the lightweight message queue (the original MNS) In the queue or topic of, the developer's service consumes messages for subsequent business processing.

      Experience now
      Hands on Practice

      Realize customized data multi-channel alarm through lightweight message queue (original MNS) topic HTTP subscription+ARMS

      This scenario distributes customized alarm information to multiple notification channels at the same time, such as SMS, email and nail groups. By adopting the HTTP subscription mode of the topic model of lightweight message queue (formerly MNS), and combining with the customized integration capability provided by the application real-time monitoring service ARMS, you can realize the above multi-channel synchronous notification function in a simple configuration mode.

      Experience now
      Product pricing

      The lightweight message queue (the original MNS) is billed according to the actual usage, without reserving any instance resources, and provides a saving plan to help you save use costs.

      Billing method

      The lightweight message queue (the original MNS) supports pay as you go billing based on the number of requests to call the client's topic/queue related interface and the number of topics/queues. There is a quota of 20 million free requests per month. If the quota is exceeded, it will be charged according to the actual number of requests exceeded.

      • Pay as you go

        Pay as you go according to the number of API requests and the number of resources.
        View details
      • Savings plan

        The savings plan is a kind of discount benefit plan. The more committed consumption amount, the more discount. It is valid for one year.
        View details
      Security Compliance

      disaster recovery

      Service multi zone high availability: The service is highly available in multiple zones. When a zone is unavailable, the service can still be accessed normally through the original access point.

      Data replication: Message service provides data integration capability. It can dump data to similar storage or other storage by configuring data inflow and outflow tasks to quickly realize cross regional backup of message data.

      data security

      Transmission encryption: Provide the service of message encryption transmission on the public network HTTPS.

      Three copies of data storage: The message data of the message service is stored in three copies.

      access control

      RAM Policy: RAM Policy is a user based authorization policy. Users can use the RAM Policy to set the access permissions of the related resources under their names.

      Access Point: Configure different access points for different users to reduce the complexity of access management for large-scale shared datasets.

      common problem
      Q: What can the lightweight message queue (the original MNS) do?
      A: 1. Integrate the lightweight message queue (the original MNS) with other AliCloud products to make applications more reliable and flexible. two The lightweight message queue (formerly MNS) is used as the work queue, where each message represents a task and needs to be completed through a process. One or more ECS View details
      Q: Does the lightweight message queue (the original MNS) support long polling?
      A: The lightweight message queue (formerly MNS) supports long polling. Compared with the traditional short polling, the long polling will only return a response when the message enters the queue or the long polling times out. As soon as messages are available, long polling can retrieve messages from your queue in a simple and economical way. View details
      Q: What operations does the lightweight message queue (the original MNS) provide?
      A: The available operations provided by the lightweight message queue (the original MNS) include those related to the lifecycle management of queues, topics and subscriptions, as well as those related to the sending, receiving and management of messages. It supports operations through the console and API calls. View details
      Q: Continue billing after deleting the queue
      A: If you no longer need to use a queue, after deleting the queue, the resource usage fee of the queue will no longer be charged from the day after the deletion. At the same time, you need to stop all API requests for the queue. Otherwise, the lightweight message queue (the original MNS) will still make API requests for times ..... View details
      Q: Continue billing after deleting the subject
      A: If you no longer need to use a topic, after deleting the topic, you will no longer be charged the resource usage fee for the topic from the day after the deletion, and you need to stop all API requests for the topic, otherwise the lightweight message queue (the original MNS) will still follow the API request times ..... View details
      Q: After the subscription to the lightweight message queue (the original MNS) is successful, no messages can be received, and no relevant records can be found in the log
      A: It may be that the FilterTag parameter is configured during subscription. This parameter describes the tag of message filtering in the subscription. Messages with consistent tags will be pushed. Please check the documentation for solutions. View details
      Q: Signature authentication failed when using the HttpEndpoint interface of the lightweight message queue (original MNS)
      A: When using some HttpServer frameworks, the framework may convert the parameters in the HttpHeader to the format, resulting in signature authentication failure. Please check the documentation for solutions. View details
      Q: "Message not exist" error when deleting messages in the lightweight message queue (original MNS)
      A: Because the VisibilityTimeout expires, the ReceiptHandle of the message becomes invalid, causing the message deletion to fail. Please check the documentation for solutions. View details
      You cannot try this product for the moment. View all trials

      Want to experience more product features?

      Buy Now Lightweight message queue (original MNS) product

      Learn more about AliCloud products?

      explore Alibaba Cloud products Learn more about product introduction

      Need help when encountering difficulties?

      contact us Consult Alibaba Cloud service team