This tutorial explores Message Sender and Browser settings and their uses, plus Async implementation, for developers designing in Anypoint MQ on CloudHub.
My last article on MQ got a good response. As already decided, we will conclude the MQ details in this article. So, let us start on available features of Anypoint MQ.
I have provided many settings and configurations in the previous article. Here we will start with other settings and their usage. Now you can click on the queue name which you have already created and configured.
The Anypoint platform provides the opportunity to send the message to the queue directly. It results in proper checks about the working of the queue. For example, I can check what messages I have put in the queue and what is the format related to it.
The below image can provide you the type of message Anypoint MQ supports natively. JSON, Text (string) , and XML are currently supported. These types are very common in day to day operations on the ESB layer.
Now you can see the message what we have just inserted in the below image.
You can see the message ID, timing of push, and content of the message. The one problem Anypoint MQ is currently having that there is no messageId-based pulling from the queue. This feature is very common with most on-prem queues and on cloud available with SQS by Amazon. I hope soon we will have more teeth to Anypoint MQ over cloud.
There is an individual delete and purge (group delete) option if you want clear the queue. Please note all such operations are possible from the Mule flow if you are using Amazon SQS. Here, Anypoint platform is the place where we have to come to perform such operations (i.e. group deletion) .
Now I should move towards how to make an Async design using MQ.
The design decisions are merit-based. There can never be only one approach. However, I can suggest the one I have implemented. Say for example I have to do a transaction between three systems (A—>B—>C) . In this scenario, A—>Mule—>B and then B’s response has to be moved into C for consumption. To make all the processes async, we have to place queues in between.
I have tried to provide some detailed insight into Anypoint MQ’s workings. I hope this will be helpful in working/designing with Anypoint MQ.
