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."We have found the key feature of this solution to be the simplicity of sending out notifications."
"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."
"The most valuable feature of Amazon SNS is speed. It's really fast."
"The initial setup of Amazon SNS was easy."
"Messages easily flow from publisher or application to subscriber."
"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."
"The integration between the features is excellent."
"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 most valuable feature is the interaction within the system."
"We use our routing feature when the request is coming from the business application. The request goes to the distributive side and it is routed to the right claim instance."
"Support for JMS 2.0, because we develop solutions compatible with Java EE7."
"There are a lot of extensible options for security, i.e., various things you can do. It's pretty easy to navigate."
"Stability-wise, I rate the solution a ten out of ten."
"This product has good security."
"IBM MQ's flexibility has sped up our active communication."
"I have found that the solution scales well."
"We would like the integration with third party applications to be improved within this solution."
"I expect Amazon SNS to provide some capabilities to allow the configuration process to be done in a single script."
"The tool needs to have direct integration with AvPro."
"Messages should flow through a gateway without the need for a mediator."
"There could be more integration with other solutions."
"We would like to have the option when someone leaves the organization or moves to another team, to remove notifications. Currently this needs to be done manually by the company admin."
"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."
"In terms of improvement, I would like to have better customer support for SNS. We can then manage it very easily."
"Presenting and maybe having some different options for different user experiences based on the administrative duties that you have to do as an app manager or configure the server or security would be an improvement."
"It's hard to put in a nutshell, but it's sort of developed as more of an on-premise solution. It hasn't moved much away from that."
"The issue is that they're using a very old clustering model."
"If they could come up with monitoring dashboards that would be good. We are using external monitoring tools, apart from our IBM MQ, to monitor IBM MQ. If we could get monitoring tools or dashboards to keep everything simple for the user to understand, that would be good."
"At a recent conference, I went to a presentation that had the latest version and it has amazing stuff that's coming out. So, I am excited to use those, specifically surrounding the web console and the fact that it's API integrated."
"There are things within the actual product itself that can be improved, such as limitations on message length, size, etc. There is no standardized message length outside of IBM. Each of the implementations of the MQ series or support of that functionality varies between various suppliers, and because of that, it is very difficult to move from one to the other. We have IBM MQ, but we couldn't use it because the platform that was speaking to MQ didn't support the message length that was standard within IBM MQ. So, we had to use a different product to do exactly the same thing. So, perhaps, there could be more flexibility in the standards around the message queue. If we had been able to increase the message queue size within the IBM MQ implementation, we wouldn't have had to go over to another competing product because the system that was using MQ messaging required the ability to hold messages that were far larger than the IBM MQ standard. So, there could be a bit more flexibility in the structuring. It has as such nothing to do with the IBM implementation of MQ. It is just that the standard that is being put out onto the market doesn't actually stipulate those types of things."
"While there is support for API, it's not like the modern API capabilities."
"Everything in the solution could be simplified a little. We have trouble with the configuration and cost which is mostly an internal issue, but nevertheless, the errors do come up when there are configuration changes across a specific version. We have slightly different versions, which may have slightly different configurations which cause issues."
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.
