TIBCO Messaging - solid and reliable
March 15, 2024

TIBCO Messaging - solid and reliable

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Modules Used

  • TIBCO Enterprise Message Service

Overall Satisfaction with TIBCO Messaging

We use TIBCO Messaging mostly to provide reliable communication from systems to middleware processes (mostly developed as well on TIBCO BusinessWorks) or the other way round. Business tends to require a very fast communication layer where messages can be persisted, so no request gets lost in case of any issue, and TIBCO Messaging happens to be a great solution in this scenario.
  • Low latency delivery of messages, so messages can be processed almost at the very same time when they are published.
  • Robustness through an efficient fault-tolerant solution that works particularly well over cluster architecture.
  • Requests and queues can be easily configured so old/obsolete messages expire spontaneously after a certain time.
  • In terms of TIBCO Messaging, it would nice to have a more out-of-the-box way of linking its objects (queues, topics) directly to those of other popular solutions like MQ or Kafka.
  • Not being able to filter (that is, using selectors) through patterns/subtexts on the message body is missed on occasions.
  • Given the current trends and state-of-art, lift & shift of on-premise EMS clusters to cloud architectures should be more directly attainable.
We chose TIBCO Messaging not just for its performance but because it looked like the natural way to pave our existing TIBCO Integration architecture. Setting up TIBCO EMS servers and objects seems more straightforward than with most of competitors. It is easy to configure and easy to use and understand.

Do you think TIBCO Messaging delivers good value for the price?

Not sure

Are you happy with TIBCO Messaging's feature set?

Yes

Did TIBCO Messaging live up to sales and marketing promises?

Yes

Did implementation of TIBCO Messaging go as expected?

Yes

Would you buy TIBCO Messaging again?

Yes

Considering our experience is mostly based on TIBCO Messaging, the fact of having been using and choosing it for over 15 years now surely means something. It is not just that it works well on point-to-point persistent integrations, but its implementation of topics allows a distributed integration to be achieved as well, always with very low latency.