Amazon Simple Notification Service (SNS) vs. TIBCO Rendezvous

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Amazon SNS
Score 8.0 out of 10
N/A
Amazon Web Services offers the Amazon Simple Notification Service (SNS) which provides pub/sub messaging and push notifications to iOS and Android devices. It is meant to operate in a microservices architecture and which can support event-driven contingencies and support the decoupling of applications.
$0.01
per 1 million
TIBCO Rendezvous
Score 6.0 out of 10
N/A
TIBCO's Rendezvous is message oriented middleware. The software uses messages to enable distributed application programs to communicate across a wide variety of hardware platforms and programming languages.N/A
Pricing
Amazon Simple Notification Service (SNS)TIBCO Rendezvous
Editions & Modules
API Requests & Payload Data
$0.01
per 1 million
API Requests
$0.50
per 1 million requests
Notification Deliveries
$0.50
per million notifications
No answers on this topic
Offerings
Pricing Offerings
Amazon SNSTIBCO Rendezvous
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Amazon Simple Notification Service (SNS)TIBCO Rendezvous
Considered Both Products
Amazon SNS
Chose Amazon SNS
Amazon Simple Notification Service (SNS) is well integrated in AWS and has been there since the early days of public cloud. It is a cost effective and very inexpensive solution to meet the needs of event notifications and custom messaging. Wish to share that there is …
Chose Amazon SNS
Amazon’s SNS is incredibly easy to set up compared to the more powerful, but complex, Kafka flavours.
Chose Amazon SNS
I worked with Adobe campaign 2 years ago and comparatively, SNS is way better and easier to integrate with. There's a lack of latency with SNS and better customer support. Easier to group with subscriptions and easier to work from the command line with the use of the SDK. All …
Chose Amazon SNS
No obvious difference. We chose AWS SNS, as we are an AWS EdStart company and built on the AWS stack already.
Chose Amazon SNS
SNS helps in integrating with other AWS components which are used in development such as Lambda, APIGW, S3 and DynamoDb easily. If used with third party software like PagerDuty, it makes the development and integration more complex. It is used mostly for publishing and …
Chose Amazon SNS
We use AWS and becasue Amazon SNS can be easily integrated with AWS.
Chose Amazon SNS
Amazon Simple Notification Service and PagerDuty have been used by various organizations. Amazon SNS is ideal if you're within an AWS environment. PagerDuty is used when we are working outside of Amazon Web Services. Though PagerDuty is more expensive than Amazon SNS they do …
Chose Amazon SNS
SNS is already integrated with other AWS services. I can reuse lists or topics.
Chose Amazon SNS
We have looked at other service providers, including the local service providers as well, but Amazon SNS stood ahead of all in terms of service availability across the globe and cost-effective plans per notification SMS. Moreover, we can also use Amazon SNS along with other AWS …
Chose Amazon SNS
Common confusion between SNS and SQS. SNS directs information to its subscribers without any effort on the subscribers or individuals' end. SQS gathers the information and then the individual has to almost go find it. They do similar things but in a space where information can …
Chose Amazon SNS
We have opted ultimately for AWS SNS once configuration was set topics and subscriptions setup. Site 24 and US Monitor are considerations to this product, but incur cost outside of Amazon, so not best for starting up for our needs.
Chose Amazon SNS
The main reason we chose Amazon SNS is for easy integration with all the workflows in AWS. The other alternatives can be (and really are) best in specific points, but the main strength of SNS is that is one service of AWS, so we don't need to complicate things in our …
Chose Amazon SNS
Our company prioritizes using AWS offerings unless there is a strong use case for using something within Azure. SQS is a similar service that solves different problems and we are using it in conjunction with SNS.
Chose Amazon SNS
Our clients are mostly on AWS, so it was easy for us to use Amazon Simple Notification Service (SNS) and to integrate it with current applications.
Chose Amazon SNS
We use EC2 instances to train ML model against a heavy volume of data. When the model is trained (i.e. loss reduces to a certain level), we push notification to all the stakeholders to notify them the new model is available. To achieve it, SNS is the most simple and cost …
Chose Amazon SNS
We use a lot of services from AVS, and it's easy to set up all services between each other.
Chose Amazon SNS
Many products, including PagerDuty, can be used to notify stakeholders when alarms are triggered. SNS is only suitable for non-emergency email alerts, and integration with CloudWatch is its only advantage. If you want to be notified of an issue by email, SNS can be configured …
Chose Amazon SNS
SNS is much more customizable compared to SES and allows for many more delivery methods. While it is better for email-based notification services, not being able to send notifications via SMS limits your app functionality considerably. Being able to switch message delivery …
Chose Amazon SNS
As I mentioned previously, I wish we had gone with a different service such as a Mixpanel or OneSignal as they are reputable in the space and are known for their strong support and documentation. AWS SNS was the way to go for us at the time we chose it due to the fact that we …
TIBCO Rendezvous
Chose TIBCO Rendezvous
TIBCO EMS could be preferred to TIBCO RV for more reliable communication, because EMS guarantees data should not lost during network transmission. The plus point for EMS is that it's based upon JMS specification, so the integration with Java is very appreciated by programmers. …
Chose TIBCO Rendezvous
Messaging is a very old concept offered by many software vendors, Although Tibco Rendezvous is very well recognized non-open source solution.In my opinion Tibco JMS is mostly used in all the applications than the IBM MQ and mule software -
Chose TIBCO Rendezvous
TIBCO EMS provides centralized server administration to manger the delivery of services in run time
Best Alternatives
Amazon Simple Notification Service (SNS)TIBCO Rendezvous
Small Businesses
AWS IoT Core
AWS IoT Core
Score 9.9 out of 10
AWS IoT Core
AWS IoT Core
Score 9.9 out of 10
Medium-sized Companies
Apache Kafka
Apache Kafka
Score 7.7 out of 10
Apache Kafka
Apache Kafka
Score 7.7 out of 10
Enterprises
Google Cloud Pub/Sub
Google Cloud Pub/Sub
Score 9.0 out of 10
Google Cloud Pub/Sub
Google Cloud Pub/Sub
Score 9.0 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Amazon Simple Notification Service (SNS)TIBCO Rendezvous
Likelihood to Recommend
8.0
(0 ratings)
9.0
(0 ratings)
Usability
9.0
(0 ratings)
10.0
(0 ratings)
Support Rating
8.4
(0 ratings)
5.0
(0 ratings)
User Testimonials
Amazon Simple Notification Service (SNS)TIBCO Rendezvous
Likelihood to Recommend
Using SNS for any notification use case where available is the default and defacto solution. It directly integrates with SES to configure both incoming email and email delivery responses.
Additionally, any notifications, such as CloudWatch alarms, are a good use case for SNS topics and allow us to fan out delivery as needed (pagerduty, email, etc)
Read full review
I would recommend TIBCO Rendezvous to a colleague for several reasons. One of most important could be to use it on different operating systems (i.e. Windows, Linux) and be able to create real-time communications. Another reason could be the easy message addressing: only those who subscribe to specific subject receive the messages.
Read full review
Pros
  • Built in for quicker setup within AWS ecosystem.
  • Trusted as you control the users and configuration via IAM and easy access controls.
  • Can be sent to S3 simple storage or for long term storage if required.
  • Can be used in many regions, same configs.
Read full review
  • Faster broadcast data.
  • Exchange data across multiple networks.
  • It works without a central server.
  • Messages filtered based on specific subject.
Read full review
Cons
  • At times you receive access denied errors which are annoying.
  • Rarely do you receive internal failure errors where you can't access the information. It is rare but it does happen.
  • You are required to add an MWS Authentication Token every so often. I wish it would pull that information automatically for you so you don't have to go searching for it.
Read full review
  • RV doesn't support centralized administration to manage the delivery of synchronous messages in run time without changing its configuration which was done in code base
Read full review
Likelihood to Renew
No answers on this topic
Not likely to renew or buy the license as they are using the TIBCO EMS as the primary mode of communication.
Read full review
Usability
It is useful for applications developed using event driven architecture. It helps in tracking and logging the events in a very timely and efficient manner. The dashboards are a little difficult to implement. But overall it is very easy to integrate with other AWS services like Lambda, API GW, S3 and DynamoDB. The permissions to access should be resolved before using it.
Read full review
Attending an official TIBCO classroom training, where you can have an active participation with an expert teacher, you can find the answers to all yours needs. In any case, if you are not satisfied on your requests, the teacher takes the time to find the best solution.
I had the opportunity to attend one and I could learn all features I needed for my business: now I can say TIBCO Rendezvous is very usable.
Read full review
Support Rating
The AWS documentation is well maintained and has lots of information which makes it easier for developers to refer to and develop applications in a fast efficient manner. It is well documented with examples which is easy to understand and implement. You can also get help by posting into forums from like-minded developers.
Read full review
I never needed support for TIBCO Rendezvous. I always used it without any issue and until now I don't remember some situations where it interrupted its 24/7 uptime.
Read full review
Alternatives Considered
Amazon Simple Notification Service (SNS) is well integrated in AWS and has been there since the early days of public cloud. It is a cost effective and very inexpensive solution to meet the needs of event notifications and custom messaging. Wish to share that there is considerable number of developers who can easily build solutions using AWS SNS. So, training costs are minimal. Other solutions are emerging and we are seeing a great usage especially of Firebase notifications because of its very neat integration with open source cross platform hybrid app frameworks like ionic, xamarin. SNS needs to become better and should have plugin support for the mobile application developers using low code/no code tools too.
Read full review
TIBCO EMS provides centralized server administration to manger the delivery of services in run time
Read full review
Return on Investment
  • Cost of alert calls to the different stakeholders across different geographies have gone down since using Amazon SNS.
  • Amazon SNS has saved a lot of time for the employees that they used to spend to call multiple stakeholders so they can now focus more on productive tasks.
  • Amazon SNS usage needs prior knowledge of programming.
Read full review
  • Positive - RV supports faster delivery of messages to multiple subscribers (asynchronous communications)
  • Negative - RV doesn't support centralized administration and guarantee delivery is more accurate like EMS Persistent delivery mode
Read full review
ScreenShots