Mule ESB Reviews

We're using our Mule ESB mostly for integration projects for multinational companies that do business on a B2C or B2B basis. We also work with companies with multiple third-party vendors employed under their payroll. The Mule ESB helps integrate data from third-party systems or vendors with the company's systems and all the different platforms associated with a particular company.

The most valuable feature of MuleS ESB is its API-led architecture. It provides a unique, user-friendly, and scalable architecture for hosting APIs. The platform also gives you visibility into how applications are set up.

The API management capabilities are exemplary. You can apply security policies to most applications, monitor logs, and get analytical data on request reception, response generation time, associated APIs, endpoints, and inbound and outbound messages.

We use it for creating APIs and integrating with different messaging systems.

Most of our use cases are for Salesforce. So, the connectors for Salesforce have been really helpful. They've made development two times faster.

Mostly, we use Mule ESB for an integration piece where the source and destination need to be integrated with user-defined logic in between. This integration involves an API-led connectivity approach, which is a major component in MuleSoft.

The most valuable features of Mule ESB are DataWeave, which is the core of MuleSoft, and batch processing methods, such as batch processing for bulk loads and parallel processing for asynchronous tasks.

I manage a team to handle various integrations using Mule ESB and lead the integration practice. We are a platinum partner of Mule, implementing Mule solutions for our clients.

Mule ESB has provided a centralized control plane for distributed deployment, making it a useful solution.

My current client is using Oracle Fusion Middleware as their integration platform, and they want us to build a new platform enabling the same functionality using MuleSoft. 

Mule ESB has a user-friendly design, and everything is in one place. The API and architecture are popular right now. Also, MuleSoft has a large and supportive online community. 

I use the solution in my company to deal with use cases, like certain developments in webMethods.io. I had used the tool to deal with API implementation, which was something that was related to integration with the help of APIs. We used to provide APIs to our partners as an organization so that they can use our API and the logic we have written under the APIs, which can help them get the information they want based on the APIs.

From an improvement perspective, there should be fewer coding challenges for users in Mule ESB.

I'm a consultant in a bank in Kuwait. I suggest good products for companies that are seeking my advice.

One of the important features of Mule ESB as an enterprise architect is that it should be scalable. It should be customizable for different kinds of clients. 

For client A, we need only two products. For client B, I need to group one and three. The product must be customizable for each. 

The product should be able to identify who is calling and what the components are. We need to return them to the calling point. Mule ESB covers most of these requirements.

Last month, the Guardian had a post saying that Mule is one of the best products for enterprise applications.

Mule ESB excels in orchestrating workflows and seamlessly integrating with business implementations while keeping technical details hidden. It also offers protocol transformation, converting between different protocols, and supports service exposure to customers while maintaining technical invisibility.

We utilize data transformation capabilities extensively. For complex cases, we employ the SSLi engine, whereas for simpler ones like healthcare or response data, such as EDI 270 or 271. We prefer to use an external XRT engine instead of handling it within the ESB for ease of management. For smaller data transformations, we rely on DSPS.