Cache-Aside Caching Pattern

Databases are often too large to load directly into a cache. It is common to use the cache-aside pattern to load data into the cache only as needed. When the system makes changes to the data, the system can also update the cache, which is then distributed to other clients. Additionally, the system can set an expiration on data or use an eviction policy to trigger data updates into the cache.

Further reading at Tutorial: Create a Web App (cache-aside) - Azure Cache for Redis | Microsoft Docs