The solution is used in many projects. I'm an IT consultant. I use the tool when there's a need for asynchronous messaging.

We are an integrator for Anypoint MQ, based on Mule 4.3, with several active customers. The solution is typically delivered by cloud and there are differing kinds of use cases that we see.

If there is an event-driven architecture in place, then we will use Anypoint MQ to connect the different APIs together (such as the Experience APIs, Process API, and the System API) so as to enable a seamless process while minimizing data loss. That's the main use case seen in our work.

We transfer data between systems. We are to save the data to make the communication between systems synchronous. We use Anypoint MQ for making the communication synchronous. The source integration component will place the data into Anypoint MQ, and the target company will take it from there.

We're using Anypoint MQ for messaging, in different types: from SAP to third party systems, global third party systems, etc. There's a hundred of them.

We use the solution for migration and integration.

We mostly use it for reprocessing messages in case of failures within asynchronous flows across millions of applications.

We use it for integrating different applications within our infrastructure.

Since we work in a consulting firm, we develop apps on MuleSoft Anypoint MQ. We mainly use this solution for integrations.

We are using Anypoint MQ for integrating third-party systems with synchronous messaging.

We are an implementation partner of Anypoint and I'm the director and solutions architect in the company.