When the site scales to more than one instance, the live show details get out of sync due to them currently being cached via IMemoryCache. Need to change this to use IDistributedCache backed by Redis.
If the cost of going to Redis for each call ends up affecting the home page response time too much, consider building a hybrid cache that uses Redis for cache invalidation only (via pub/sub), or perhaps use response caching for the home page set to expire for a few minutes (users can force a refresh from their client so they can always get latest if need be).
When the site scales to more than one instance, the live show details get out of sync due to them currently being cached via
IMemoryCache. Need to change this to useIDistributedCachebacked by Redis.If the cost of going to Redis for each call ends up affecting the home page response time too much, consider building a hybrid cache that uses Redis for cache invalidation only (via pub/sub), or perhaps use response caching for the home page set to expire for a few minutes (users can force a refresh from their client so they can always get latest if need be).