We changed our name from IT Central Station: Here's why
You must select at least 2 products to compare!
Amazon SNS Logo
2,020 views|1,709 comparisons
21,992 views|16,136 comparisons
Featured Review
Find out what your peers are saying about Amazon SNS vs. IBM MQ and other solutions. Updated: January 2022.
564,997 professionals have used our research since 2012.
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
"Stability has been good for us. It is quite high.""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 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."

More Amazon SNS Pros →

"It also has a backup queue concept and topics, features that I have not seen anywhere else. I like these features very much.""I haven't seen any severe issues related to it. Most of the time it's running. That is the advantage of IBM MQ.""RabbitMQ and Kafka require more steps for setup than IBM MQ. Installation of the IBM product is very simple.""The clusterization which results in persistence is the most valuable feature.""What is quite useful is the asynchronous function which means we don't lose everything in the bank. Although we use a lot of things synchronously, asynch is the best thing so that no banking information is ever lost, even when the network goes down and comes up.""Whenever payments are happening, such as incoming payments to the bank, we need to notify the customer. With MQ we can actually do that asynchronously. We don't want to notify the customer for each and every payment but, rather, more like once a day. That kind of thing can be enabled with the help of MQ.""The methodology and the way in which the platform has been produced as a standard is most valuable. There are so many different versions of it now, but the actual basic functionality and the simplicity of it have made it far easier to be implemented in so many different instances. When I worked with the OS/2 or PS/2 machine environment, the messaging mechanisms were based upon IBM MQ. It is so versatile, which is the main reason that I'm a fan of it.""I have found the solution to be very robust. It has a strong reputation, easy to use, simple to configure in our enterprise software, and supports all the protocols that we use."

More IBM MQ Pros →

"I recently worked with Firebase, and it provides an option to create a marketing campaign with a title and a specific image to inform our audience about something. We just design the campaign and then use the push notifications. It would be good if Amazon also adds a similar feature.""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."

More Amazon SNS Cons →

"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.""They could integrate monitoring into the solution, a bit more than they do now. Currently, they have opened the REST API so you can get statistic and accounting information and details from MQ and build your own monitoring, if you want. IBM can improve the solution in this direction.""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.""The initial setup is difficult. Creating your own cluster is difficult. Working with cluster repositories is difficult. Issue management with IBM MQ is difficult.""The main issue we are having with the solution is due to the connection dropouts which have been going on for a long time now.""There are many complications with IBM MQ servers.""I wanted to upgrade Windows Server. It's not that easy to move.""They have provided a Liberty Profile in the Web Console for administration, and that could be further enhanced. It is not fit for use by an enterprise. They have to get rid of their WebSphere process and develop a front-end on Node.js or the like."

More IBM MQ Cons →

Pricing and Cost Advice
  • "The pricing of push notifications and everything is quite fair. If you are using FCM under the hood, it is completely free. When you are using push notification on SMS, it is just a nominal price that you need to pay. SMS services are a lot more costly. It is because we don't have proper providers in India. That's why it gets a lot more costly in terms of SMS. This is the reason why we don't use SMS services from SNS itself. We use other third-party services like SMS Horizon. We use a third-party service for email services. It is almost free. It is just around $1 a month. Configuring Lambda is also quite cheap. You only pay for the Lambda usage. You don't pay for SNS itself."
  • "It is the cheapest solution in the market. It is on a monthly basis. After a month, you are build based on your usage. There are no additional costs to the standard licensing fees."
  • More Amazon SNS Pricing and Cost Advice →

  • "The price is high."
  • "There is a different platform price between Windows, z/OS, and iSeries."
  • "IBM products, in general, have high licensing costs and support costs are too high."
  • "Most of our customers are quite happy with the solution but they have an issue with the cost. They want to move to cheaper solutions."
  • "It is a very expensive product compared to the open source products in the market."
  • "It would be a 10 out of 10 if it wasn't so expensive."
  • "It's a very expensive product."
  • "IBM MQ is expensive and they charge based on the CPU."
  • More IBM MQ Pricing and Cost Advice →

    Use our free recommendation engine to learn which Message Oriented Middleware (MOM) solutions are best for your needs.
    564,997 professionals have used our research since 2012.
    Questions from the Community
    Ask a question

    Earn 20 points

    Top Answer: 
    Apache Kafka is open source and can be used for free. It has very good log management and has a way to store the data used for analytics. Apache Kafka is very good if you have a high number of users… more »
    Top Answer: 
    IBM MQ has a great reputation behind it, and this solution is very robust with great stability. It is easy to use, simple to configure and integrates well with our enterprise ecosystem and protocols… more »
    Top Answer: 
    The solution allows one to easily configure an IBM MQQueueManager.
    Average Words per Review
    Average Words per Review
    Also Known As
    WebSphere MQ
    Learn More

    Amazon Simple Notification Service (SNS) is a highly available, durable, secure, fully managed pub/sub messaging service that enables you to decouple microservices, distributed systems, and serverless applications. Amazon SNS provides topics for high-throughput, push-based, many-to-many messaging. Using Amazon SNS topics, your publisher systems can fan out messages to a large number of subscriber endpoints for parallel processing, including Amazon SQS queues, AWS Lambda functions, and HTTP/S webhooks. Additionally, SNS can be used to fan out notifications to end users using mobile push, SMS, and email.

    You can get started with Amazon SNS in minutes by using the AWS Management Console, AWS Command Line Interface (CLI), or AWS Software Development Kit (SDK).

      IBM MQ provides the universal messaging backbone for service-oriented architecture (SOA) connectivity. It connects virtually any commercial IT system, whether on premise, in the cloud, or a mixture. For more than 20 years IBM has led the market in messaging middleware and more than 10,000 businesses across all geographies and industries rely on IBM MQ.

      Visit for your trial here.

    Learn more about Amazon SNS
    Learn more about IBM MQ
    Sample Customers
    PlayOn! Sports, NASA, Change Healthcare, FCBarcelona
    Deutsche Bahn, Bon-Ton, WestJet, ARBURG, Northern Territory Government, Tata Steel Europe, Sharp Corporation
    Top Industries
    Media Company25%
    Computer Software Company18%
    Comms Service Provider18%
    Financial Services Firm8%
    Financial Services Firm37%
    Insurance Company10%
    Healthcare Company6%
    Computer Software Company26%
    Financial Services Firm24%
    Comms Service Provider14%
    Company Size
    No Data Available
    Small Business7%
    Midsize Enterprise9%
    Large Enterprise84%
    Small Business15%
    Midsize Enterprise10%
    Large Enterprise75%
    Find out what your peers are saying about Amazon SNS vs. IBM MQ and other solutions. Updated: January 2022.
    564,997 professionals have used our research since 2012.

    Amazon SNS is ranked 3rd in Message Oriented Middleware (MOM) with 3 reviews while IBM MQ is ranked 1st in Message Oriented Middleware (MOM) with 45 reviews. Amazon SNS is rated 9.4, while IBM MQ is rated 8.0. The top reviewer of Amazon SNS writes "Automatically scalable, very stable, and full of solid and useful features". On the other hand, the top reviewer of IBM MQ writes "We don't lose messages in transit and we can store messages and forward them when required". Amazon SNS is most compared with Amazon EventBridge, PubSub+ Event Broker and TIBCO Enterprise Message Service, whereas IBM MQ is most compared with Apache Kafka, VMware RabbitMQ, ActiveMQ, PubSub+ Event Broker and Aurea CX Messenger. 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.