3. Safe Harbour Statement
● Both the speaker and the host are organizing this meet-up in individual capacity only. We are
not representing our companies here.
● This presentation is strictly for learning purposes only. Organizer/Presenter do not hold any
responsibility that same solution will work for your business requirements.
● This presentation is not meant for any promotional activities.
3
4. A recording of this meetup will be uploaded to events page within 24 hours.
Questions can be submitted/asked at any time in the Chat/Questions & Answers Tab.
Make it more Interactive!!!
Give us feedback! Rate this meetup session by filling feedback form at the end of the day.
We Love Feedbacks!!! Its Bread & Butter for Meetup.
Housekeeping
4
5. 5
A SHOW OF HANDS:
New Members With Us.!!
CHEERS…!!!
We have prizes to give away!
3 lucky winners will receive a MuleSoft voucher!!!
6. Introduction
● About the Organizers
6
Shubham Chaurasia
Billennium India
Professional Integration Developer
A SHOW OF HANDS:
Who is new to this Meetup?
7. Certified MuleSoft Developer
6+ years of Total Experience, 5+ years in MuleSoft
Working as Sr. Engineering Management Specialist at
HashedIn By Deloitte
● About the Speaker
Speaker
7
8. 8
● Introductions
What is Anypoint MQ?
What are the different types of Queues & Operations Anypoint MQ supports?
How can we leverage Anypoint Platform to publish messages directly?
Brief discussion on MQ connectors and configurations
● Demo
● Trivia
● Wrap-Up
Agenda
9. Multi-Tenant
Cloud messaging service
Supports large payloads (max 10 MB)
Is managed easily using Anypoint Platform
Provides dead-letter queue (DLQ) for undeliverable messages
Performs asynchronous messaging scenarios between applications
Anypoint MQ supports up to 120,000 in-flight messages per standard (non-FIFO) queue
Anypoint MQ
9
10. REST API
Large payloads
Message groups
Disaster recovery
Encrypted queues
Usage information
Client management
Anypoint MQ connector
Delayed delivery for messages
Queues and Message Exchanges
Environments and role-based access control
Anypoint MQ Features
10
11. REST API
Large payloads
Message groups
Disaster recovery
Encrypted queues
Usage information
Client management
Anypoint MQ connector
Delayed delivery for messages
Queues and Message Exchanges
Environments and role-based access control
Anypoint MQ Features
11
12. REST API
Large payloads
Message groups
Disaster recovery
Encrypted queues
Usage information
Client management
Anypoint MQ connector
Delayed delivery for messages
Queues and Message Exchanges
Environments and role-based access control
Anypoint MQ Features
12
13. REST API
Large payloads
Message groups
Disaster recovery
Encrypted queues
Usage information
Client management
Anypoint MQ connector
Delayed delivery for messages
Queues and Message Exchanges
Environments and role-based access control
Anypoint MQ Features
13
14. Type of Queues
Queue: The queue is a storage area where messages are
stored for processing.
Exchange: The exchange is used for broadcasting a
messages, like one message to multiple consumers. If any
message is send to the exchange, it will be forwarded to all
the the queues binded with it.
FIFO (first in, first out): FIFO is a normal queue where
messages are stored.The FIFO queue is used when
message need to be consumed in order.
14
15. Type of Queues
Queue: The queue is a storage area where messages are
stored for processing.
Exchange: The exchange is used for broadcasting a
messages, like one message to multiple consumers. If any
message is send to the exchange, it will be forwarded to all
the the queues binded with it. we cannot bind FIFO queue
to exchange.
FIFO (first in, first out): FIFO is a normal queue where
messages are stored.The FIFO queue is used when
message need to be consumed in order.
15
n=450
16. The dead-letter queue or (undelivered-message queue) is the queue to which messages are
sent if they cannot be routed to their correct destination.
Few things to remember before creating a DLQ.
The DLQ and parent queue both need to be:
Same type of queue (standard or FIFO)
Created in the same geographical region
Created in the same environment and owned by the same Anypoint Platform account
Dead Letter Queue (DLQ)
16
18. Types of Connectors
Subscriber to subscribe to the queue and listen for the receiving
message. (Event source)
Publish to publish the message to the Queue.
Consumer to consume a message from the queue.
Ack to send an acknowledgement to the queue about the
successful consumption of the message and delete the message
from in-flight status.
Nack to send negative acknowledgement to the queue stating the
consumed message is not processed successfully; changes the
status of the message from in-flight to in-queue to be consumed
again by an available consumer.
18
19. Message Acknowledgment
Automatic: By default, the Subscriber source uses the AUTO acknowledgment mode.
With this mode, the messages that the Subscriber source retrieves are acknowledged
automatically after message flow processing succeeds.
Immediate: When you use the IMMEDIATE acknowledgment mode, the consumed
message is acknowledged right before being dispatched to the Mule flow.
Manual: When you use the MANUAL acknowledgment mode, the application logic
decides when to perform the acknowledgment of the message, using
the ACK or NACK sources. To perform the manual acknowledgment, you need the value
of ack token provided as part of the resulting message attributes.
19
21. Circuit Breaker
21
The Subscriber source provides circuit breaking capability, which enables you to
control how the connector handles errors that occur while processing a consumed
message.
For example, when connecting to an external service, you can use the circuit breaker to
handle any downtime of that service. The circuit breaker allows the system to stop making
requests and allows the external service to recover under a reduced load.
The circuit breaker has three states:
Closed: Normal retrieval and processing of message based on the subscriber strategy.
Half Open: Retrieve a single message and attempt to process it.
Open: Scheduled message fetch are skipped and no more messages are processed.
23. Anypoint MQ REST APIs
Anypoint MQ APIs enable you to use REST to send and receive messages, administer
queues and message exchanges, and analyse results.
Anypoint MQ provides these APIs:
Anypoint MQ Admin API: This API allows users to manage their destinations.
Anypoint MQ Broker API: This API allows clients to send & receive messages from
queues & exchanges.
Anypoint MQ Stats API: This API allows users to view statistics for destinations.
23
24. Anypoint MQ REST API References
Admin API Doc:
https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-
23abe036327a.anypoint-platform/anypoint-mq-admin/minor/1.0/console/method/%23503/
Broker API Doc:
https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-
23abe036327a.anypoint-platform/anypoint-mq-broker/minor/1.0/console/method/%23482/
Stats API Doc:
https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-
23abe036327a.anypoint-platform/anypoint-mq-stats/minor/1.0/console/summary/
24
25. Limitations of Anypoint MQ
Anypoint MQ cannot be deployed on-premises.
Note: We have REST APIs to overcome this limitation.
Max size of payload is limited to 10 MB, cannot process payloads larger than 10 MB.
25
28. Take a stand !
28
● Nominate yourself for the next meetup speaker and suggest a topic as well.
29. 29
● Share:
○ Tweet using the hashtag #MuleSoftMeetups
○ Join Mysore Group: https://meetups.mulesoft.com/mysore/
● Feedback:
○ Fill out the survey feedback and suggest topics for upcoming events
○ Contact MuleSoft at meetups@mulesoft.com for ways to improve the program
○ Reach out to Mysore Meetup Leaders (Shubham / Giridhar) to suggest
topics for next Meetup
What’s next?
30. Get ready to WIN a MuleSoft Voucher from MuleSoft
Quiz Time
