Cleo Integration Cloud vs Mule ESB

• A great platform perfectly integrated with the rest of the company's software.
• Detailed design with simple and easy access from anywhere to our information.
• Multi-location and multi-device access.
• We save on hardware, software and maintenance, by minimizing the user's need for powerful equipment and the programs in charge of managing and configuring them, reducing the investment in their acquisition.
• Cleo integration is in charge of technical maintenance and updates.

Read full review

• It is best suited for Rest API development. Mule ESB uses RAML as an API descriptor which is less complex and easy to understand. RAML is an open standard majorly supported by Mulesoft. Once RAML is developed, it is very easy (a few clicks)to create flows corresponding to the resources defined in the RAML. One can also include JSON schema validation in RAML, and with the use of APIkit router, Mule ESB makes the request validation very easy (it's automatic basically.)
• Mule ESB comes with a large spectrum of community and enterprise connectors. We have connectors for all the major platforms like Facebook, Twitter, Salesforce, SAP, etc. This enables Mule ESB to integrate with the other systems in a faster and more robust way. Mule ESB has many components to fulfill the requirements of each integration (for example batch processing, parallel processing, choice, etc.)
• Mule API gateway is one of the best tools (modules) of Mulesoft's offering. It supports API governance and management very well. One can easily enforce policies on their APIs with API gateway. It enables some of the must-have features in an API solution (i.e. throttling, oAuth, access levels, etc.)
• Implementing a CI/CD (DevOps) environment for Mule ESB is a very easy task. Mule majorly uses MAVEN as its build tool, which in turn makes it best suitable for CI/CD approach. Mule also provides MAVEN plugins for auto deployments to the servers. Mule also has a best Unit testing module which is MUnit. MUnit can be used for both Unit and Functional testing, and it is easy to write and generates coverage reports in various formats.

Read full review

• A fully functional help manual would be good. Some topics have no help at all, "envelopeassemblybycontext" for instance.
• A needed feature is to be able to sort files by either file type (FM, RS, BPS) or by filename. Some of our projects have almost a hundred files.
• Better, more descriptive error messages. Sometimes a ruleset or process fails and the error message is not helpful.

Read full review

• Make sure to not over-engineer shared components. It can complicate development
• Create a roadmap for where you are going - if not, you may miss components
• I suggest getting support, otherwise it could be a difficult learning curve

Read full review

• We have easily improved our EDI tenfold (or more) as far as ease of adding new customers for example
• We have saved a ton of money by reducing chargebacks for missing ASNs for example
• We have improved customer scorecards where they measure our EDI performance such as one large brand name customer we sell wholesale to who originally scored us around 28% and after implementing CLEO we quickly went to a 96%+ score.

Read full review

• Overall a great tool for complex integrations

Read full review