Alternatives to Amazon SNS logo

Alternatives to Amazon SNS

Amazon Pinpoint, Twilio, Amazon MQ, Google Cloud Messaging, and Firebase are the most popular alternatives and competitors to Amazon SNS.
1.4K
1.2K
+ 1
18

What is Amazon SNS and what are its top alternatives?

Amazon SNS is a fully managed messaging service provided by AWS that enables developers to decouple microservices, distributed systems, and serverless applications. Its key features include push notifications, SMS, email, and mobile push messages, with support for message filtering, message attributes, and message encryption. However, Amazon SNS charges based on the number of requests and messages published, which can result in unpredictable costs for high-volume usage.

  1. Twilio Notify: Twilio Notify offers a scalable and reliable platform for sending notifications to users via SMS, push notifications, and email. Key features include personalized messages, event-based triggers, delivery confirmations, and reporting/analytics. Pros: Seamless integration with other Twilio services, global reach for SMS notifications. Cons: Pricing based on message volume, may be expensive for high-volume usage.
  2. Firebase Cloud Messaging: Firebase Cloud Messaging is a free cross-platform messaging solution that enables reliable delivery of notifications to Android, iOS, and web applications. Key features include message targeting, flexible message payloads, and delivery optimization. Pros: Easy setup and integration with Firebase services, high deliverability rates. Cons: Limited to Firebase ecosystem, lacking advanced features for message handling.
  3. Pusher: Pusher is a real-time messaging service that allows developers to deliver notifications, messages, and events in real-time to web and mobile applications. Key features include channels, events, presence, and webhooks for seamless communication. Pros: Real-time capabilities, easy to use APIs, excellent documentation and support. Cons: Pricing based on the number of connections and users, which can be costly for large applications.
  4. OneSignal: OneSignal is a powerful and easy-to-use push notification platform for web and mobile apps that supports multiple channels such as push notifications, email, and in-app messaging. Key features include segmentation, automation, A/B testing, and analytics. Pros: Free tier available for small apps, rich set of features, robust SDKs for various platforms. Cons: Limited customization options in the free tier, pricing can be expensive for high-volume usage.
  5. PubNub: PubNub is a real-time communication platform that provides scalable and reliable messaging infrastructure for building real-time applications. Key features include presence, history, security, and synchronization across devices. Pros: Global network infrastructure, low latency, support for IoT and edge computing. Cons: Complex pricing model based on messages and connections, may be costly for high-traffic applications.
  6. PushEngage: PushEngage is a browser push notification platform that helps websites engage with users through personalized notifications. Key features include segmentation, triggered campaigns, cart abandonment notifications, and drip campaigns. Pros: Easy setup and integration, excellent customer support, reasonable pricing plans. Cons: Limited to browser notifications, lacks support for other channels like SMS and email.
  7. Airship: Airship is a customer engagement platform that provides push notifications, in-app messaging, SMS, and email capabilities to deliver personalized messages to users. Key features include automation, segmentation, predictive AI, and analytics. Pros: Multi-channel engagement, comprehensive features for targeting and personalization. Cons: Expensive pricing for advanced features, may require additional integrations for full functionality.
  8. Pushwoosh: Pushwoosh is a cross-channel messaging platform that enables sending push notifications, in-app messages, email, and SMS to engage with users across devices. Key features include automation, personalized notifications, geotargeting, and analytics. Pros: Multi-channel messaging, flexible APIs, cost-effective pricing plans. Cons: Limited support for advanced features in lower-tier plans, may require additional setup for complex campaigns.
  9. Leanplum: Leanplum is a mobile marketing platform that provides personalized messages, A/B testing, automation, and analytics to optimize user engagement and retention. Key features include segmentation, real-time messaging, optimization, and predictive analytics. Pros: Robust features for mobile app engagement, comprehensive analytics dashboard. Cons: Pricing based on message volume, may not be cost-effective for small apps.
  10. Catapush: Catapush is a messaging API that offers scalable and reliable messaging services for critical communications such as alerts, notifications, and reminders. Key features include two-way messaging, high deliverability rates, message templates, and message encryption. Pros: Focus on critical messaging, high priority delivery, cost-effective pricing plans. Cons: Limited to messaging use cases, may lack advanced features for marketing campaigns.

Top Alternatives to Amazon SNS

  • Amazon Pinpoint
    Amazon Pinpoint

    Amazon Pinpoint makes it easy to run targeted campaigns to drive user engagement in mobile apps. Amazon Pinpoint helps you understand user behavior, define which users to target, determine which messages to send, schedule the best time to deliver the messages, and then track the results of your campaign. ...

  • Twilio
    Twilio

    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 MQ
    Amazon MQ

    Amazon MQ is a managed message broker service for Apache ActiveMQ that makes it easy to set up and operate message brokers in the cloud. ...

  • Google Cloud Messaging
    Google Cloud Messaging

    Google Cloud Messaging (GCM) is a free service that enables developers to send messages between servers and client apps. This includes downstream messages from servers to client apps, and upstream messages from client apps to servers. ...

  • Firebase
    Firebase

    Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. ...

  • Amazon SES
    Amazon SES

    Amazon SES eliminates the complexity and expense of building an in-house email solution or licensing, installing, and operating a third-party email service. The service integrates with other AWS services, making it easy to send emails from applications being hosted on services such as Amazon EC2. ...

  • Kafka
    Kafka

    Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design. ...

  • OneSignal
    OneSignal

    OneSignal is a high volume push notification service for websites and mobile applications. OneSignal supports all major native and mobile platforms by providing dedicated SDKs for each platform, a RESTful server API, and a dashboard. ...

Amazon SNS alternatives & related posts

Amazon Pinpoint logo

Amazon Pinpoint

72
320
13
Targeted Push Notifications for Mobile Apps
72
320
+ 1
13
PROS OF AMAZON PINPOINT
  • 13
    Transactional Messages
CONS OF AMAZON PINPOINT
    Be the first to leave a con

    related Amazon Pinpoint posts

    Manish Mishra
    Lead Consultant at Knoldus Software LLp · | 6 upvotes · 244.2K views
    Shared insights
    on
    Amazon PinpointAmazon PinpointAmazon SNSAmazon SNS

    Instead of Amazon SNS, which is currently being used to send outbound push notification and including SMS, we want to build the 2 Way SMS using Amazon Pinpoint. Just want to know about Pinpoint and any outstanding issues if we drop SNS since it does not support 2 Way and use Pinpoint for both incoming and outgoing flow.

    See more
    Twilio logo

    Twilio

    11.1K
    8.6K
    521
    Bring voice and messaging to your web and mobile applications.
    11.1K
    8.6K
    + 1
    521
    PROS OF TWILIO
    • 148
      Powerful, simple, and well documented api
    • 88
      RESTful API
    • 66
      Clear pricing
    • 61
      Great sms services
    • 58
      Low cost of entry
    • 29
      Global SMS Gateway
    • 14
      Good value
    • 12
      Cloud IVR
    • 11
      Simple
    • 11
      Extremely simple to integrate with rails
    • 6
      Great for startups
    • 5
      SMS
    • 3
      Great developer program
    • 3
      Hassle free
    • 2
      Text me the app pages
    • 1
      New Features constantly rolling out
    • 1
      Many deployment options, from build from scratch to buy
    • 1
      Easy integration
    • 1
      Two factor authentication
    CONS OF TWILIO
    • 4
      Predictable pricing
    • 2
      Expensive

    related Twilio posts

    Tom Klein

    Google Analytics is a great tool to analyze your traffic. To debug our software and ask questions, we love to use Postman and Stack Overflow. Google Drive helps our team to share documents. We're able to build our great products through the APIs by Google Maps, CloudFlare, Stripe, PayPal, Twilio, Let's Encrypt, and TensorFlow.

    See more
    Ravi Sathanapalli
    Director Product Management at Centime · | 7 upvotes · 101.1K views
    Shared insights
    on
    TwilioTwilioAmazon SNSAmazon SNS

    Hi, We are looking to implement 2FA - so that users would be sent a Verification code over their Email and SMS to their phone.

    We faced some limitations with Amazon SNS where we could either send the verification code to email OR to the phone number, while we want to send it to both.

    We also are looking to make the 2FA more flexible by adding any other options later on.

    What are the best alternatives to SNS for this use case and purpose? Looked at Twilio but want to explore other options before making a decision.

    Would be great to know what the experience with Twilio has been, especially the limitations/issues with Twilio...

    Appreciate any input from users of Twilio and others who have had similar use cases.

    See more
    Amazon MQ logo

    Amazon MQ

    54
    325
    12
    Managed Message Broker Service for ActiveMQ
    54
    325
    + 1
    12
    PROS OF AMAZON MQ
    • 7
      Supports low IQ developers
    • 3
      Supports existing protocols (JMS, NMS, AMQP, STOMP, …)
    • 2
      Easy to migrate existing messaging service
    CONS OF AMAZON MQ
    • 4
      Slow AF

    related Amazon MQ posts

    MITHIRIDI PRASANTH
    Software Engineer at LightMetrics · | 4 upvotes · 279K views
    Shared insights
    on
    Amazon MQAmazon MQAmazon SQSAmazon SQS

    I want to schedule a message. Amazon SQS provides a delay of 15 minutes, but I want it in some hours.

    Example: Let's say a Message1 is consumed by a consumer A but somehow it failed inside the consumer. I would want to put it in a queue and retry after 4hrs. Can I do this in Amazon MQ? I have seen in some Amazon MQ videos saying scheduling messages can be done. But, I'm not sure how.

    See more
    Kavitha Padmakumar
    devops engineer at Harman · | 3 upvotes · 11.3K views
    Shared insights
    on
    Amazon MQAmazon MQCloudAMQPCloudAMQP

    How is CloudAMQP different from Amazon MQ?

    which is the better one to use?

    See more
    Google Cloud Messaging logo

    Google Cloud Messaging

    91
    246
    22
    Simple and reliable messaging to reach over a billion devices.
    91
    246
    + 1
    22
    PROS OF GOOGLE CLOUD MESSAGING
    • 9
      Free
    • 6
      Scalable
    • 4
      Easy setup
    • 2
      Easy iOS setup
    • 1
      IOS Support
    CONS OF GOOGLE CLOUD MESSAGING
    • 1
      Reliability

    related Google Cloud Messaging posts

    Firebase logo

    Firebase

    40.5K
    34.7K
    2K
    The Realtime App Platform
    40.5K
    34.7K
    + 1
    2K
    PROS OF FIREBASE
    • 371
      Realtime backend made easy
    • 270
      Fast and responsive
    • 242
      Easy setup
    • 215
      Real-time
    • 191
      JSON
    • 134
      Free
    • 128
      Backed by google
    • 83
      Angular adaptor
    • 68
      Reliable
    • 36
      Great customer support
    • 32
      Great documentation
    • 25
      Real-time synchronization
    • 21
      Mobile friendly
    • 19
      Rapid prototyping
    • 14
      Great security
    • 12
      Automatic scaling
    • 11
      Freakingly awesome
    • 8
      Super fast development
    • 8
      Angularfire is an amazing addition!
    • 8
      Chat
    • 6
      Firebase hosting
    • 6
      Built in user auth/oauth
    • 6
      Awesome next-gen backend
    • 6
      Ios adaptor
    • 4
      Speed of light
    • 4
      Very easy to use
    • 3
      Great
    • 3
      It's made development super fast
    • 3
      Brilliant for startups
    • 2
      Free hosting
    • 2
      Cloud functions
    • 2
      JS Offline and Sync suport
    • 2
      Low battery consumption
    • 2
      .net
    • 2
      The concurrent updates create a great experience
    • 2
      Push notification
    • 2
      I can quickly create static web apps with no backend
    • 2
      Great all-round functionality
    • 2
      Free authentication solution
    • 1
      Easy Reactjs integration
    • 1
      Google's support
    • 1
      Free SSL
    • 1
      CDN & cache out of the box
    • 1
      Easy to use
    • 1
      Large
    • 1
      Faster workflow
    • 1
      Serverless
    • 1
      Good Free Limits
    • 1
      Simple and easy
    CONS OF FIREBASE
    • 31
      Can become expensive
    • 16
      No open source, you depend on external company
    • 15
      Scalability is not infinite
    • 9
      Not Flexible Enough
    • 7
      Cant filter queries
    • 3
      Very unstable server
    • 3
      No Relational Data
    • 2
      Too many errors
    • 2
      No offline sync

    related Firebase posts

    Johnny Bell

    I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

    I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

    I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

    Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

    Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

    With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

    If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

    See more
    Collins Ogbuzuru
    Front-end dev at Evolve credit · | 20 upvotes · 25.9K views

    Your tech stack is solid for building a real-time messaging project.

    React and React Native are excellent choices for the frontend, especially if you want to have both web and mobile versions of your application share code.

    ExpressJS is an unopinionated framework that affords you the flexibility to use it's features at your term, which is a good start. However, I would recommend you explore Sails.js as well. Sails.js is built on top of Express.js and it provides additional features out of the box, especially the Websocket integration that your project requires.

    Don't forget to set up Graphql codegen, this would improve your dev experience (Add Typescript, if you can too).

    I don't know much about databases but you might want to consider using NO-SQL. I used Firebase real-time db and aws dynamo db on a few of my personal projects and I love they're easy to work with and offer more flexibility for a chat application.

    See more
    Amazon SES logo

    Amazon SES

    9.8K
    5.9K
    328
    Bulk and transactional email-sending service.
    9.8K
    5.9K
    + 1
    328
    PROS OF AMAZON SES
    • 102
      Reliable
    • 97
      Cheap
    • 57
      Integrates with other aws services
    • 52
      Easy setup
    • 18
      Trackable
    • 2
      Easy rails setup
    CONS OF AMAZON SES
      Be the first to leave a con

      related Amazon SES posts

      Cyril Duchon-Doris

      We decided to use AWS Lambda for several serverless tasks such as

      • Managing AWS backups
      • Processing emails received on Amazon SES and stored to Amazon S3 and notified via Amazon SNS, so as to push a message on our Redis so our Sidekiq Rails workers can process inbound emails
      • Pushing some relevant Amazon CloudWatch metrics and alarms to Slack
      See more
      Simon Bettison
      Managing Director at Bettison.org Limited · | 8 upvotes · 779K views

      In 2012 we made the very difficult decision to entirely re-engineer our existing monolithic LAMP application from the ground up in order to address some growing concerns about it's long term viability as a platform.

      Full application re-write is almost always never the answer, because of the risks involved. However the situation warranted drastic action as it was clear that the existing product was going to face severe scaling issues. We felt it better address these sooner rather than later and also take the opportunity to improve the international architecture and also to refactor the database in. order that it better matched the changes in core functionality.

      PostgreSQL was chosen for its reputation as being solid ACID compliant database backend, it was available as an offering AWS RDS service which reduced the management overhead of us having to configure it ourselves. In order to reduce read load on the primary database we implemented an Elasticsearch layer for fast and scalable search operations. Synchronisation of these indexes was to be achieved through the use of Sidekiq's Redis based background workers on Amazon ElastiCache. Again the AWS solution here looked to be an easy way to keep our involvement in managing this part of the platform at a minimum. Allowing us to focus on our core business.

      Rails ls was chosen for its ability to quickly get core functionality up and running, its MVC architecture and also its focus on Test Driven Development using RSpec and Selenium with Travis CI providing continual integration. We also liked Ruby for its terse, clean and elegant syntax. Though YMMV on that one!

      Unicorn was chosen for its continual deployment and reputation as a reliable application server, nginx for its reputation as a fast and stable reverse-proxy. We also took advantage of the Amazon CloudFront CDN here to further improve performance by caching static assets globally.

      We tried to strike a balance between having control over management and configuration of our core application with the convenience of being able to leverage AWS hosted services for ancillary functions (Amazon SES , Amazon SQS Amazon Route 53 all hosted securely inside Amazon VPC of course!).

      Whilst there is some compromise here with potential vendor lock in, the tasks being performed by these ancillary services are no particularly specialised which should mitigate this risk. Furthermore we have already containerised the stack in our development using Docker environment, and looking to how best to bring this into production - potentially using Amazon EC2 Container Service

      See more
      Kafka logo

      Kafka

      23.3K
      21.8K
      607
      Distributed, fault tolerant, high throughput pub-sub messaging system
      23.3K
      21.8K
      + 1
      607
      PROS OF KAFKA
      • 126
        High-throughput
      • 119
        Distributed
      • 92
        Scalable
      • 86
        High-Performance
      • 66
        Durable
      • 38
        Publish-Subscribe
      • 19
        Simple-to-use
      • 18
        Open source
      • 12
        Written in Scala and java. Runs on JVM
      • 9
        Message broker + Streaming system
      • 4
        KSQL
      • 4
        Avro schema integration
      • 4
        Robust
      • 3
        Suport Multiple clients
      • 2
        Extremely good parallelism constructs
      • 2
        Partioned, replayable log
      • 1
        Simple publisher / multi-subscriber model
      • 1
        Fun
      • 1
        Flexible
      CONS OF KAFKA
      • 32
        Non-Java clients are second-class citizens
      • 29
        Needs Zookeeper
      • 9
        Operational difficulties
      • 5
        Terrible Packaging

      related Kafka posts

      Nick Rockwell
      SVP, Engineering at Fastly · | 46 upvotes · 3.6M views

      When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

      So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

      React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

      Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

      See more
      Ashish Singh
      Tech Lead, Big Data Platform at Pinterest · | 38 upvotes · 3M views

      To provide employees with the critical need of interactive querying, we’ve worked with Presto, an open-source distributed SQL query engine, over the years. Operating Presto at Pinterest’s scale has involved resolving quite a few challenges like, supporting deeply nested and huge thrift schemas, slow/ bad worker detection and remediation, auto-scaling cluster, graceful cluster shutdown and impersonation support for ldap authenticator.

      Our infrastructure is built on top of Amazon EC2 and we leverage Amazon S3 for storing our data. This separates compute and storage layers, and allows multiple compute clusters to share the S3 data.

      We have hundreds of petabytes of data and tens of thousands of Apache Hive tables. Our Presto clusters are comprised of a fleet of 450 r4.8xl EC2 instances. Presto clusters together have over 100 TBs of memory and 14K vcpu cores. Within Pinterest, we have close to more than 1,000 monthly active users (out of total 1,600+ Pinterest employees) using Presto, who run about 400K queries on these clusters per month.

      Each query submitted to Presto cluster is logged to a Kafka topic via Singer. Singer is a logging agent built at Pinterest and we talked about it in a previous post. Each query is logged when it is submitted and when it finishes. When a Presto cluster crashes, we will have query submitted events without corresponding query finished events. These events enable us to capture the effect of cluster crashes over time.

      Each Presto cluster at Pinterest has workers on a mix of dedicated AWS EC2 instances and Kubernetes pods. Kubernetes platform provides us with the capability to add and remove workers from a Presto cluster very quickly. The best-case latency on bringing up a new worker on Kubernetes is less than a minute. However, when the Kubernetes cluster itself is out of resources and needs to scale up, it can take up to ten minutes. Some other advantages of deploying on Kubernetes platform is that our Presto deployment becomes agnostic of cloud vendor, instance types, OS, etc.

      #BigData #AWS #DataScience #DataEngineering

      See more
      OneSignal logo

      OneSignal

      352
      484
      127
      A high volume push notification service for websites and mobile applications
      352
      484
      + 1
      127
      PROS OF ONESIGNAL
      • 28
        Free of cost
      • 22
        More parametrable
      • 17
        Simple and Easy To Use. Well Documented :)
      • 13
        Device to device
      • 12
        Simple
      • 9
        Many Platforms
      • 9
        Great support
      • 8
        Free
      • 4
        Flexibility in working with web, android and iOS
      • 4
        Phonegap / Cordova / Ionic starters
      • 1
        Good
      CONS OF ONESIGNAL
        Be the first to leave a con

        related OneSignal posts

        Lukas Bergamo
        CEO & Founder at ¹OnePlace · | 7 upvotes · 433.3K views
        Shared insights
        on
        OneSignalOneSignalFirebaseFirebase
        at

        At the beginning of the ¹OnePlace project, our team needed to decide which service to use to send bulk notifications to all users quickly and consistently. We tested some services without success and as we already used firebase we decided to implement in the beginning using Notifications by Firebase. We're having trouble updating the user's token to see if it has removed the app or not. This brought a working overhead and we were not sure if the notification had arrived at the destination. Today we use OneSignal, which did not bring reliability to the submitted notifications, nor do we need to bother with manual token updates. We ship approximately 500 thousand notifications with 100% delivery!

        OneSignal Firebase

        See more
        Yasmine de Aranda
        Chief Growth Officer at Huddol · | 7 upvotes · 370.8K views

        Hi there, we are a seed-stage startup in the personal development space. I am looking at building the marketing stack tool to have an accurate view of the user experience from acquisition through to adoption and retention for our upcoming React Native Mobile app. We qualify for the startup program of Segment and Mixpanel, which seems like a good option to get rolling and scale for free to learn how our current 60K free members will interact in the new subscription-based platform. I was considering AppsFlyer for attribution, and I am now looking at an affordable yet scalable Mobile Marketing tool vs. building in-house. Braze looks great, so does Leanplum, but the price points are 30K to start, which we can't do. I looked at OneSignal, but it doesn't have user flow visualization. I am now looking into Urban Airship and Iterable. Any advice would be much appreciated!

        See more