Try our new research platform with insights from 80,000+ expert users

Amazon SNS vs TIBCO Rendezvous 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
11
Ranking in other categories
No ranking in other categories
TIBCO Rendezvous
Ranking in Message Oriented Middleware (MOM)
6th
Average Rating
8.0
Number of Reviews
2
Ranking in other categories
Business Activity Monitoring (4th)
 

Mindshare comparison

As of May 2025, in the Message Oriented Middleware (MOM) category, the mindshare of Amazon SNS is 6.5%, down from 7.1% compared to the previous year. The mindshare of TIBCO Rendezvous is 6.2%, up from 4.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Message Oriented Middleware (MOM)
 

Featured Reviews

Bireshwar Adhikary - PeerSpot reviewer
The best service available with easy message flow and a pay-as-you-go model
Messages easily flow from publisher or application to subscriber. You can also flow messages from publisher to SNS with an https-like mediator. Amazon SQS is there, so message queue services are also there. The message transports to the service provider such as Redshift, the SQ bucket, Teams, Splunk, or any other message service. The solution has no up-front costs. Messages flow much more quickly than in the past. They used to run a bit late after being published.
MP
Good communication, stable, and responsive support
TIBCO Rendezvous has some difficulties to be deployed in a cloud environment. We use it typically in a bare-metal infrastructure. We can use a cluster of the nodes of the other companies. For example, we cannot deploy in the cloud infrastructure, but the companies cannot deploy TIBCO Rendezvous in a cloud environment without issues. It is very easy to start the TIBCO Rendezvous in the DMO infrastructure. The first time we deployed TIBCO Rendezvous, we used it to support individual transaction integration between the distributed and mainframe applications. We spent approximately five days deploying TIBCO Rendezvous in the companies in their application. It's very fast to implement and to use.

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."
"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 of Amazon SNS is speed. It's really fast."
"Amazon SNS has SMS notifications as well. Most of the other solutions have only email notifications."
"Stability has been good for us. It is quite high."
"Messages easily flow from publisher or application to subscriber."
"The initial setup of Amazon SNS was easy."
"TIBCO Rendezvous has a strategy to communicate in the network between the DMO of the product. They provide strategy through secure communication. They use the UDP protocol, but It's not a resilient protocol. They put another protocol to create a type of guarantee. It has a high level of communication between the DMO. This is the best capability the solution has."
 

Cons

"Messages should flow through a gateway without the need for a mediator."
"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."
"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."
"There needs to be more documentation on the integration with different platforms."
"We would like the integration with third party applications to be improved within this solution."
"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."
"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."
"TIBCO Rendezvous is currently restricted in a cloud environment and it would be more useful in a hybrid cloud setup. It does not work correctly in a cloud environment alone. This is something they can improve in the future."
 

Pricing and Cost Advice

"The solution has no up-front costs because you pay based on the number of messages you publish."
"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."
"One can use the tool for free."
"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."
"Amazon SNS is cheap and I would rate it a three out of ten. The pricing is usage-based."
"Their pricing is competitive. I would rate the cost four out of five."
"There is a license needed to use this solution."
report
Use our free recommendation engine to learn which Message Oriented Middleware (MOM) solutions are best for your needs.
851,823 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
28%
Computer Software Company
14%
Manufacturing Company
12%
Media Company
5%
Financial Services Firm
57%
Computer Software Company
15%
Energy/Utilities Company
4%
University
3%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Amazon SNS?
The most valuable feature of Amazon SNS is speed. It's really fast.
What needs improvement with Amazon SNS?
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.
Ask a question
Earn 20 points
 

Also Known As

No data available
Rendezvous
 

Overview

 

Sample Customers

PlayOn! Sports, NASA, Change Healthcare, FCBarcelona
Agilent Technologies, Vodafone Hutchison Australia
Find out what your peers are saying about Amazon SNS vs. TIBCO Rendezvous and other solutions. Updated: April 2025.
851,823 professionals have used our research since 2012.