We use Mule ESB for integrating with third-party vendors. Mule ESB bridge between internal systems and third-party systems. Additionally, we use it for enterprise, web, and APIs services.

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

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.

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. 

We use this solution when we have integrations and need to connect to SAP or to some Q mechanisms like ActiveMQ or RabbitMQ. The applications we develop are for administrators. We are customers of Mule ESB. 

Our clients are using the solution for app-to-app integrations and B2B integrations.

We used Mule ESB for the integration between two or three organizations.

At the moment, we are using MuleSoft 4, for which I am a certified developer. We use version 4.3. 

We use this solution to integrate with other software applications.

Now, we are running almost 50 integration APIs, and will have over 1 million billable transactions.

The solution can be deployed on cloud or on-premises. I'm using version 4.2.

ESB is middleware for interacting with multiple heterogeneous systems. Our most critical use case is ensuring the connection is ready, systems are interacting seamlessly, data conversion is happening, and the business logic is being applied. 

The solution is the middleware between the producer and a consumer, and we ensure that the producer is creating the data according to the consumer's requirements. If any orchestration or any transformation is necessary, then MuleSoft performs that. 

When I worked for the Sprint telephone company, we used the solution as a bridge between their legacy systems and the front end. We developed a lot of the functionality, for example, logging into users' accounts and activating cell phones.

This is an enterprise service bus, and it is mainly used for transferring data. For example, it is used when System A has the data that needs to be sent to System B. 

Our use case is transferring the enterprise data from one enterprise to a different enterprise. We use different types of connectors or connections to get the data, transform the data, and send it to a system. Almost all the integrations work in the same manner.

It can be deployed on-premise, but nowadays, most of us prefer cloud-based solutions.

We use this solution to get data.

I am a solution architect where I design solutions by leveraging integration tools, low-code platforms, and BPM platforms. We are using Mule EBS for transformation purposes.

We are using the on-premises version of this solution.

We were using it for EDI. We were using it for integration between RFID portals and our ERP system. We were also using it for the integration of customer data between the CRM and the ERP systems. I am no longer using it because I changed the company.

We were using the cloud version.

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

I use Mule ESB to exchange data between four or five systems at one time. We exchange government organizations' data.

We primarily provide services using the Mule ESB. We use it to integrate multiple systems.

I used the free trial account to test the product, it allows 10 days free trial.  

I'm a software engineer and a user of Mule ESB. 

We use Salesforce to store the most valuable information in our system. We have many clients that request this data, and we send it to them using the Mule ESB solution.

We normally use the API-led connectivity approach. We get the architecture and follow the basic rules and principles that Mule has.

It's used for regional implementation, where several systems are integrated and contributing to a central on-premises system.

Our primary use for this solution is API driven related management and lightweight message processing.

We use the solution to create integration with different systems. 

My primary uses are asset maintenance and data management.

We use Mule ESB to integrate different products like SAP and Salesforce. We also use it to transform data and communicate it in different versions. 

We use this solution for payment integration. We are customers of Mule ESC and I'm a co-founder and the data engineer head.

I use ESB to do integrations for a company called Pelindo. Pelindo is a company that's a terminal operator. They are involved in logistics, have many partners, and require transaction detection and a payment gateway.

We implemented the Mule solution for our orchestration. We use it to follow up with the customer so the online order gets orchestrated to the target automated system.

We are an IT consulting company and we have built our security on Mule ESB. We work for different customers for whom we develop projects for application integration using MuleSoft.

Our use cases involve connecting backend systems like Salesforce, SAP, and other custom applications. We also expose these APIs to external customers. We have also integrated it with a system of engagement, for example, Qooper.

Mule ESB acts as an intermediary that assists with integration between multiple layers.

• API integration with many backend systems, deployment options, testing. 
• It helps me to manage API as well.

The integration of an ERP system with a payment system in order to improve accounting information and invoice management.