TIBCO Enterprise Message Service integration
June 08, 2023
TIBCO Enterprise Message Service integration
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with TIBCO Enterprise Message Service
We use TIBCO Enterprise Message Service for sync as well as async messaging requirements. All applications interact via this tool for pure integration purposes. JMS is a well defined integration protocol and the benefits of this pattern enabled us to load balance and persist transactions out of the box. Retries were handled without development effort and this product is capable of high volumes while maintaining high throughput and performance. We have approximately 500 applications which utilize this messaging service some of which also perform XA type of transactions which this product supports. JMS also provides specific JMS headers which we use for correlation and monitoring purposes. The product passes all our requirements for end to end integration requirements.
- Asynchronous integration
- Load Balancing
- Fault Tolerance
- Publish Subscribe patterns
- Handles high througput
- Throttling features
- Easily Scalable architecture
- Provide Message Age on a queue is not availbale
- Licensing Model can be improved
- Direct Integration into other JMS products
- Better log file structure, currently all activity resides in the same log such as payload, correlation info, exceptions etc
- Ability to achieve high performance and throughput
- Ability to persist messages upon failures thereby guarantee's zero message loss
- Ability to easily scale TIBCO Enterprise Message Service instances as load increases
- Improved developer productivity as TIBCO Enterprise Message Service requires minimal coding
- Quicker time to market as the configuration / onboarding can be automated with this tool
- Ability to onboard more clients/consumers as the tool can handle large volumes seamless
- Improved visibility on the end to end process as the product provides monitoring by using JMS header information
MQ was way more expensive and it is limited in many ways against TIBCO Enterprise Message Service. MQ does not allow easy topic to queue bridging and also requires much more configuration for basic types of activities. Does not support all of the same JMS headers that TIBCO Enterprise Message Service offers. Monitoring is not out of the box either and alot of development is required in this regard.
Do you think TIBCO Messaging delivers good value for the price?
Yes
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