- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- Topic Management
- Subscription Management
- Message Template Management
- SMN Operation Recording
- Logs
- Permissions Management
- Quotas
- Appendix
- API Reference
- SDK Reference
-
FAQs
- What Are the Advantages of SMN?
- What Protocols Does SMN Support?
- How Is SMN Billed?
- What Are the Requirements for an SMN Topic Name?
- How Many Topics Can I Create?
- How Many Subscriptions Can Be Added to a Topic?
- How Many Messages Can Be Published to a Topic?
- How Many Message Templates Can I Create?
- What Are the Limitations on SMS Messages?
- Can I Add Subscriptions Using Multiple Protocols to a Topic?
- Can a Topic Creator Change Subscription Protocols in a Topic?
- Can I Change a Subscription Endpoint for a Topic?
- Can I Delete a Published Message?
- Does SMN Ensure That Messages Are Received by Subscription Endpoints?
- Will a Subscriber Receive the Same Message Multiple Times?
- Why Do Subscribers Fail to Receive Messages After I Publish Messages to a Topic?
- What Can I Do When Pictures in an Email Message Cannot Be Displayed?
- How Do I Obtain My Account ID?
- How Does DingTalk, Lark, or WeCom Chatbot Obtain Subscription Endpoints?
- Videos
Show all
Service Advantages
SMN has the following advantages over any traditional messaging systems.
Item |
SMN |
Traditional Messaging System |
---|---|---|
Simplicity |
SMN provides three basic APIs to create topics, add subscriptions, and publish messages and can be quickly integrated with your services. It enables you to send messages in substantial quantity and do not require highly skilled development. |
A self-developed messaging system is expensive and takes long time to be integrated with your services. Its APIs are complicated and hard to use. |
Stability and reliability |
SMN stores messages in multiple data centers and supports transparent topic migration. Once a message fails to deliver, SMN saves it in a message queue and tries to deliver it again. If one service node is faulty, your requests are automatically processed by another available node. |
A traditional messaging system cannot achieve the stability and reliability required by critical services and does not provide measures to ensure service continuity. |
Multiple message types |
You publish a message once, and SMN delivers it to endpoints in various message types. |
You need to develop separate messaging systems in multiple types to send SMS message, email, HTTP, or HTTPS notifications. |
Security |
SMN isolates data based on topics and does not allow any unauthorized users to access message queues, thereby protecting your service data. |
Service data is potentially exposed to unauthorized access due to lack of effective protection mechanisms. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.