MuleSoft Surat Virtual Meetup#33 - Unleash the power of Anypoint MQ and DLQ

1. Surat MuleSoft Meetup Group
Unleash the power of Anypoint MQ and DLQ
12th February 2022

2. 2
Organizers
Jitendra Bafna
Senior Solution Architect III
EPAM Systems
Nitish Jain
Senior Software Engineer
Accenture

3. 3
Jitendra Bafna
●14 years of Experience in Integrations and APIs.
●Working as a Senior Solution Architect III at EPAM Systems.
●MuleSoft Certified Integration and Platform Architect.
●Certified Cloud Architect.
●TOGAF 9.2 Certified
●Expertise in implementing MuleSoft platform like CloudHub,
Customer Hosted Mule Runtime, Anypoint VPC, VPN and DLB.
●Expertise in implementing APIs using MuleSoft
●Expertise in Digital Transformation
Speaker
Jitendra Bafna
Senior Solution Architect III
EPAM Systems

4. Speaker
Abhishek Bathwal
Associate Solution Architect
Apisero Inc
About:
● Working as Associate Solution Architect at Apisero Inc.
● 6+ year of Total Experience. 4+ years in Mulesoft.
● Certified MuleSoft Developer and Architect.
● Mulesoft Mentor
● Guwahati and Lucknow Meetup Leader

5. 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.
5

6. 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
6

7. 7
Agenda
● Anypoint MQ
○ Queue Types
○ Connector Types
○ Configuration
○ Error Types
● Circuit Breaker
● DLQ

8. ● Is a cloud messaging service that performs asynchronous messaging scenarios between
applications such as queuing and pub/sub.
● Is managed easily using Anypoint Platform.
● Supports large payloads (max 10 MB), encryption, queuing, and publish/subscribe
(pub/sub)paradigms.
● Enables easy connection to non-Mule applications using the REST API.
● Provides dead-letter queue (DLQ) for undeliverable messages.
● Displays usage statistics on the number of messages and API requests.
Note: Anypoint MQ is not included in the trial account. We require a separate Enterprise subscription.
Message content can be text, CSV, or JSON. The maximum size of a message is 10 MB.If the payload
contains any format except text (such as CSV, HTML, JSON, and XML), Anypoint MQ converts it to a string
before sending, which increases the payload size. This conversion might result in the payload exceeding the
maximum payload size of 10 MB and causing a Payload too large error.
Anypoint MQ

9. 9
Queue Types
● 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.
● Queue: The queue is a storage area where messages
are stored for processing.

10. 10
Connector Types
● 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.

11. 11
Configuration
Main elements require:
● URL
● Client API ID
● Client Secret

12. 12
Error Types
● ANYPOINT-MQ:CONNECTIVITY
● ANYPOINT-
MQ:DESTINATION_NOT_FOUND
● ANYPOINT-MQ:ILLEGAL_BODY
● ANYPOINT-MQ:PUBLISHING
● ANYPOINT-MQ:RETRY_EXHAUSTED
● ANYPOINT-MQ:ACKING
● ANYPOINT-MQ:CONSUMING
● ANYPOINT-MQ:TIMEOUT
● ANYPOINT-MQ:NACKING

13. 13
Circuit Breaker
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.

14. 14
Configure the Circuit Breaker
● onErrorTypes:
The error types that count as a
failure during the flow
execution.By default, all errors
count as a circuit failure.
● errorsThreshold:
The number of onErrorTypes
errors that must occur for the
circuit breaker to open.
● tripTimeout:
How long the circuit remains open
once errorsThreshold is reached.

15. ● 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
DLF 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.
DLQ

16. Demo

17. Q&A

18. Take a stand !
18
●Nominate yourself for the next meetup speaker and suggest a topic as well.

19. Get ready to WIN a Special Gift from MuleSoft Community
Quiz Time

20. 20
● Share:
○ Tweet using the hashtag #MuleSoftMeetups
○ Invite your network to join: https://meetups.mulesoft.com/surat/
● Feedback:
○ Fill out the survey feedback and suggest topics for upcoming events
○ Contact MuleSoft at meetups@mulesoft.com for ways to improve the program
What’s next?

21. Thank you