Amazon Simple Notification Service (SNS) vs. Clickatell vs. Google Cloud Pub/Sub

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Amazon SNS
Score 8.7 out of 10
N/A
Amazon Web Services offers the Amazon Simple Notification Service (SNS) which provides pub/sub messaging and push notifications to iOS and Android devices. It is meant to operate in a microservices architecture and which can support event-driven contingencies and support the decoupling of applications.
$0.01
per 1 million
Clickatell
Score 0.0 out of 10
N/A
Clickatell’s Chat Commerce Platform supports the creation and development of customer relationships in chat-based messaging, engagement, and payment solutions. With it, the vendor states its global customers can manage millions of monthly conversations and transactions, all through chat.N/A
Google Cloud Pub/Sub
Score 8.8 out of 10
N/A
Google offers Cloud Pub/Sub, a managed message oriented middleware supporting many-to-many asynchronous messaging between applications.N/A
Pricing
Amazon Simple Notification Service (SNS)ClickatellGoogle Cloud Pub/Sub
Editions & Modules
API Requests & Payload Data
$0.01
per 1 million
API Requests
$0.50
per 1 million requests
Notification Deliveries
$0.50
per million notifications
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Amazon SNSClickatellGoogle Cloud Pub/Sub
Free Trial
NoNoNo
Free/Freemium Version
NoNoNo
Premium Consulting/Integration Services
NoNoNo
Entry-level Setup FeeNo setup feeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Amazon Simple Notification Service (SNS)ClickatellGoogle Cloud Pub/Sub
Considered Multiple Products
Amazon SNS
Chose Amazon SNS
Amazon Simple Notification Service (SNS) is well integrated in AWS and has been there since the early days of public cloud. It is a cost effective and very inexpensive solution to meet the needs of event notifications and custom messaging. Wish to share that there is …
Chose Amazon SNS
Amazon’s SNS is incredibly easy to set up compared to the more powerful, but complex, Kafka flavours.
Chose Amazon SNS
I worked with Adobe campaign 2 years ago and comparatively, SNS is way better and easier to integrate with. There's a lack of latency with SNS and better customer support. Easier to group with subscriptions and easier to work from the command line with the use of the SDK. All …
Chose Amazon SNS
No obvious difference. We chose AWS SNS, as we are an AWS EdStart company and built on the AWS stack already.
Chose Amazon SNS
SNS helps in integrating with other AWS components which are used in development such as Lambda, APIGW, S3 and DynamoDb easily. If used with third party software like PagerDuty, it makes the development and integration more complex. It is used mostly for publishing and …
Chose Amazon SNS
We use AWS and becasue Amazon SNS can be easily integrated with AWS.
Chose Amazon SNS
Amazon Simple Notification Service and PagerDuty have been used by various organizations. Amazon SNS is ideal if you're within an AWS environment. PagerDuty is used when we are working outside of Amazon Web Services. Though PagerDuty is more expensive than Amazon SNS they do …
Chose Amazon SNS
SNS is already integrated with other AWS services. I can reuse lists or topics.
Chose Amazon SNS
We have looked at other service providers, including the local service providers as well, but Amazon SNS stood ahead of all in terms of service availability across the globe and cost-effective plans per notification SMS. Moreover, we can also use Amazon SNS along with other AWS …
Chose Amazon SNS
Common confusion between SNS and SQS. SNS directs information to its subscribers without any effort on the subscribers or individuals' end. SQS gathers the information and then the individual has to almost go find it. They do similar things but in a space where information can …
Chose Amazon SNS
We have opted ultimately for AWS SNS once configuration was set topics and subscriptions setup. Site 24 and US Monitor are considerations to this product, but incur cost outside of Amazon, so not best for starting up for our needs.
Chose Amazon SNS
The main reason we chose Amazon SNS is for easy integration with all the workflows in AWS. The other alternatives can be (and really are) best in specific points, but the main strength of SNS is that is one service of AWS, so we don't need to complicate things in our …
Chose Amazon SNS
Our company prioritizes using AWS offerings unless there is a strong use case for using something within Azure. SQS is a similar service that solves different problems and we are using it in conjunction with SNS.
Chose Amazon SNS
Our clients are mostly on AWS, so it was easy for us to use Amazon Simple Notification Service (SNS) and to integrate it with current applications.
Chose Amazon SNS
We use EC2 instances to train ML model against a heavy volume of data. When the model is trained (i.e. loss reduces to a certain level), we push notification to all the stakeholders to notify them the new model is available. To achieve it, SNS is the most simple and cost …
Chose Amazon SNS
We use a lot of services from AVS, and it's easy to set up all services between each other.
Chose Amazon SNS
Many products, including PagerDuty, can be used to notify stakeholders when alarms are triggered. SNS is only suitable for non-emergency email alerts, and integration with CloudWatch is its only advantage. If you want to be notified of an issue by email, SNS can be configured …
Chose Amazon SNS
SNS is much more customizable compared to SES and allows for many more delivery methods. While it is better for email-based notification services, not being able to send notifications via SMS limits your app functionality considerably. Being able to switch message delivery …
Chose Amazon SNS
As I mentioned previously, I wish we had gone with a different service such as a Mixpanel or OneSignal as they are reputable in the space and are known for their strong support and documentation. AWS SNS was the way to go for us at the time we chose it due to the fact that we …
Clickatell

No answer on this topic

Google Cloud Pub/Sub
Chose Google Cloud Pub/Sub
Google Cloud Pub/Sub is a managed service compared to Apache Kafka.

Simple Queue Service (SQS) is an Amazon managed service that supports similar functionality as compared to Google Cloud Pub/Sub. However, we selected Google Cloud Pub/Sub as all other services in our platform …
Chose Google Cloud Pub/Sub
Kafka looks like and ordered queue, there no deliver backoff, so if a message has a problem, it doesn't advance to the next one. Google Cloud Pub/Sub looks like more a SET of messages, and kafka like a LIST. In kafka a same message will repeat instantaneously while it is being …
Chose Google Cloud Pub/Sub
Having used Amazon Web Services SNS & SQS I can say that even if the latter may offer more features, Google Cloud Pub/Sub is easier to use. On the other hand, usage of SNS & SQS as well as documentation and troubleshooting is easier with the AWS solution.
Since we are not using …
Chose Google Cloud Pub/Sub
Google Cloud Pub/Sub as a managed service is significantly more easy to use than a self managed Kafka cluster. As our software was already on GCP it was a no-brainer to use Pub/Sub due to the high level of integration and ease of use with other Google Cloud Platform services.
Chose Google Cloud Pub/Sub
  • Easy to setup Publisher, Subscribers and Message Queue service
  • More Reliable and Easy Scalable with Google Managed services
  • Easily integrated with most of the data sources we typically use for Data Storage and Analysis
Chose Google Cloud Pub/Sub
Amazon SQS has no integration with google play billing whereas Google Cloud Pub/Sub had native integration with google cloud billing, Play billing.
Chose Google Cloud Pub/Sub
We considered several messaging platforms including Kafka and Kinesis but both would have required more developer work and didn't integrate as nicely with our ecosystem. RabbitMQ is another messaging platform I've researched and prototyped on; it also would have required more …
Chose Google Cloud Pub/Sub
Compute Engine is not a direct competitor, but in fact, works well coupled with Pub/Sub.
Best Alternatives
Amazon Simple Notification Service (SNS)ClickatellGoogle Cloud Pub/Sub
Small Businesses
AWS IoT Core
AWS IoT Core
Score 9.9 out of 10
OneSignal
OneSignal
Score 8.0 out of 10
AWS IoT Core
AWS IoT Core
Score 9.9 out of 10
Medium-sized Companies
Apache Kafka
Apache Kafka
Score 8.8 out of 10
LocaliQ
LocaliQ
Score 8.7 out of 10
Apache Kafka
Apache Kafka
Score 8.8 out of 10
Enterprises
Apache Kafka
Apache Kafka
Score 8.8 out of 10
Airship
Airship
Score 8.9 out of 10
Apache Kafka
Apache Kafka
Score 8.8 out of 10
All AlternativesView all alternativesView all alternativesView all alternatives
User Ratings
Amazon Simple Notification Service (SNS)ClickatellGoogle Cloud Pub/Sub
Likelihood to Recommend
8.0
(0 ratings)
-
(0 ratings)
9.0
(0 ratings)
Likelihood to Renew
-
(0 ratings)
-
(0 ratings)
10.0
(0 ratings)
Usability
9.0
(0 ratings)
-
(0 ratings)
10.0
(0 ratings)
Availability
-
(0 ratings)
-
(0 ratings)
10.0
(0 ratings)
Performance
-
(0 ratings)
-
(0 ratings)
10.0
(0 ratings)
Support Rating
8.4
(0 ratings)
-
(0 ratings)
9.8
(0 ratings)
Configurability
-
(0 ratings)
-
(0 ratings)
10.0
(0 ratings)
Product Scalability
-
(0 ratings)
-
(0 ratings)
10.0
(0 ratings)
User Testimonials
Amazon Simple Notification Service (SNS)ClickatellGoogle Cloud Pub/Sub
Likelihood to Recommend
Using SNS for any notification use case where available is the default and defacto solution. It directly integrates with SES to configure both incoming email and email delivery responses.
Additionally, any notifications, such as CloudWatch alarms, are a good use case for SNS topics and allow us to fan out delivery as needed (pagerduty, email, etc)
Read full review
No answers on this topic
Using Google Cloud Pub/Sub will mainly depend on the cloud platform used. Our client didn't choose GCP for Google Cloud Pub/Sub, if we went with AWS we would be using SNS/SQS (obviously). However, Google Cloud Pub/Sub is a better solution in the GCP services compared to self-managed solutions such as RabbitMQ for instance (it is managed by GCP and integrates with GCP solutions).
Read full review
Pros
  • Built in for quicker setup within AWS ecosystem.
  • Trusted as you control the users and configuration via IAM and easy access controls.
  • Can be sent to S3 simple storage or for long term storage if required.
  • Can be used in many regions, same configs.
Read full review
No answers on this topic
  • A hands-off approach to publishing messages and subscribing to topics.
  • Easy to use APIs.
  • Useful, simple UI on cloud console to send messages for debugging, etc.
Read full review
Cons
  • At times you receive access denied errors which are annoying.
  • Rarely do you receive internal failure errors where you can't access the information. It is rare but it does happen.
  • You are required to add an MWS Authentication Token every so often. I wish it would pull that information automatically for you so you don't have to go searching for it.
Read full review
No answers on this topic
  • Allow write and read of messages more than 10 MB
  • Support rate at which HTTP endpoints are triggered to reduce scale requirements on downstream services
  • Support replay of messages
Read full review
Likelihood to Renew
No answers on this topic
No answers on this topic
It serves all of our purposes in the most transparent way I can imagine, after seeing other message queueing providers, I can only attest to its quality.
Read full review
Usability
It is useful for applications developed using event driven architecture. It helps in tracking and logging the events in a very timely and efficient manner. The dashboards are a little difficult to implement. But overall it is very easy to integrate with other AWS services like Lambda, API GW, S3 and DynamoDB. The permissions to access should be resolved before using it.
Read full review
No answers on this topic
It is easy to create Google Cloud Pub/Sub topics from both Web Console and CLI commands.
Google Cloud Pub/Sub supports creation of one or more subscriptions.
By supporting a BigQuery Pub/Sub subscription to automatically write to a BigQuery table it simplifies development by avoiding implementation of a custom micro service for writes to BigQuery.
Read full review
Reliability and Availability
No answers on this topic
No answers on this topic
I have never faced a single problem in 4 years.
Read full review
Performance
No answers on this topic
No answers on this topic
It's very fast, can be even better if you use protobuf.
Read full review
Support Rating
The AWS documentation is well maintained and has lots of information which makes it easier for developers to refer to and develop applications in a fast efficient manner. It is well documented with examples which is easy to understand and implement. You can also get help by posting into forums from like-minded developers.
Read full review
No answers on this topic
They have decent documentation, but you need to pay for support. We weren't able to answer all our questions with the documentation and didn't have time to setup support before we needed it so I can't give it a higher rating but I think it tends to be a bit slow unless you're a GCP enterprise support customer.
Read full review
Alternatives Considered
Amazon Simple Notification Service (SNS) is well integrated in AWS and has been there since the early days of public cloud. It is a cost effective and very inexpensive solution to meet the needs of event notifications and custom messaging. Wish to share that there is considerable number of developers who can easily build solutions using AWS SNS. So, training costs are minimal. Other solutions are emerging and we are seeing a great usage especially of Firebase notifications because of its very neat integration with open source cross platform hybrid app frameworks like ionic, xamarin. SNS needs to become better and should have plugin support for the mobile application developers using low code/no code tools too.
Read full review
No answers on this topic
  • Easy to setup Publisher, Subscribers and Message Queue service
  • More Reliable and Easy Scalable with Google Managed services
  • Easily integrated with most of the data sources we typically use for Data Storage and Analysis
  • 10k Topics is a good enough number to build and deliver the business use cases
  • Asynchronous and fallback mechanisms are great to ensure parallel delivery of the messages
Read full review
Scalability
No answers on this topic
No answers on this topic
You can just plug in consumers at will and it will respond, there's no need for further configuration or introducing new concepts. You have a queue, if it's slow, you plug in more consumers to process more messages: simple as that.
Read full review
Return on Investment
  • Cost of alert calls to the different stakeholders across different geographies have gone down since using Amazon SNS.
  • Amazon SNS has saved a lot of time for the employees that they used to spend to call multiple stakeholders so they can now focus more on productive tasks.
  • Amazon SNS usage needs prior knowledge of programming.
Read full review
No answers on this topic
  • Pub/Sub has helped avoid data loss improving our customer value prop.
  • Pub/Sub has reduced development time that would otherwise be needed to build a highly scalable queue.
Read full review
ScreenShots