Mule ESB

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.

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).

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.

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.

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.

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.

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].

Batch, ESB and proxy can be done easily.