Amazon SNS vs TIBCO Enterprise Message Service comparison

"Stability has been good for us. It is quite high."

"The integration between the features is excellent."

"It's a simple communication service that allows us to communicate with customers."

"The initial setup of Amazon SNS was easy."

"Messages easily flow from publisher or application to subscriber."

"The most valuable feature of Amazon SNS is speed. It's really fast."

"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."

"Amazon SNS has SMS notifications as well. Most of the other solutions have only email notifications."

"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.​"

"The Enterprise Messaging Server will store the message and wait for other subscribers to come onto the network."

"The setup was done by TIBCO. It has been stable and has a server."

"​The initial setup is straightforward and the product documentation is very good.​"

"TIBCO Enterprise Message Service's most valuable features are rapid zero-code integration and its large number of adapters and plugins."

"It allows us to achieve synchronous as well as asynchronous communication with the added advantage of making the communication reliable."

"We have implanted the core middleware solution for the organization using this product and it is responsible for communication between different applications."

"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."

"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."

"There needs to be more documentation on the integration with different platforms."

"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."

"We would like the integration with third party applications to be improved within this solution."

"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."

"An area for improvement would be integration with the API layer."

"Overall, my experience with the support team has been disappointing."

"TIBCO also has its proprietary line of cloud-based applications, but specifically, these two products are not cloud compatible."

"I would like to see better integration with Java and Apache Kafka."

"​Since all the communications goes through this product, it acts as a single point of failure."

"The pricing is very cheap."

"Their pricing is competitive. I would rate the cost four out of five."

"The solution has no up-front costs because you pay based on the number of messages you publish."

"One can use the tool for free."

"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."

"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.​"