Programmer Analyst Advisor
November 01, 2017

Programmer Analyst Advisor

Joe Yee | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with TIBCO Enterprise Message Service

We, at FedEx, use Tibco EMS across the whole company. We use it to address problems where processing does not need to be request & response, and can proceed asynchronously. This asynchronous attribute also allows for decoupling of processing units.
  • 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.
  • Tibco EMS takes can take hours to recover in case there is there is an outage.
  • Tibco EMS does not seem to provide for reservoir or replay. We need a reservoir to offload the messages in case a consumer is down or can't keep up temporarily, and as a followup we need a replay in order to put those messages back to the original JMS destination. Because of this, we had to come up with our own home grown solution.
  • Tibco EMS has contributed to our corporate renewal and retirement of legacy processes, and thereby saving the company maintenance costs.
  • Tibco EMS has contributed to our new application design, and thereby offering our customers better experience.
Tibco EMS was among the top choices after extensive research by our internal R&D team. It was select for performance, scalability, and supportability.
Tibco EMS is well suited in situations where the application can benefit from asynchronous processing. It is not suite for synchronous request/response. It is not suited for permanent storage, as all messages in the JMS topic/queue are supposed to be transitory in nature.