Downloaded 15 times
Uploaded byCodemotion
Advanced Concept of Caching - Mathilde Lemee - Codemotion Milan 2014
The document discusses advanced caching concepts, primarily focusing on methods to improve data access in applications, such as cache-as-a-storage-of-record and different caching strategies like write-through and write-behind. It highlights the importance of data consistency, refresh strategies, and the implications of scalability in software architecture. The author shares insights on practical applications of caching in e-commerce and banking scenarios.
More Related Content
Similar to Advanced Concept of Caching - Mathilde Lemee - Codemotion Milan 2014
![[Hanoi-August 13] Tech Talk on Caching Solutions](https://cdn.slidesharecdn.com/ss_thumbnails/nitecocachingsolution-130826204343-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
Advanced Concept of Caching - Mathilde Lemee - Codemotion Milan 2014
- 1. MILAN november 28th/29th2014 Mathilde Lemee Advanced Concept of Caching @MathildeLemee - Aetys
- 4.
- 5.
- 6. TTI TTL #codemotion@MathildeLemee
- 7. Tom wants to improve data access #codemotion @MathildeLemee
- 8. CACHE ASIDE Application Cache PGuett BB PHUITT ! ! GGeett AB HMIITS S! ! DAO Databas e Read B #codemotion @MathildeLemee
- 9. Tom wants thatthe cache always have updated datas. #codemotion @MathildeLemee
- 10. System of Record #codemotion @MathildeLemee
- 11. Cache as as-o-r : Read through Application Persistence layer Ehcache Database Get A HIT ! #codemotion @MathildeLemee
- 12. Cache as as-o-r : Read through Application Persistence layer Get A MISS! Ehcache Database #codemotion @MathildeLemee
- 13. Cache as as-o-r : Write through Application Persistence layer Ehcache Database PUT ! #codemotion @MathildeLemee
- 14. Tom works ona e-commerce website and want to have the faster data access. #codemotion @MathildeLemee
- 15. Cache as as-o-r : Write Behind Database Application Ehcache Persistence layer A Write-behind thread A Put B PUT ! B C C D D Get A B C D Write A B C D #codemotion @MathildeLemee
- 17. Access Time #codemotion@MathildeLemee
- 18. Write Through Responsetimes #codemotion @MathildeLemee
- 19. Write Behind ResponseTimes #codemotion @MathildeLemee
- 20.
- 21. Write Through –Database load #codemotion @MathildeLemee
- 22. Write Behind –Database load #codemotion @MathildeLemee
- 23. Tom doesn't controlthe datas #codemotion @MathildeLemee
- 24. REFRESH AHEAD #codemotion@MathildeLemee
- 25. 0 TTR TTL #codemotion @MathildeLemee
- 26. Paul work ina bank where at a fixed time datas are updated #codemotion @MathildeLemee
- 27. SCHEDULED REFRESH AHEAD #codemotion @MathildeLemee
- 28.
- 29. CACHE ASIDE VS READ/WRITE THROUGH #codemotion @MathildeLemee
- 30. Refresh Ahead/Scheduled Refresh VS The world #codemotion @MathildeLemee
- 31. Refresh Ahead VS Scheduled Refresh Ahead #codemotion @MathildeLemee
- 32. Write Behind VS Write Through #codemotion @MathildeLemee
- 33. KNOW YOUR DATAS #codemotion @MathildeLemee
- 34.
- 35.
- 36.
- 37. La scalabilité estla capacité qu’a l’architecture Wikipedia pour évoluer en cas #codemotion @MathildeLemee
- 38.
- 39.
- 40. La scalabilité d’une application est égale à la #codemotion @MathildeLemee
- 41.
- 43.
- 44.
- 45.
- 46.
- 47. ET SI …#codemotion @MathildeLemee
- 49.
- 50.
- 51.
- 52.
- 53.
- 54. ET SI …#codemotion @MathildeLemee
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 63.
- 64.
- 65.
- 66. ET SI …#codemotion @MathildeLemee
- 67. Consistence • Julie/ 32 ans / 2 enfants / Paris • Paul / 27 ans / 4 enfants / Marseille • Thomas / 40 ans / 1 enfant / Paris – Déménagement de Thomas sur Marseille Qui habite sur Paris ? #codemotion @MathildeLemee
- 68.
- 69. ONE ANY EACHQUORUM THRE E QUORUM LOCAL QUORUM TWO #codemotion @MathildeLemee
- 70. CAP • Consistency: • Availability : • Partionning #codemotion @MathildeLemee
- 71. • Consistency +Available = RDBMS • Consistency + Partionning = BigTable / Hbase / MongoDB / Redis • Available + Partionning = Riak/Cassandra/CouchDB #codemotion @MathildeLemee
- 72.
- 73.
- 74.
- 75.
- 76. IMDG vs RelationalDatabase
- 77.
- 78.