2. Lack of etiquette and manners is a huge turn off.
KnolX Etiquettes
Punctuality
Respect Knolx session timings, you
are requested not to join sessions
after a 5 minutes threshold post
the session start time.
Feedback
Make sure to submit a constructive
feedback for all sessions as it is
very helpful for the presenter.
Silent Mode
Keep your mobile devices in silent
mode, feel free to move out of
session in case you need to attend
an urgent call.
Avoid Disturbance
Avoid unwanted chit chat during
the session.
3. Our Agenda
01 Introduction to cache
02 Caching Architecture
03 Advantages
04 Caching in Play
Framework
05 Demo
4. Introduction to Cache
About Osttra
01
● Cache is a high-speed data storage which stores a subset of data
● Caching allows efficient reuse of previously retrieved or computed
data
1. What is Caching?
About Osttra
01
● Cache has originated since Atlas and the IBM System/360 Model
CPUs in the 1960s
● CPU cache was limited to L1 cache (data and instruction)
● Today, cache is leveraged across layers of technology including
Operating Systems, Networking layers, databases and Application
2. History
6. Advantages of Caching in Application
Improve Application
Performance
Reduce Database
Cost
Reduce the Load on
the Backend
7. Caching in Play Framework
Play provides Cache APIs by default
Provides APIs for Synchronous and Asynchronous Caching
These APIs can be used to store cache data in-memory or can be exported to
external DB like redis-cache
Steps to implement cache in play application:
1. Add cacheApi to library dependency
2. Select suitable implementation (Synchronous or Asynchronous)
3. Setup external database like Redis-Cache to store cache data (not required for
in-memory caching)
4. Inject suitable cacheApi in the class you want to integrate cache to
5. Cache is ready - set and get data with sub-second latency.