We performed a comparison between Amazon SNS and IBM MQ based on real PeerSpot user reviews.
Find out in this report how the two Message Oriented Middleware (MOM) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Push notifications are the most valuable. I have mostly used push notifications for my system. Amazon SNS supports all devices for push notification services. It supports iOS, Android, and Windows notifications. It provides reliable push notification services. We have queues, and we can track which notifications have failed or had some issues. We can then figure out the issue. We can also debug the issue because of which our push notification didn't reach the end users."
"Amazon SNS has SMS notifications as well. Most of the other solutions have only email notifications."
"The best aspect of this solution is its simplicity. We just have to create topics and can have as many subscriptions as we want under any topic we create."
"The mobile push notifications are the most valuable. Previously, we used to use Firebase Cloud Messaging (FCM) for this functionality. It is a Google service for sending push notifications. Android did not have a good service for sending push notifications, but now, Amazon SNS integrates with FCM. Under the road, it is actually using FCM, but we can see all the metrics on our AW service itself, which makes it a lot easier instead of using a third-party service for this particular functionality."
"Stability has been good for us. It is quite high."
"The initial setup of Amazon SNS was easy."
"Messages easily flow from publisher or application to subscriber."
"The integration between the features is excellent."
"This initial setup is not complex at all. Deploying it was very easy."
"The most valuable feature is the Queue Manager, which lies in the middle between our application and our core banking server."
"The reliability of the queuing is the most valuable feature."
"The high availability and session recovery are the most valuable features because we need the solution live all day."
"Reliable messaging and throughput are the most valuable."
"The initial setup is easy."
"The most valuable feature is the stability. It's perfect in this way."
"We use queue managers/concentrators for message flow going upstream and downstream on applications with enterprise licenses."
"There could be more integration with other solutions."
"Messages should flow through a gateway without the need for a mediator."
"I expect Amazon SNS to provide some capabilities to allow the configuration process to be done in a single script."
"There needs to be more documentation on the integration with different platforms."
"In terms of improvement, I would like to have better customer support for SNS. We can then manage it very easily."
"The tool needs to have direct integration with AvPro."
"In future releases, I want to see if the platforms that SMS can reach. It would be a good way to improve it. More platforms to be able to use it."
"A major issue with AWS as a whole is that it has a lot of services that do the same thing, and people get confused about which one to use in which scenario. Previously, we used to use SNS for connecting microservices. SNS has around six types of subscribers. We can subscribe to Lambda, HTTP, HTTPS, SMS, email, and push notifications. We used to use HTTP endpoints and Lambda for connecting to microservice systems. Now we have something called EventBridge, which actually does that for you. For connecting to services, we should just use EventBridge rather than SQS, SNS. I hear a lot of complaints from people wherein they do not understand when to use EventBridge and when to use SQS, SNS. They can remove these features so that it doesn't confuse users about when to use SQS, SNS, or EventBridge."
"The product does not allow users to access data from API or external networks since it can only be used in a closed network, making it an area where improvements are required."
"Scaling is difficult with IBM MQ."
"There could be a better front-end GUI interface for us, where we can see things more easily."
"While there is support for API, it's not like the modern API capabilities."
"The solution requires a lot of work to implement and maintain."
"The issue is that they're using a very old clustering model."
"It would be nice if we could use the cluster facilities because we are doing active/passive configuration use."
"The initial setup is difficult. Creating your own cluster is difficult. Working with cluster repositories is difficult. Issue management with IBM MQ is difficult."
Amazon SNS is ranked 3rd in Message Oriented Middleware (MOM) with 11 reviews while IBM MQ is ranked 1st in Message Oriented Middleware (MOM) with 158 reviews. Amazon SNS is rated 9.0, while IBM MQ is rated 8.4. The top reviewer of Amazon SNS writes "The best service available with easy message flow and a pay-as-you-go model". On the other hand, the top reviewer of IBM MQ writes "Offers the ability to batch metadata transfers between systems that support MQ as the communication method". Amazon SNS is most compared with Amazon EventBridge, PubSub+ Event Broker and TIBCO Enterprise Message Service, whereas IBM MQ is most compared with ActiveMQ, Apache Kafka, VMware Tanzu Data Services, Red Hat AMQ and PubSub+ Event Broker. See our Amazon SNS vs. IBM MQ report.
See our list of best Message Oriented Middleware (MOM) vendors.
We monitor all Message Oriented Middleware (MOM) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
