Amazon SNS vs SendGrid: What are the differences?
Developers describe Amazon SNS as "Fully managed push messaging service". Amazon Simple Notification Service makes it simple and cost-effective to push to mobile devices such as iPhone, iPad, Android, Kindle Fire, and internet connected smart devices, as well as pushing to other distributed services. Besides pushing cloud notifications directly to mobile devices, SNS can also deliver notifications by SMS text message or email, to Simple Queue Service (SQS) queues, or to any HTTP endpoint. On the other hand, SendGrid is detailed as "Email Delivery. Simplified". SendGrid's cloud-based email infrastructure relieves businesses of the cost and complexity of maintaining custom email systems. SendGrid provides reliable delivery, scalability and real-time analytics along with flexible API's that make custom integration a breeze.
Amazon SNS belongs to "Mobile Push Messaging" category of the tech stack, while SendGrid can be primarily classified under "Transactional Email".
Some of the features offered by Amazon SNS are:
- In most cases, developers can get started with Amazon SNS by using just three APIs: CreateTopic, Subscribe, and Publish. Additional APIs are available, which provide more advanced functionality.
- With SNS you can publish a message once, and deliver it one or more times. So you can choose to direct unique messages to individual Apple, Google or Amazon devices, or broadcast deliveries to many mobile devices with a single publish request.
- SNS allows you to group multiple recipients using topics. A topic is an “access point” for allowing recipients to dynamically subscribe for identical copies of the same notification. One topic can support deliveries to multiple endpoint types -- for example, you can group together iOS, Android and SMS recipients. When you publish once to a topic, SNS delivers appropriately formatted copies of your message to each subscriber.
On the other hand, SendGrid provides the following key features:
- Open Tracking
- Click Tracking
- Unsubscribe Tracking
According to the StackShare community, SendGrid has a broader approval, being mentioned in 2692 company stacks & 421 developers stacks; compared to Amazon SNS, which is listed in 227 company stacks and 76 developer stacks.
What is Amazon SNS?
What is Twilio SendGrid?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Amazon SNS?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Every app needs email, even the ones we build regularly send some kind, be it signup, reset passwords or general announcements, it's all gotta come from somewhere. SendGrid have been a very reliable platform in the past, and we've had no issues so far.
SendGrid came to our attention as a great way of handling outgoing e-mail communication. Mass capabilities, spam handling and the sheer power of MailChimp as a vendor made our decision here.
All of our external emails are sent using SendGrid. SendGrid's statistics dashboards help us figure out whether our emails are reaching people, and how much attention is paid to them.
Our primary transport mechanism for events. One SNS topic carries a specific event type and n-number of subscribers (usually a Lambda) may subscribe to that event.
Amazon SNS is used for push notification to push notifications of the occurrence of different events during operations of our computing resources on AWS cloud.
Email service used within Coolfront Mobile to send emails and track emails to contractors and their customers (e.g. home-owners).
We use SNS for platform-agnostic mobile push message handling, essentially to avoid dealing with APNS ourselves.
Sending welcome emails, chasing potential customers, providing customers with help, password reset emails, etc.
I mainly use it for the infrastructure notifications and alarms of zerotoherojs.com ’s learning dashboards.