We'll discuss different caching strategies, with special emphasis on when and how to use them. Because #cachingmatters.

1. How to cache like a
boss
ŽELJKO PLESAC

3. NOT ALL DATA IS EQUAL.

4. NOT ALL CACHING
MECHANISMS ARE EQUAL.

5. EACH CACHING MECHANISM
IS SUITABLE FOR ONLY ONE
PART OF YOUR APP DATA.

6. CACHING IS SLOW.

7. Response caching with OkHttp
Session object
LruCache
DiskLruCache
Preferences
Database
CACHING MECHANISMS

8. Cache network responses on OkHttp client.
Custom cache size and cache time validity.
No support for data caching, which is created in your app.
OKHTTP RESPONSE CACHING

9. private static final Interceptor cacheControlInterceptor = new Interceptor() {
@Override
public Response intercept(Chain chain) throws IOException {
Request request = chain.request();
Response response = chain.proceed(request);
if (shouldCacheResponse(request)) {
// Re-write response CC header to force use of cache
return response.newBuilder()
.header("Cache-Control", "public, max-age=3600") // 1 hour
.build();
} else {
return response;
}
}
};

10. Simple POJO object which is used for data storage.
Singleton, provided by AppComponent.
Can have shorter lifecycle than app lifecycle.
Used for storing sensitive user data.
SESSION OBJECT

11. If you need to store it, the data should be encrypted.
SESSION OBJECT

12. Memory cache which holds strong references to a limited
number of values.
It has a limited space requirement.
Deleted on app restart.
LRU CACHE

13. Each time a valued is accessed, it is moved to the head of the
queue.
When a value is put into the cache, the value at the end of the
list may be evicted.
LRU CACHE - HOW IT WORKS

14. Similar to LruCache, but the data is stored in a directory on a
filesystem.
Use Jake Wharton’s implementation.
DISK LRU CACHE

15. For storing primitive data in key-value pairs.
Can be private or shared.
Stored on filesystem.
PREFERENCES

16. Native support for relational databases (SQLite).
Support for NoSQL databases by 3rd party libraries (Realm,
Firebase, CouchBaseLite)
DATABASES

17. Full database support
• transactions
• database schemas
• CRUD actions
• migrations
• can be copied, deleted, exported
DATABASES

21. Thank you!
Visit www.infinum.co or find us on social networks:
infinum.co infinumco infinumco infinum
@ZELJKOPLESAC
ZELJKO.PLESAC@INFINUM.CO