When you want to cache more than view fragments and save time reprocessing expensive operations in your services, chances are there is a way to speed up your application by leveraging cache. When you need more than one application server, a distributed cache is required to support your application so that all app servers can take advantage of the speed boost.
In this episode, Monster James dives into a sample scenario of using an Azure Redis cache instance as the backing store for lookups in a service that is used in an ASP.NET Core MVC application.
Here's some other entries on caching that you might be interested in:
Follow @aspnetmonsters