Amazon SNS vs TIBCO Enterprise Message Service comparison

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

"We have found the key feature of this solution to be the simplicity of sending out notifications."

"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 initial setup of Amazon SNS was easy."

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

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

"The integration between the features is excellent."

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

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

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

"I like TIBCO's ability to create versioned queues and persistent messages."

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

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

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

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

"It is very useful tool. It is also very easy to learn and implement.​"

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

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

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

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

"There could be more integration with other solutions."

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

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

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

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

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

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

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

"The pricing is very cheap."

"Amazon SNS is cheap and I would rate it a three out of ten. The pricing is usage-based."

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

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

"In our case, we didn't pay for each product separately. We simply paid for all those companies that provided the components."