# Service Advantages

SMN has the following advantages over any traditional messaging systems.

Table 1 SMN advantages
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 messaging 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.

Parent topic: Overview