2. 2
▪ Around 14 years of Experience into ERP and Integrations.
▪ Working as Development and Integration Architect @Casper Inc.
▪ 3X MuleSoft Certified, 1X AWS Certified
▪ Managed multiple End to End Implementations/Integration projects.
▪ Mentoring Mule Developers and People trying to switch to MuleSoft.
Introduction
Neeraj Kumar- Host NYC
3. Safe Harbor Statement
•Both the speaker and host are organizing this meet up in individual capacity only.
We are not representing our companies here.
•This presentation is strictly for learning purpose only. Organizer/Presenter do not
hold any responsibility that same solution will work for your business
requirements also.
•This presentation is not meant for any promotional activities.
4. 4
▪ 10 years of IT experience
▪ Integration Practice Lead at Datacom New Zealand
▪ Multi-MuleSoft Certified Developer and Architect
▪ Speaker during MuleSoft CONNECT 2020 and MuleSoft
Partner Kickoff 2021
▪ Contributor to MuleSoft Blogs
▪ MuleSoft Ambassadress (2021)
▪ Wellington, New Zealand Meetup Co-Leader
▪ Currently mentoring talented Mule Developers
Introduction
Mary Joy Sabal
5. Agenda
● Caching Concept
● What should I cache?
● HTTP Caching Policy in API Manager
● Secure Cache Key by using Header Injection Policy
● Demo
● Caching Process
● Caching Strategies
● Demo
● Benefits of an API Caching Policy
● Key Takeaways
7. What should I cache?
● Any resource accessible via HTTP GET or CONNECT
● Static data
● Responses that are immutable
● Responses that change infrequently or at predictable intervals
● Responses used by many clients (frequently-requested data)
18. Caching Strategies
● Default: in-memory object store
● Default Key: SHA256KeyGenerator and a SHA256 digest to generate a unique key for the
message payload
22. Benefits of an API Caching
● Easy configuration
● Unified implementation – there is one policy which populates, invalidates, and implements
lookups.
● Support for all deployment targets: CloudHub, Hybrid environments, and Runtime Fabric
● Ability to cache APIs dynamically using DataWeave expressions
● Easily skip and purge cache dynamically using header control
● Extensions that are fully supported by Custom policies
23. Key Takeaways
● Monetary costs, such as paying for bandwidth or volume of data sent; or
● Opportunity costs, like processing time that could be used for other purposes
24. Feel free to reach out!
24
https://www.linkedin.com/in/mary-joy-sabal/
joy.sabal2@datacom.co.nz
https://blogs.mulesoft.com/author/maryjoysabal
28. Question 1
1) What are the two API policies we have covered on this session?
a) HTTP Caching Policy and Cache Scope
b) HTTP Caching Policy and Detokenization
c) HTTP Caching Policy and Header Removal
d) HTTP Caching Policy and Header Injection
28
29. Question 2
2) What is the default caching strategy?
a) Persistent
b) In-memory Object Store
29
30. Question 3
3) What are the two HTTP headers from the response so client will be aware for how long
the resource will be valid?
30
31. Upcoming Meetups
● Topic: Power of SalesForce Lightning WC and Mule along with Platform Events.
Date: Saturday, July 24th 2021, 11AM EDT
Speaker: Amit Singh, India
https://meetups.mulesoft.com/events/details/mulesoft-new-york-city-presents-power-of-salesforce-lightning-web-components-
and-mule-along-with-platform-events/