In this post, it is demonstrated how to use in-memory caching and Redis based distributed caching in an ASP.NET Core Web API.

In this article, we are going to learn how to Use Redis cache with ASP.NET Core using the package “Microsoft.Extensions.Caching.Redis” provided by Microsoft. The Cache is used to cache data which is frequently used and which does not change often.

In this article, we are going to learn how to Access Azure Redis cache using StackExchange.Redis.Extensions.Core Extensions. “StackExchange.Redis.Extensions.Core”

The way storage is designed for Azure App Service is very interesting. Unlike with Heroku (or other similar providers), App Service offers a shared, persistent storage for your application. This generally means, that when one instance in a farm makes a write to the file system (D:\home) it will be available for all the other instances in the farm and it is going to persist even if the farm restarts or recycles.

When building several big cloud applications we found a lack of great solutions (that's not to say there aren't solutions out there) for many key pieces to building scalable distributed applications while keeping the development experience simple. Here are a few examples of why we built and use Foundatio:

ASP.NET Core supports several different caches. The simplest cache is based on the IMemoryCache, which represents a cache stored in the memory of the web server.

There are many types of caching - In-Memory, Distributed, Response caching. Check out how to do that in ASP.NET Core