No more typing reviews! Try our Samantha, our new voice AI agent.

Amazon SNS vs TIBCO Enterprise Message Service comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Amazon SNS
Ranking in Message Oriented Middleware (MOM)
5th
Average Rating
9.0
Reviews Sentiment
7.9
Number of Reviews
12
Ranking in other categories
No ranking in other categories
TIBCO Enterprise Message Se...
Ranking in Message Oriented Middleware (MOM)
3rd
Average Rating
7.8
Number of Reviews
6
Ranking in other categories
Business Activity Monitoring (2nd)
 

Mindshare comparison

As of June 2026, in the Message Oriented Middleware (MOM) category, the mindshare of Amazon SNS is 4.8%, down from 6.2% compared to the previous year. The mindshare of TIBCO Enterprise Message Service is 10.2%, up from 10.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Message Oriented Middleware (MOM) Mindshare Distribution
ProductMindshare (%)
TIBCO Enterprise Message Service10.2%
Amazon SNS4.8%
Other85.0%
Message Oriented Middleware (MOM)
 

Featured Reviews

HarshalJethwa - PeerSpot reviewer
Cloud Operations Engineer at a tech vendor with 51-200 employees
Event-driven messaging has improved real-time notifications and incident response
In my experience, the best features Amazon SNS offers include the ability to create an event-driven architecture and services, as well as real-time notifications.When I mention real-time capabilities and integration with other AWS services, specific integrations or real-time features that stand out most to me are S3 bucket events including creating a bucket, creating an object, updating an object, modifying an object, and deleting an object. Additionally, with CloudWatch alarms, when I get an alarm on CloudWatch, it will notify me via email using Amazon SNS. The same applies to application events. Amazon SNS has impacted my organization positively because using it, we are able to create an event-driven architecture and send notifications for events or incidents. Amazon SNS has helped my team respond faster, improved reliability, and saved time. Specifically, because of it, we are able to identify events as soon as possible. It saves our time and we can also process them as soon as possible.
SunilKumar26 - PeerSpot reviewer
Technical Lead at a tech consulting company with 51-200 employees
Persistent messaging has improved reliability while message rate and licensing still need work
One problem is the license cost. If we take Kafka, it's an open source platform, Apache Kafka, but with TIBCO Enterprise Message Service, the license cost is significantly higher. The message rate in TIBCO Enterprise Message Service needs to be increased compared to Kafka. The streaming capacity of Kafka is much better than TIBCO Enterprise Message Service. This part should be improved. The message rate per bit, per minute, and per second is much lower in TIBCO Enterprise Message Service compared to Kafka. Setup is relatively simple and not overly complex, but we do need some root access and administrator privileges. However, the problem is that once we upgrade TIBCO Enterprise Message Service, whatever services are on the primary must be taken down.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"We have found the key feature of this solution to be the simplicity of sending out notifications."
"We use this solution because the integration between the features is excellent."
"It's a simple communication service that allows us to communicate with customers."
"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 helped my team respond faster, improved reliability, and saved time."
"We see ROI because we use the features that help us and make our product work better."
"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."
"Stability has been good for us. It is quite high."
"The setup was done by TIBCO. It has been stable and has a server."
"TIBCO Enterprise Message Service is a security and reliability product with persistent messaging, asynchronous and synchronous messaging for the queues and topics."
"​The initial setup is straightforward and the product documentation is very good.​"
"The Enterprise Messaging Server will store the message and wait for other subscribers to come onto the network."
"TIBCO Enterprise Message Service's most valuable features are rapid zero-code integration and its large number of adapters and plugins."
"We have implanted the core middleware solution for the organization using this product and it is responsible for communication between different applications."
"I like TIBCO's ability to create versioned queues and persistent messages."
"It is very useful tool. It is also very easy to learn and implement.​"
 

Cons

"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."
"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."
"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."
"We would like the integration with third party applications to be improved within this solution."
"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."
"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."
"One problem is the license cost. If we take Kafka, it's an open source platform, Apache Kafka, but with TIBCO Enterprise Message Service, the license cost is significantly higher."
"An area for improvement would be integration with the API layer."
"Overall, my experience with the support team has been disappointing."
"I would like to see better integration with Java and Apache Kafka."
"It can be improved in the sense that in the market we can see the cloud is coming, but this is not cloud compatible."
"TIBCO also has its proprietary line of cloud-based applications, but specifically, these two products are not cloud compatible."
"​Since all the communications goes through this product, it acts as a single point of failure."
 

Pricing and Cost Advice

"One can use the tool for free."
"Their pricing is competitive. I would rate the cost four out of five."
"Amazon SNS is cheap and I would rate it a three out of ten. The pricing is usage-based."
"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."
"The pricing is very cheap."
"The solution has no up-front costs because you pay based on the number of messages you publish."
"In our case, we didn't pay for each product separately. We simply paid for all those companies that provided the components."
"​The cost of licensing is very high. One should go for the product only if they need to ensure message reliability and they cannot afford to lose messages.​"
report
Use our free recommendation engine to learn which Message Oriented Middleware (MOM) solutions are best for your needs.
902,588 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
20%
Financial Services Firm
9%
Retailer
9%
Outsourcing Company
9%
Financial Services Firm
29%
Computer Software Company
9%
University
8%
Comms Service Provider
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise1
Large Enterprise4
No data available
 

Questions from the Community

What needs improvement with Amazon SNS?
I believe Amazon SNS could be improved because when you integrate it, you also need SQS, so it is a two-service job. It does not provide filtering or advanced routing, there is no ordering guarante...
What is your primary use case for Amazon SNS?
My main use case for Amazon SNS is that we use it for a messaging service with a publish-subscribe model to send messages to multiple subscribers.A specific example of how I use Amazon SNS for the ...
What advice do you have for others considering Amazon SNS?
The features I find valuable in Amazon SNS are messaging, real-time notifications, and the ability to create an event-driven architecture. I give this product a rating of 8 out of 10.
What needs improvement with TIBCO Enterprise Message Service?
One problem is the license cost. If we take Kafka, it's an open source platform, Apache Kafka, but with TIBCO Enterprise Message Service, the license cost is significantly higher. The message rate ...
What is your primary use case for TIBCO Enterprise Message Service?
The main use case for the product is that for the analytics we will be using TIBCO Spotfire.
What advice do you have for others considering TIBCO Enterprise Message Service?
Currently I am using TIBCO as well as I am getting trained on cybersecurity tools. I am using TIBCO Spotfire currently, the BI tool, Spotfire from TIBCO.
 

Also Known As

No data available
Enterprise Message Service
 

Overview

 

Sample Customers

PlayOn! Sports, NASA, Change Healthcare, FCBarcelona
BNL, SunGard, TUI Group, UTi Worldwide, Yellow Pages Group
Find out what your peers are saying about Amazon SNS vs. TIBCO Enterprise Message Service and other solutions. Updated: June 2026.
902,588 professionals have used our research since 2012.