Likelihood to Recommend The tool has potential. Its capabilities and visual aspects could be considered rather basic but this might improve, particularly if the business intelligence/analytics aspect is leveraged. Once running well, it could allow (perhaps smaller) companies to successfully improve their customers' experiences through digitalizing customer journey - and we all know that customer loyalty goes a long way. However, whether or not the tool is comprehensive enough to deliver this for larger companies with more complex, multi- and omni-channel interactions is yet to be seen...
Read full review If you need a robust, extensible, reliable Enterprise Service Bus, with "Enterprise" being the key word here, TIBCO [Enterprise Message Service] will be able to fulfill every expectation. As proof of concept, or ad-hoc implementations, it might not be as well suited due to the infrastructure required.
Read full review Pros Face-lifted platforms: CX Messenger (formerly Sonic), CX Monitor (formerly Actional), CX Process (formerly Savvion) User-friendly UI Relatively painless implementation 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. Joe Yee IT Strategic Technical Advisor
Read full review Cons Standard edition is significantly lighter touch than the (pricier) Enterprise version There are similar solutions on the market that are competitively prices and offer positive user experience Data migration can be tricky at times Read full review 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. Read full review Likelihood to Renew EMS is a solid system and I see no reason to abandon it, in fact I am eager to see what the next versions will offer and future road maps. Knowing we have support to help us in case of problems is invaluable, both in case of critical issues and to improve overall performance.
Read full review Alternatives Considered We also use other messaging products:
IBM MQ , especially for integration with other systems (server2server), which has been an industry standard for a long time, and
Apache Kafka for cloud-native applications. EMS is a worse option compared to them, but it is still acceptable.
Read full review Return on Investment As our customers vary in size and maturity, the ROI ranges accordingly. For younger, smaller businesses this is a useful tool. Digitalization of he customer journey has certainly helped save time and efforts in many cases. For more mature market players the tool is not always comprehensive enough. Dashboard and report personalization take time and efforts, and sometimes it feels that a dedicated BI tool would be a more suitable solution. Read full review 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 Read full review ScreenShots Aurea Process Screenshots