EMS as a strong JMS provider
November 15, 2017

EMS as a strong JMS provider

Hugo Romani Cortes | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with TIBCO Enterprise Message Service

TIBCO Enterprise Message Service is used as the main messaging broker for the entire middleware. It represents the backbone of the middleware providing asynchronous mechanism between applications.
Thanks to the offered patterns (publish-subscribe / point-to-point) we are able to integrate complex or simple applications. With EMS we are able to implement pivot model and we are thinking of moving to a more modern approach (microservice architecture). We need to asses EMS performance in a microservice architecture.
  • TIBCO Enterprise Message Service is able to natively distribute the traffic load between instances. Thanks to an easy configuration we can create a farm of EMS instances
  • TIBCO Enterprise Message Service is a very easy configurable product. The default configurations files are property files that allow a simple configuration.
  • TIBCO Enterprise Message Service offers a good set of QoS that can be configured at client level and server level (i.e. message persistence, acknowledgment, etc.)
  • In case of distributed instances, TIBCO EMS supports a limited version of shared directories. TIBCO should enhance the number of supported file systems.
  • The last admin UI offer a modern view but requires the usage of an external product (TIBCO Enterprise Administrator) + the ems agent. A standalone admin UI would be appreciate despite community tool such as Gems.
  • TIBCO EMS supports only tcp connectivity. It would be great if EMS can supports other protocols such as MQTT.
  • TIBCO EMS is highly expensive compare to open source solutions (Active MQ).
  • TIBCO supports can provide good support and advanced features such as TLS 1.2 support (refer to PCI constraints).
  • In-person training
It's required to get a training (online or in person) in order to get feedback from the trainer and get some tips regarding the configuration. Just like all TIBCO products, a lot of parameters can be tuned (i.e. re connection after a timeout, etc...) and must be explained in order to understand the meaning.
2 days of training is enough on this solution as it's not really complex
TIBCO Enterprise Message Service was selected because of the contract with TIBCO. We generally see company buying other TIBCO products such as TIBCO BusinessWorks and then TIBCO offers some discount on their "minor" products.
If I would compare technical capabilities of EMS against another provider, I would select EMS because of its robustness and easy maintenance.
Within a full TIBCO environment, EMS integrates very well with other components.
In case of messaging pattern requirements, EMS can fits most of technical challenges especially for small messages.

It is highly recommended to not use EMS in case of batch transfers, especially when we want to exchange big content (i.e. file content).
EMS can be a bottleneck and must be recovered quickly if we don't want to loose messages (i.e. subscriber down on a queue).