Reviews (1-5 of 5)
February 27, 2019
Score 10 out of 10
We began experimenting with Mulesoft about 2 years ago, and it has grown into a complete corporate competency within a year, complete with its own IT shared service department of developers, managers and support administrators. While the core department does all the work and management, each division throughout the company has one or more developers who leverage the core team for major projects, but can build and utilize approved pre-built modules as needed. It was brought in mainly for us to connect internal legacy databases and systems to our Salesforce instance, but we find it has a lot of other utility uses in building API’s to connect just about anything. The main use case would be to extract order data from our Infor ERP and Oracle-based repositories and pipe it into Salesforce.
- Extracting order and invoice data from our Infor ERP and related Oracle-based repositories, Mule then pipes it into Salesforce, enabling us to gain a 360-degree view of the customer order life-cycle.
- We have a very complex pricing tool written in a .net application that is very difficult to get information extracted from for analytics. With Mule, we can easily pull the data out and load it into a repository for our BI tools to go after.
- Mule lets us connect our legacy CRM system (built on .net) easily to both Salesforce and our Data Warehouse for faster analytics and access to historical customer interactions. Additionally, since our Salesforce instance it new, it aids in the roll-on of new OEM partners and loading of their historical data.
- As with any system, setting up secure agents and firewall permissions was a bit of a challenge. We ran into a few SSL and certificate roadblocks that required some extra follow through with out networking staff. I think an easier plug-and-play approach with more documentation would have helped, but since Mule is newish, I assume documentation will simply improve over time.
- Lack of decent in-person training was a challenge early on, but we created our own competency internally to resolve that so haven’t had to look outside for over a year now. Recommend any newcomers follow the same path, and ensure you have redundancy in case an important resource departs.
- Pricing could be a little better, there are other options (Red Hat, etc.) and I feel like the price is only what it is because it has the Salesforce brand behind it.
Read this authenticated review
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.
My organization has partnered with Mulesoft and implemented Mule ESB solution for their esteemed clients. We are using Mule ESB to enable an API-first approach for the clients. API is an essential element in the digital transformation of any organization and Mule ESB is best suited for API development. Mule ESB Enterprise Edition comes with all the required tools for the API cycle. Mule ESB is suitable for both on-premise and cloud approach. Their licensing model enables the organizations to select the best suitable tool stack for them, be it an on-premise solution (suitable for banks, etc.) or a cloud solution (CloudHub).
- 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.
- Anypoint Studio is the primary IDE to do the Mule ESB development. Although Anypoint Studio is a good tool, and makes the life of a developer very easy with its drag and drop features, it seems too slow at times. Running a slightly large application on the local machine is a bit of a pain because of the slowness of the IDE.
- I personally feel the Database connector which Mule ESB provides is not very easy to use. It does not fetch metadata from the database, which complicates the mapping. Calling a stored procedure from Mule ESB is a very hectic task because one haa to write DTO classes for complex data types.
- Documentation provided by Mulesoft doesn't seem complete and sufficient. Sometimes it's very hard understand the configuration of a particular component because most of the documentation doesn't have detailed description.
Read Deepak Kushwaha's full review
Well Suited for:
- REST APIs.
- Rapid API Development.
- Most suitable for integration with SFDC.
- Batch processing.
- Parallel processing.
- Integration with Database.
- Exposing SOAP services.
- Small organizations, because it is super costly.
August 21, 2018
Score 9 out of 10
Mule ESB will be the integration platform for our company. Right now, many of our services are created manually, and we are leveraging Mule to insure consistency and expedite service development. As part of this program, our plan is to service enable all parts of our business logic, and make them transparent. This will allow consumers to build UIs as needed in order to support Line of Business workflows.
- Connectors allow for easy integration
- Design of services allows for reuse
- Great support community available
- Services may be deployed to the Cloud
- 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 this authenticated review
Mule works well in a large enterprise. Smaller companies may want to look at the Open Source version which lowers the investment. Mule handles complicated and straight forward transactions well. Mule Support can assist with foundational components and design paradigms, making it easier for developers to be on-boarded to build out the services required by the Business Unit.
February 22, 2018
Score 8 out of 10
We helped several customers implement Mulesoft for integrating their various systems. We have used it mainly to integrate Salesforce with various other systems including homegrown systems using SOAP and Rest web services.
- As an ESB it provides great flexibility to add/remove systems in the integration easily. Highly scalable.
- Supports any kind of system to be integrated, Supports Java.
- Experienced resources will be required to build complex integrations.
- It's not perfect to be used as ETL. There are other ETLs in the market which offer better features overall but when it comes to ESB features, Mule is much better.
Read Ankit Goyal's full review
If 3 or more integration systems need to be integrated or there will be a scope of adding more in the future, Mule ESB is well suited.
December 13, 2016
Score 10 out of 10
We are using the cloud version of Mule. All our flows are deployed in the cloud hub with proper proxy and ESB flows. Yes, it is being used by the whole organization. It addresses all our insurance enrollment, claim management, and document management [needs].
- Considering all other ESBs in the market, it is very light weight and easy to develop.
- Performance is very fast as everything is Rest. That's the reason Netflix and Amazon are using this ESB.
- All the complex transformation can be done with the help of Dataweave. It is built on top of Scala and lambda.
- Logging the Database query in production with out changing the log4j level
Read KamaL Vachiravel's full review
Batch, ESB and proxy can be done easily.