Working with large amounts of saved data will increase memory use dramatically. In-memory cache is fine if we are working with short-lived objects or with systems with not frequent cache peaks. Any app crashes or restarts will also clean up all the cached data.
For long-lived cache entities, or for very highly loaded systems it is recommended to use distributed caching. The app should store cache outside of the working process - another app, process, database, etc.
Going to add a very simple distributed cache based on Redis instances - data will be stored outside on single or cluster type Redis blocks
Working with large amounts of saved data will increase memory use dramatically. In-memory cache is fine if we are working with short-lived objects or with systems with not frequent cache peaks. Any app crashes or restarts will also clean up all the cached data.
For long-lived cache entities, or for very highly loaded systems it is recommended to use distributed caching. The app should store cache outside of the working process - another app, process, database, etc.
Going to add a very simple distributed cache based on Redis instances - data will be stored outside on single or cluster type Redis blocks