In our experience, the product performs really well when interfacing systems with ERP's through SQL server database tables, but we've even made some interfaces with the web service functionality included with the magic xpi integration platform. Also, we've made some SAP Business One - SAP Business One interfaces, for copying information from one company to another.
If you’re bringing anything into Salesforce you should just invest now into Mule, you will get your money’s worth and find a myriad of uses to build APIs between many other systems. Once you build a component you can easily reuse it as a building block to attach to another source/destination. This makes it easy to ramp up quickly and spread usage of Mule throughout your enterprise. A good value for medium to large companies, but probably cheaper to outsource your job to a consulting firm if you are smaller.
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.
Although the scenarios may be online, the main service usually freezes and the processes can't transact any data. With a single restart of the service, the processes will be functioning again.
The support for more applications would be nice, even though there is a nice number of them.
The licensing for the software may be a little confusing.
Honestly, we have only used and evaluated magic xpi platform because of the recommendation of our SAP Business One main supplier, who has previously used the platform for their developments. So far, we have no regrets with the acquisition of the platform and we are very happy with it's performance until now.
The implementation time for this kind of projects has been greatly reduced.
Certifying an In-House resource in the Magix xpi platform is probably the best option, considering all of the projects that can be developed in the future without the need of an external consultant.
The processes that have been automatized with the Magic xpi platform helped reduced human error and the time those processes took to finish.