A distributed cache is a shared place to keep expensive database-query results. Application servers can reuse cached answers instead of repeating the work; Redis is one example. section 10.6
A faster homepage
Run a heavy homepage query once and keep its result in Redis for five minutes. Later visitors can get the cached answer, reducing repeated database work and potentially easing the load on the servers. section 10.6
A local L1 cache can avoid the network trip to a shared L2 cache, but it adds a synchronization problem: if a server misses an update, users may see stale data, such as an old profile picture on one page and a new one on another. section 10.6
Figure 10.8 Multi-Level Caching: The Local Cache (L1) is like a personal sticky note for blistering speed, while the Distributed Cache (L2) is a shared whiteboard for the entire system.

Compare the local L1 cache with the shared distributed L2 cache. section 10.6




