Common Exception Handling

1. All contents © MuleSoft Inc.
19th March 2022
11:00 AM IST
Delhi MuleSoft Meetup
Common Error Handler for handling
exceptions across the layers.
https://meetups.mulesoft.com/

2. All contents © MuleSoft Inc. 2
● Anurag Sharma : https://www.linkedin.com/in/anurag-sharma-59745b20/
● Ankit Lawaniya: https://www.linkedin.com/in/ankit-lawaniya/
● Pryank Gupta: https://www.linkedin.com/in/gupta-pryank-24a1293b/
● Abhay Aggarwal: https://www.linkedin.com/in/abhay-agarwal-851121112/
Organizers :
Welcome Everyone in Today’s Meetup

3. All contents © MuleSoft Inc.
• 9 Years of IT experience
• Integration Technical Lead
• MuleSoft Certified and ORACLE Certified Developer
and Architect
• MuleSoft Mentor, Delhi and Ahmedabad MuleSoft
meetup leader
• Active member on MuleSoft Helper Forum
• Mentoring and learning with talented Developers
• Owner of MuleSoft Station Group, you can join us on
Telegram and Instagram
Anurag Sharma (Technical Lead)
https://www.linkedin.com/in/anurag-sharma-59745b20/
Today’s Meetup Host:

4. All contents © MuleSoft Inc.
Speaker
4
Working as an Integration developer with 7+
years of experience in different domains and
different clients. Working as MuleSoft
developer and architect. Happy to help and
contribute to MuleSoft community and
eventually learning new things in process.
Feel free to connect with me on LinkedIn.
Love to travel and watch movies in free time.
https://www.linkedin.com/in/piyush3192/

5. All contents © MuleSoft Inc.
Common Error Handler for
handling exceptions across
the layers.

6. All contents © MuleSoft Inc. 6
• API-led connectivity is a methodical way to connect data to applications
through reusable and purposeful APIs. These APIs are developed to play a
specific role – unlocking data from systems, composing data into processes, or
delivering an experience.
API Led Connectivity Approach

7. All contents © MuleSoft Inc.
Why is API-led connectivity necessary and how it
is necessary to reduce IT’s workload?
7
P2P vs API Led Approach

8. All contents © MuleSoft Inc. 8
• System APIs – these usually access the core systems of record and provide a
means of insulating the user from the complexity or any changes to the
underlying systems. Once built, many users, can access data without any need
to learn the underlying systems and can reuse these APIs in multiple projects.
• Process APIs – These APIs interact with and shape data within a single
system or across systems (breaking down data silos) and are created here
without a dependence on the source systems from which that data originates,
as well as the target channels through which that data is delivered.
• Experience APIs – Experience APIs are the means by which data can be
reconfigured so that it is most easily consumed by its intended audience, all
from a common data source, rather than setting up separate point-to-point
integrations for each channel. An Experience API is usually created with API-
first design principles where the API is designed for the specific user
experience in mind.
APIs used in API Led Connectivity Approach

9. All contents © MuleSoft Inc. 9
Errors can be cumbersome

10. All contents © MuleSoft Inc. 10
Why do we need a good Error Handling?
Error handling refers to the response and recovery procedures from error conditions present
in a software application. In other words, it is the process comprised of anticipation,
detection and resolution of application errors, programming errors or communication errors.
Error handling helps in maintaining the normal flow of program execution. In fact, many
applications face numerous design challenges when considering error-handling techniques.
There are four main categories of errors:
•Logical errors
•Generated errors
•Compile-time errors
•Runtime errors
As errors could be fatal, error handling is one of the crucial areas for application designers
and developers, regardless of the application developed or programming languages or tools
used. In worst-case scenarios, the error handling mechanisms force the application to log
the user off and shut down the system.

11. All contents © MuleSoft Inc. 11
• Testing isn’t enough alone.
• Categorize your exceptions: Code related or data related(business).
• Easy maintenance and less lookup in code when error occurs.
• Traceability – CorrelationId , Flow Name, Json Logger – trace points.
• Prediction of exception based on transport used(HTTP,JMS,SF).
• Proper Error Message – HTTP Status Code, Error Description, Error Details,
verbose messages.
• Security: Certain errors and logger while handling exception can leave your
underlying system vulnerable.
• Easy to explain to layman manager when error occurs and reduce manual efforts
of looking & explaining the errors(self explanatory)
• Design, learn, adapt and adopt.
Why and what Important points to consider while designing Error Handling

12. All contents © MuleSoft Inc. 12
Use Case: We have an organization which get employee details.
Employee details are stored in database and there some enrichment
done at process level and outcome at experience layer.
Challenge: Some exceptions occurs at system layer doesn’t propagate
to process and experience layer.
Solution: Design a basic exception handling framework which will be
used as dependency into our projects and address the issues and
challenges we discussed.
Today’s use case

13. All contents © MuleSoft Inc. 13
Demo:

14. All contents © MuleSoft Inc.
Q & A

15. All contents © MuleSoft Inc.
Answer the question and win a voucher for MuleSoft training
Quiz Time

16. All contents © MuleSoft Inc.
Winners?

17. All contents © MuleSoft Inc. 17
● Share:
○ Next Meetup 26th March 11:00 A.M.
○ See Virtual | MuleSoft Delhi – Anypoint Monitoring- Gaining Insight into API’s
MuleSoft Meetups Delhi
○ RSVP asap and learn something new about API Monitoring
● Feedback:
○ Tweet using the hashtag #MuleSoftMeetups
○ Fill out the survey feedback and suggest topics for upcoming events
○ Become a Feature Atendee of Delhi Mulesoft Meetup Group -
https://meetups.mulesoft.com/delhi/
○ Contact Organizers for any new topic suggestion
○ Contact MuleSoft at meetups@mulesoft.com for ways to improve the program
○ Invite your network to join: https://meetups.mulesoft.com/
What’s next?

18. All contents © MuleSoft Inc. 18
● Anurag Sharma : https://www.linkedin.com/in/anurag-sharma-59745b20/
Host of today’s Meetup :
You can connect to me if you want to be Next Speaker
Ask anything to Join MuleSoft Community
Can Request to become a Featured Attendee of Delhi MuleSoft Meetup

19. All contents © MuleSoft Inc.
Introduce yourself or share any problems and innovative ideas
Networking time

20. All contents © MuleSoft Inc.
Thank you
don’t forget to provide the
Feedback of this Meetup