Amazon SQS vs TIBCO Enterprise Message Service

• It provides an always-available serverless queue for workflows or mission-critical processes.
• Is extremely low cost and overall costs to our environments have been negligible.

Read full review

• Tibco EMS performs very well, and it meets our stringent performance requirements for corporate messaging backbone.
• Tibco EMS scales well, and this is another of our stringent requirements.
• Tibco provides good support for the EMS product, and continues to improve it. This is important as we don't want to use something that does not keep up with the changes in the technology landscape.

Read full review

• Almost all of the functionality has been covered by SQS, but they could improve the throughput time.
• Also, they could provide built-in Cloud Watch, so that we can easily configure it without any external efforts.

Read full review

• A bit of lag time between data sync and the data reaching the server for some of our field sites.
• It still seems like a niche product for me with little community support. I didn't know about it before working for a company that deployed it.
• Certain functionality is too complex to setup as compared to other products on the market.

Read full review

• Positive impact - time allocation towards different features
• Negative impact - too many resources dedicated towards debugging
• Positive impact - less manual labor during testing

Read full review

• It promotes the event-driven a-synchronized architecture, boosting the service-oriented design change by decoupling the data generator and the data consumer.
• Applications can be easily "attached" to the data flow to quickly roll out the business added values without having to risk the changes of existing applications or components.

Read full review