Anypoint Platform vs TIBCO Enterprise Message Service

• API Manager provides easy API Policy Governance. You do not have to manage multiple platforms for managing the policies.
• Supports hybrid Mule EBS environments. You can configure both CouldHub-based and on-premise-based API using Mulesoft API manager in a similar manner.
• It's very easy to implement API proxy.
• User friendly UI.
• Single platform to manage all.

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.

Read full review

• Has more features than what we really need so we're paying for more than we use. Sort of like paying for an Abrams tank when all we really need is a Toyota Corolla.
• Not a value product, tends to be expensive.
• Takes a while for developers to learn to use Mulesoft Anypoint.

Read full review

• A bit of lag time between data sync and the data reaching the server for some of our field sites.
• It still seems like a niche product for me with little community support. I didn't know about it before working for a company that deployed it.
• Certain functionality is too complex to setup as compared to other products on the market.

Read full review

• If you are a big size organization that heavily uses API's and SaaS-based integration, Anypoint platform is great. However, if your API implementations are not in Mulesoft, hosting just API specs is not worth it in terms of ROI.
• Mulesoft uses propitiatory language which makes it difficult to write custom code when required, some other iPaaS platforms like Webmethods.io uses nodeJS which makes it easier to write custom code. In short, when you need to write custom code, building and supporting is a challenge.

Read full review

• It promotes the event-driven a-synchronized architecture, boosting the service-oriented design change by decoupling the data generator and the data consumer.
• Applications can be easily "attached" to the data flow to quickly roll out the business added values without having to risk the changes of existing applications or components.

Read full review