0

I have a .net core web app with multiple instances and want to have a caching strategy that allows me to clear 'sections' or 'regions' of the cache, and ensure the changes are applied across all instances.

The current implementation works great with in memory caching (fast, no dependencies), but will not work with multiple instances of each web app.

For any services required, I'd like to stick with Azure for ease of billing for the client.

So far I've looked into:

  1. Using the existing in memory cache + service bus to subscribe to cache events to ensure all services are synced

  2. Using Redis as a distributed cache

Interested to hear if others have a better solution to this, or any feedback/experience with the above options.

Dan
  • 33
  • 2
  • 1
    The second option seems to be a good choice. The cache is separated from the instance, so that the scaling up or down of the instance does not have much impact. – Jason Feb 10 '22 at 06:36

0 Answers0