v1.4.0
Feature: Cache Re-population
This release introduces a mechanism to re-populate the cache in the following scenario (#57):
- A call to
redis.get
fails to retrieve an item (it's not present in Redis). - A call to
postgres.get
succeeds in retrieving the item. - The retrieved item will be saved with
redis.put
, future lookups will hit the cache. 🆕
Prior to this change, the Redis cache was only acting as a cache for components/uris/layouts/etc modified after the cache's inception. As a result, a loss of cache data could result in a permanent performance drop without a recovery from backup or a manual solution for re-hydration.
Adopting a v1.4.x
release may significantly increase the memory requirements for the Redis cache for Amphora users that do not have the majority of their data already cached.
If the memory available in Redis is less than the total size of the Postgres database it's strongly recommended to upgrade directly to > v1.5.x
and enable an eviction policy in Redis.