A publisher sends messages to topics that they have created or to topics they have permission to publish.<\/p>\n
Instead of including a specific destination address in each message, a publisher sends a message to the topic.<\/p>\n
Amazon SNS matches the topic to a list of subscribers who have subscribed to that topic and delivers the message to each of those subscribers.<\/p>\n
There are the following types of scenarios in which we need to notify our clients:-<\/p>\n
Applications and System Alerts<\/strong><\/h2>\nThese are simple notifications, triggered by a predefined threshold and sent to specified users via mail or SMS.<\/p>\n
Many cases require immediate notifications, such as changes to your AWS scaling group<\/a> or when disk usage exceeds a threshold.<\/p>\nPush Emails and Text Messaging<\/strong><\/h2>\nThese are the simplest ways to transmit messages to individuals or groups.<\/p>\n
For example, you could use Amazon SNS to push targeted headlines, including exciting offers and discounts corresponding to your application, to the subscribers.<\/p>\n
Upon receiving the mail or sms, interested readers can choose to revert you for the same.<\/p>\n
Fanout in Amazon SNS<\/strong><\/h2>\nThe “fanout” scenario occurs when an Amazon SNS message is sent to a topic, which then replicates and pushes the message to multiple Amazon SQS queues, HTTP endpoints, or email addresses.<\/p>\n
For example, you could develop an application that sends a message to an SNS topic each time someone places an order for a product.<\/p>\n
Then, amazon SQS queues that are subscribed to those topics would identically receive notification for the new order.<\/p>\n
One EC2 instance<\/a> can process the order, while the other analyzes it as a data warehouse.<\/p>\nMobile Push Notifications<\/strong><\/h2>\nMobile push notifications enable you to send notifications directly to mobile applications.<\/p>\n
You can send mobile notifications with a link to download and install the update when it’s available.<\/p>\n
\n- Mobile push notifications engage customers when your app is currently not active.<\/li>\n
- Users opt-in to receive them.<\/li>\n
- Delivered to a specific application on a specific device.<\/li>\n
- Short messages: read, ignore, or acknowledge to launch the app.<\/li>\n<\/ul>\n
How does Amazon SNS work?<\/h2>\n
From a developer’s perspective, when you send a mobile notification, you address that message to a particular app on a specific device.<\/p>\n
The message is then sent directly, so the user doesn’t have to check for it, and the mobile app doesn’t have to pull it; instead, it arrives quickly and pops up on the user’s screen.<\/p>\n
![\"Platform-Service\"](\"http:\/\/cloudkul.com\/blog\/wp-content\/uploads\/2016\/01\/Platform-Service.png\")
<\/a><\/p>\nTo maintain this scenario, each mobile device uses a platform service<\/strong> that uses a persistent connection to send messages.<\/p>\nAs a developer, when you address a message to a device, you don’t send it directly to the device. Instead, you send the notification to a platform service, which then delivers it to the device.<\/p>\n
Hence, you don’t have to maintain hundreds or millions of simultaneous connections and you don’t need to hold on to messages to deliver them when the device is off.<\/p>\n
To implement this scenario, developers manage tokens for each device and must proactively swap or disable them based on the feedback.\u00a0<\/strong><\/p>\nThis platform service would require you to maintain the list of all the tokens of all the devices you haven’t authorized to send mobile notifications to and when the device is disabled.<\/p>\n
For example, if a user deletes your app or changes their device token, developers must update their databases to correctly address the list of allowed devices.<\/p>\n
IN CASE OF ANY QUERY, PLEASE CONTACT US <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Push Emails and Text Messaging<\/strong><\/h2>\nThese are the simplest ways to transmit messages to individuals or groups.<\/p>\n
For example, you could use Amazon SNS to push targeted headlines, including exciting offers and discounts corresponding to your application, to the subscribers.<\/p>\n
Upon receiving the mail or sms, interested readers can choose to revert you for the same.<\/p>\n
Fanout in Amazon SNS<\/strong><\/h2>\nThe “fanout” scenario occurs when an Amazon SNS message is sent to a topic, which then replicates and pushes the message to multiple Amazon SQS queues, HTTP endpoints, or email addresses.<\/p>\n
For example, you could develop an application that sends a message to an SNS topic each time someone places an order for a product.<\/p>\n
Then, amazon SQS queues that are subscribed to those topics would identically receive notification for the new order.<\/p>\n
One EC2 instance<\/a> can process the order, while the other analyzes it as a data warehouse.<\/p>\nMobile Push Notifications<\/strong><\/h2>\nMobile push notifications enable you to send notifications directly to mobile applications.<\/p>\n
You can send mobile notifications with a link to download and install the update when it’s available.<\/p>\n
\n- Mobile push notifications engage customers when your app is currently not active.<\/li>\n
- Users opt-in to receive them.<\/li>\n
- Delivered to a specific application on a specific device.<\/li>\n
- Short messages: read, ignore, or acknowledge to launch the app.<\/li>\n<\/ul>\n
How does Amazon SNS work?<\/h2>\n
From a developer’s perspective, when you send a mobile notification, you address that message to a particular app on a specific device.<\/p>\n
The message is then sent directly, so the user doesn’t have to check for it, and the mobile app doesn’t have to pull it; instead, it arrives quickly and pops up on the user’s screen.<\/p>\n
<\/a><\/p>\nTo maintain this scenario, each mobile device uses a platform service<\/strong> that uses a persistent connection to send messages.<\/p>\nAs a developer, when you address a message to a device, you don’t send it directly to the device. Instead, you send the notification to a platform service, which then delivers it to the device.<\/p>\n
Hence, you don’t have to maintain hundreds or millions of simultaneous connections and you don’t need to hold on to messages to deliver them when the device is off.<\/p>\n
To implement this scenario, developers manage tokens for each device and must proactively swap or disable them based on the feedback.\u00a0<\/strong><\/p>\nThis platform service would require you to maintain the list of all the tokens of all the devices you haven’t authorized to send mobile notifications to and when the device is disabled.<\/p>\n
For example, if a user deletes your app or changes their device token, developers must update their databases to correctly address the list of allowed devices.<\/p>\n
IN CASE OF ANY QUERY, PLEASE CONTACT US <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
The “fanout” scenario occurs when an Amazon SNS message is sent to a topic, which then replicates and pushes the message to multiple Amazon SQS queues, HTTP endpoints, or email addresses.<\/p>\n
For example, you could develop an application that sends a message to an SNS topic each time someone places an order for a product.<\/p>\n
Then, amazon SQS queues that are subscribed to those topics would identically receive notification for the new order.<\/p>\n
One EC2 instance<\/a> can process the order, while the other analyzes it as a data warehouse.<\/p>\n Mobile push notifications enable you to send notifications directly to mobile applications.<\/p>\n You can send mobile notifications with a link to download and install the update when it’s available.<\/p>\n From a developer’s perspective, when you send a mobile notification, you address that message to a particular app on a specific device.<\/p>\n The message is then sent directly, so the user doesn’t have to check for it, and the mobile app doesn’t have to pull it; instead, it arrives quickly and pops up on the user’s screen.<\/p>\n To maintain this scenario, each mobile device uses a platform service<\/strong> that uses a persistent connection to send messages.<\/p>\n As a developer, when you address a message to a device, you don’t send it directly to the device. Instead, you send the notification to a platform service, which then delivers it to the device.<\/p>\n Hence, you don’t have to maintain hundreds or millions of simultaneous connections and you don’t need to hold on to messages to deliver them when the device is off.<\/p>\n To implement this scenario, developers manage tokens for each device and must proactively swap or disable them based on the feedback.\u00a0<\/strong><\/p>\n This platform service would require you to maintain the list of all the tokens of all the devices you haven’t authorized to send mobile notifications to and when the device is disabled.<\/p>\n For example, if a user deletes your app or changes their device token, developers must update their databases to correctly address the list of allowed devices.<\/p>\n IN CASE OF ANY QUERY, PLEASE CONTACT US <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"Mobile Push Notifications<\/strong><\/h2>\n
\n
How does Amazon SNS work?<\/h2>\n
<\/a><\/p>\n