Amazon SNS vs Twilio: 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, Twilio is detailed as "Bring voice and messaging to your web and mobile applications". Twilio offers developers a powerful API for phone services to make and receive phone calls, and send and receive text messages. Their product allows programmers to more easily integrate various communication methods into their software and programs.
Amazon SNS belongs to "Mobile Push Messaging" category of the tech stack, while Twilio can be primarily classified under "Voice and SMS".
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, Twilio provides the following key features:
- Phone- Phone Numbers API
- Phone- Convert Text to Speech and Play Audio
- Phone- Record Calls and Store Them
According to the StackShare community, Twilio has a broader approval, being mentioned in 683 company stacks & 292 developers stacks; compared to Amazon SNS, which is listed in 227 company stacks and 76 developer stacks.
What is Amazon SNS?
What is Twilio?
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?
What are the cons of using Twilio?
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
Nexmo vs Twilio ?
Back in the early days at SmartZip Analytics, that evaluation had - for whatever reason - been made by Product Management. Some developers might have been consulted, but we hadn't made the final call and some key engineering aspects of it were omitted.
When revamping the platform, I made sure to flip the decision process how it should be. Business provided an input but Engineering lead the way and has the final say on all implementation matters. My engineers and I decided on re-evaluating the criteria and vendor selection. Not only did we need SMS support, but were we not thinking about #VoiceAndSms support as the use cases evolved.
Also, on an engineering standpoint, SDK mattered. Nexmo didn't have any. Twilio did. No-one would ever want to re-build from scratch integration layers vendors should naturally come up with and provide their customers with.
Twilio won on all fronts. Including costs and implementation timelines. No-one even noticed the vendor switch.
Many years later, Twilio demonstrated its position as a leader by holding conferences in the Bay Area, announcing features like Twilio Functions. Even acquired Authy which we also used for 2FA. Twilio's growth has been amazing. Its recent acquisition of SendGrid continues to show it.
Twilio is by far the most complete solution for SMS, its API is extremely well structured. And its integration with rails is pretty straight forward.
We use Twilio extensively for voice call routing, for texting. We, in fact, use it for MMS messaging as of recently...We do number masking. So the personal shopper never has your actual number, you call the Twilio number and it routes you intelligently to the customer. And vice-versa.
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.
Twilio is a service I have experimented with, and given a project with SMS requirements I would choose Twilio to support that.
We use SNS for platform-agnostic mobile push message handling, essentially to avoid dealing with APNS ourselves.
I mainly use it for the infrastructure notifications and alarms of zerotoherojs.com ’s learning dashboards.
For my own phone forwarding system, SMS messaging, and will gladly build such systems for clients.
I set up text-message alerts to be sent to me when an error was raised on the web application.
Used with BlueMix NodeRed to build an application that sends a text when it's about to rain.