Anypoint MQ in Mulesoft

Covers in high level about pre-requisites, features, best practices, and limitations

Transcript

1. AnypointMQ in MuleSoft Author : Arun V S
2. Anypoint MQ  Anypoint MQ is a multi-tenant, highly available cloud messaging service that enables customers to perform advanced asynchronous messaging scenarios between their applications.  It is fully integrated with Anypoint Platform, offering role based access control, client application management, and connectors.
3. Pre-requisites  VPC Gateway will be needed(to run behind firewall) if queue need to send messages to on-premises applications.  Anypoint MQ Enterprise License is needed. i.e, Anypoint MQ Subscription is required
4. Features  Queues and Message Exchanges: Send messages to queues, fetch messages from queues, create a message exchange to perform pub/sub scenarios.  Management console: Monitor queue statistics and see how many messages are in flight via the management console.  Anypoint MQ connector: Send and receive messages from any Mule application, whether it is deployed in CloudHub or deployed on-premises.  Client management: Create client application tokens such as client_id and client_secret separately for each application.
5. Best Practice  Follow this best practice always to guarantee persistent delivery of messages.  SaaS or Onprem Application may not be available anytime. But Data is critical to every organization. So MQs are used to overcome the problem SaaS/Onprem App - 1 SaaS/Onprem App - 2 Middleware with Mule ESB (Hosted in onprem/Cloudhub) Transform and process message Sender Queue Reciever Queue
6. Limitations  Anypoint MQ supports payload of size upto 10 MB only.  It can store messages for 1 week in the queue. After that, it will be available in Dead letter queue(if pre-configured)  Anypoint MQ cannot be deployed on-premises without VPC Setup