Does the job, but there are better alternatives
September 17, 2020

Does the job, but there are better alternatives

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

Overall Satisfaction with TIBCO Enterprise Message Service

Its used as a message bus to send messages between topics and queues to communicate between different applications. It is used across our entire organization. It solves things like messaging, processing flow via queues, message distribution via topics, persistence since messages are durable, etc.
  • Mostly reliable in production.
  • Good Java support.
  • Good performance.
  • Needs a better admin GUI. They only offer an unsupported tool called GEMS, which is weak.
  • Could be enhanced by being more open - like distributing the client libraries on standard library repos like Maven Central,
  • Should be more cloud-friendly. It runs as cloud-unfriendly appliances or requires specialized storage.
  • It was better than the previous generation TIBCO products we used.
  • The closed nature of the client libraries and documentation wasted a lot of our dev team's time because we needed logins to the TIBCO portal to view it.
  • TIBCO sample code was not very organized and very difficult to understand.
Rabbit is much easier to use and get started with thanks to its online, free, public tutorials and availability of the software on public repositories like Dockerhub, Maven Central, NuGet, etc.
Anything offered as an appliance is usually difficult to work with and very proprietary. We find more widely-used competitors like RabbitMQ nearly as good. JMS as a standard kind of failed since it didn't dictate the wire format, and this is why we are moving away from EMS at this point.