Product specification

Message Service MNS

HTTP RESTful standard is adopted for convenient access
Resource package type
Queue resource occupancy package
Queue resource usage
60 days/time
Purchase duration
one month

Message Service MNS

HTTP RESTful standard is adopted, which is easy to access and has strong cross network capability
Queue resource usage
1000 days/time
Purchase duration
half a year
Purchase quantity
one

Message Service MNS

HTTP RESTful standard is adopted, which is easy to access and has strong cross network capability
Resource package type
Request Package
Request package specification
50 million times
Purchase duration
half a year

Product advantages

Lightweight queue
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).
Serverless
MNS is a standard serverless product, which can handle nearly unlimited concurrent requests without perceiving or configuring any cluster information in advance. It can be used out of the box; At the same time, it uses the post payment billing method, which does not need to reserve any instance resources, and only pays for the actual usage.
Safe and stable
In terms of stability, triple backup of data, with reliability of 99.999999999%; Service availability reaches 99.95%; Always Writable; At the same time, it provides multi-level security protection and anti DDoS attacks; Implement a multi-user isolation mechanism, and each user has an independent namespace; Fully support RAM: primary sub account, temporary AK; Support HTTPS and VPC access.
Advanced feature support
You can customize advanced features such as message delay, timed message, message body size, message life cycle, tag filtering, and retry dead letter. Provide a sound message product solution to help developers freely transfer data and notify messages between distributed components of applications, so as to build a loosely coupled system.

Product Functions

Queue model
Rich queue attribute configuration We provide a wealth of queue attribute configuration options. You can personalize queue attributes to meet different application scenarios, and support multiple queue modes such as ordinary queues, delay queues, and priority queues.
Support concurrent access It supports multiple producers and consumers to access the same queue concurrently. The concurrency can be adjusted freely without special settings, and it can ensure that a message cannot be obtained by other consumers within a specific period of time after retrieval.
Message delivery guarantee Ensure that the message can be successfully consumed at least once within the message validity period. Resource isolation between users ensures that messages in your queue will not be illegally obtained.
Topic
Support notification messages The server actively sends the message to the callback address (Endpoint) specified by the user, eliminating unnecessary polling and resource consumption of the client program.
Support one to many broadcast messages A notification message can be subscribed and consumed by multiple subscribers at the same time.
Support multiple delivery methods Support http/https, email, SMS, mobile terminal and other push methods.
Message delivery guarantee During the message validity period, ensure that messages published in Topic will be pushed to the user program according to the specified policy and format.

Application scenarios

Decoupling of trading system
Peak shaving and valley filling in high flow scenarios
Close Unpaid Orders
User information registration
Online lottery design
Task system design
Cross private network data exchange
Video system architecture
Decoupling of trading system
As the core transaction system of Taobao/Tmall master station, the generation of each transaction order data will attract the attention of hundreds of downstream business systems, including logistics, shopping carts, points, Alimama, stream computing analysis, etc. The overall business system is huge and complex. In order to ensure the continuity of the master station's business, a distributed architecture design must be adopted, Each system is decoupled.
Capable of providing
High availability loosely coupled architecture design
Through the loose coupling design of upstream and downstream business systems, even if the downstream subsystems (such as logistics, credit, etc.) are unavailable or even down, the normal operation of the core trading system will not be affected.
Flexibility to adapt to rapid business growth
When a new business system is added as required by the business, it will not affect the basic technical architecture changes, nor will it affect the normal operation of other systems.
Recommended combination
Peak shaving and valley filling in high flow scenarios
Satisfy that the business will bring high traffic pulse in special periods, such as the second kill, red packet grabbing, enterprise good start and other large-scale activities, to prevent the system from overloading or even crashing, or a large number of requests from failing to affect the user experience.
Capable of providing
Ultra high flow pulse processing capacity
MNS's ultra high performance message processing capability can withstand traffic pulses without being overwhelmed. While ensuring system availability, it improves the user experience due to fast and effective request response.
Massive message stacking capability
Ensure the smooth and stable operation of downstream business within the safe water level, and avoid the impact of ultra-high flow.
Reasonable cost control
The cluster scale of downstream business system can be controlled by reducing valley filling, thus reducing the input cost.
Recommended combination
Close Unpaid Orders
Business logic processing after the order has not been paid, and timing tasks are triggered; You can design timing messages through the queue: when creating an order inventory minus 1, send the timing message of the payment check task to the message service queue; The scheduled message is visible 30 minutes later, and the backend service consumes the message of the payment check task; You can also complete real-time notification through MNS: the back-end service checks the payment. If the order has not been paid, the order is rolled back, and the inventory is increased by 1.
Capable of providing
Create a scheduled message
For example, by creating a timing message, it can determine whether an order that has not been paid for over time in e-commerce transactions has been paid or needs to be closed; (Meet the business requirements of the time difference between message production and consumption.
Complete scheduled notification
For example, in the above scenario, a reminder message is sent to users for overdue unpaid orders (satisfying the business scenario design of triggering timed tasks through messages).
Recommended combination
User information registration
Form registration and other systems are synchronized to asynchronism to realize asynchronous notification; After successful registration, users need to send successful registration emails, new user credits, coupons, etc. To join MNS, the response speed of the main process user registration process can be improved, while non main process or non important tasks such as sending notifications can be processed asynchronously and collectively, and tasks can be aggregated and processed in batches.
Capable of providing
Reduce requests, improve efficiency and system parallelism, and improve system throughput
MNS notification function can call back and notify users when the backend service finishes processing tasks. This in turn reduces a large number of unnecessary polling requests between users, Web front-end and back-end services.
Design operation notice
Message push notification is one of the most frequently used operation methods. It can remind users of certain operations at a certain time node, such as new activity push, interesting news content reminder, or coupon notice delivery, to enhance user stickiness.
Recommended combination
Online lottery design
The architecture design of the online lottery system: access the front-end cluster of the lottery system, and the back-end management cluster of the lottery system randomly generates prize information and injects it into the prize queue; Randomly generate prize information: synchronize the winning information through two queues. The front end reads the prize information through the prize queue, judges the user's lottery request, and sends the winning information to the winning information queue after hitting; Lottery request determination and user notification: the back-end management cluster collects the winning information from the winning information queue, sends the notification message to the prize notification subject, and the prize notification subject pushes the prize notification SMS and email to the user, and notifies the real-time statistics system http callback for winning statistics.
Capable of providing
The front lottery system and the rear prize system are loosely coupled
Through the prize queue, users can draw online prizes and generate prizes randomly.
Complete the determination of winning, synchronization of winning messages and user notification
Through the combination of queue, topic and message, real-time push of user events is realized to ensure the timeliness of winning information.
Recommended combination
Task system design
Design the task system and complete the HTTP callback. Perform task calculation asynchronously through the queue: users submit task execution messages to the task queue; The task execution cluster consumes task messages in the task queue and executes computing tasks asynchronously; Real time notification is completed through MNS: when the calculation task is completed, send a notification message to the subject, and the subject asynchronously calls the http callback on the task management server, and sends an email and SMS to notify the user.
Capable of providing
Avoid solving the data peak caused by concurrent requests, and compress the response time of the venue page
For example, in the Double 11 Promotion, hundreds of thousands of commodities in each branch venue need to be aware of price changes in real time, and a large number of concurrent access databases are under great pressure.
Avoid limiting the access flow of product changes due to bandwidth bottlenecks, and notify the product data changes in real time
Recommended combination
Cross private network data exchange
Data between isolated intranets is exchanged through the public network.
Capable of providing
Data synchronization and exchange
There is no need to connect the intranet of enterprise A and B, nor to expose the intranet services of enterprise A. The message service, as a public message channel, realizes the data synchronization and exchange between enterprise A and enterprise B.
Flexible access policy setting
The message service has supported RAM access control and STS temporary authorization, and can flexibly set the access policy of public network queues.
Recommended combination
Video system architecture
Decoupling of video upload and video processing services: videos are uploaded to OSS, and OSS sends the video upload completion event message to the message task queue; The video processing completes the status update through MNS: the video processing service MTS reads the event message in the task queue, pulls the file according to the time message, performs video transcoding, re uploads the transcoding result, and sends a notification to the notification subject; Video listing: update data of video websites, and launch videos; CDN accelerates the new transcoding video to speed up the user viewing experience.
Capable of providing
Loose coupling design between multiple tasks to improve business concurrency
Multiple tasks are performed in sequence to ensure smooth business process
Recommended combination

Product Dynamics

New functions/specifications on February 10, 2016
Message service docking mobile push function
View details
2016-12-12 New Region/New Availability Zone
Hong Kong Data Center Officially Releases Message Service
View details
2016-12-12 New Region/New Availability Zone
[Message service] The theme mode of the message service of Japan Station was officially released and launched
View details
2017-02-08 New Region/New Availability Zone
Logistics cloud supports MNS queue, subject and notification functions
View details
2017-02-28 New Region/New Availability Zone
Topic model is launched on the international station
View details
New functions/specifications on March 30, 2017
Merging of message service and short message service
View details
2017-04-10 New Features/Specifications
Message Service iOS SDK Publishing
View details
2017-04-19 New region/new zone
Shenzhen Financial Cloud supports MNS SMS function
View details
2017-06-07 Price adjustment
New SMS resource package supports sending 300000 notification SMS
View details
2017-06-22 Function optimization
Add endpoint query entry to SMS overview page
View details
2017-08-04 New region/new zone
The message service OSS event notification function adds two regions, Hong Kong and the western United States.
View details
2017-10-27 New Region/New Availability Zone
The message service is open to Malaysia. The domestic station is consistent with other domestic stations, and the international station is consistent with other international stations
View details
2018-09-14 Price adjustment
MNS Billing Model Adjustment
View details
View all logs

More products and services

Cloud message queue RocketMQ version
Alibaba officially designates news products and creates financial news services with a mature, stable and advanced technical system to experience the perfect experience of Double 11 products.
Cloud message queue MQTT version
Mobile Internet, Internet of Things, interactive live broadcast native support, Internet of Things, two-way communication between end and cloud, support tens of millions of devices online at the same time.
Cloud message queue Kafka version
The cloud message queue Kafka version is the full hosting service of Apche Kafka, which has the characteristics of exclusive cluster deployment, operation and maintenance free, out of the box use, security and reliability.
Cloud Message Queue RabbitMQ
Compatible with AMQP standard protocol and RabbitMQ open source ecology and multilingual client, it is more secure and reliable, and can be used out of the box without operation and maintenance.

Documentation and Tools