Skip to main content

Use Azure Cache For Redis In AspNetCore Application Using Distributed Cache Technique[.NET6]

In this article, we are going to do a small demo on integrating Azure Redis Cache into the AspNetCore Application using Distributed cache technique.

Redis Cache:

Redis is an open-source in-memory data structure store, used as a database, cache. It supports data structures such as strings, hashes, lists, sets, stored sets with range queries, etc.
Let's understand the flow of Redis cache in a web application:
  • Users request a page from the web application.
  • Web application queries the Redis store, if the data exists, then fetches the data and returns the response directly to the user.
  • If no data is in the Redis store, the application queries the database and fetches the data, next save the same data into the Redis store so that subsequent user request can consume the data from the Redis store directly, finally returns the response to the users.

Create A Azure Redis Cache:

Create and sign-in into the Azure portal(

On the Azure portal home page click on 'Create a resource'.
On the 'Create a resource' page select the 'Databases' and then select 'Azure Cache for Redis'.
(1)On the 'New Redis Cache' page, enter the project details.
  • Subscription- Choose your subscription plan from the dropdown.
  • Resource group - Either create a new resource group or select an existing group from the drop-down.
  • DNS name- Enter the name of your Redis instance subdomain name.
  • Location- Choose your server location from the dropdown.
  • Cache type- Select pricing plans for Redis usage. no free plans on it.
(2)Choose your type of 'Network Connectivity'.
(3)In the 'Advanced' tab you can choose the version of the Redis instance.
(4)The 'Tags', name/value pairs is an optional section.
(5)Finally, select 'Review+ Create', on successful validation, select 'create', on success in a few minutes our Redis instance will be ready.

IDistributedCache Interface:

IDistributedCache interface is implemented from the 'Microsoft.Extensions.Caching.Distributed' library. IDistributedCache is not specific to Redis Cache, but it was implemented like generic which supports all kinds of Distributed Cache like Redis, SQL Server Cache, etc. IDistributedCache supports the default dependency injection of .NET Core, so it can be easily injected into the application where ever needed. IDistributedCache Interface holds a set of methods that helps to work with cache, some of the methods like as below.
  • Get, GetAsync - fetches the cached data by the key passed.
  • Set, SetAsync - saves the data to the cache-store.
  • Remove, RemoveAsync - removes the cached data specific to key passed.

Create A .NET6 Web API Project:

Let's create a .Net6 Web API sample application to accomplish our demo. We can use either Visual Studio 2022 or Visual Studio Code(using .NET CLI commands) to create any.Net6 application. For this demo, I'm using the 'Visual Studio Code'(using the .NET CLI command) editor.
CLI command
dotnet new webapi -o Your_Project_Name

Install NuGet Package:

Package Manager:
Install-Package Microsoft.Extensions.Caching.StackExchangeRedis -Version 6.0.1

dotnet add package Microsoft.Extensions.Caching.StackExchangeRedis --version 6.0.1

Configure Azure Redis ConnectionString:

(1)On the Azure portal home page click on 'Resource groups'.
(2) On the 'Resource groups' page, select the resource group that has our Azure cache for Redis.
(3) Now click 'Azure Cache for Redis' instance.
(4) Now under 'Settings' select 'Access Keys', then copy the connection string either primary or secondary connection string.

Now copied Redis connection string needs to add to our Web API project.
"ConnectionStrings": {
Now register the Redis Cache service into the 'Program.cs' file.
builder.Services.AddStackExchangeRedisCache(options => {
    options.Configuration = builder.Configuration.GetConnectionString("AzureRedisConnection");
  • Here registered the 'AddStackExchangeRedisCache' service.
  • The 'Configuration' property is assigned with the Azure Redis connection string value.

Create A Sample API Response Model:

Let's create a sample class that will be our response object model like the 'Car.cs' file in the 'Models' folder.
namespace Dot6.AzureRedis.Learn.Models;

public class Car
    public int Id { get; set; }
    public int Year { get; set; }
    public string Manufacturer { get; set; }
    public string Model { get; set; }

Create A Sample API Controller:

Let's create a sample API controller like 'CarController.cs'.
using System.Text;
using System.Text.Json;
using Dot6.AzureRedis.Learn.Models;
using Microsoft.AspNetCore.Mvc;
using Microsoft.Extensions.Caching.Distributed;

namespace Dot6.AzureRedis.Learn.Controllers;

public class CarController : ControllerBase
    private readonly List<Car> fakeDatabase = new List<Car>
        new Car
            Id = 1,
            Manufacturer = "Honda",
            Model = "Civic",
            Year = 2021
        new Car
            Id = 2,
            Manufacturer = "Kia",
            Year = 2021,
            Model ="Seltos"
    private readonly IDistributedCache _cache;
    public CarController(IDistributedCache cache)
        _cache = cache;
  • (Line: 13-29) The 'fakeDatabase' variable contains mock or test data for our demo, in real-time application data will be fetched from the database.
  • (Line: 31) The 'Microsoft.Extensions.Caching.Distributed.IDistributedCache' interface is injected into the controller.

Use GetAsync And SetAsync:

GetAsync - This asynchronous method fetches the byte array of data from the Redis-store for a specified key.

SetAsync - This asynchronous method saves the byte array of data with a key for it like a dictionary. If we intended to save any object or collection of objects into the Redis-store then we serialize our data to a string, then string to byte array of data.

Let's create a sample API action method that uses our Redis-store.
public async Task<IActionResult> Get()
	var carsFromRedis = await _cache.GetAsync("carstore");
	if ((carsFromRedis?.Count() ?? 0) > 0)
		var carsString = Encoding.UTF8.GetString(carsFromRedis);
		var cars = JsonSerializer.Deserialize<List<Car>>(carsString);
		return Ok(new { LoadedFromRedis = true, Data = cars });

	var fakeDatabaseString = JsonSerializer.Serialize(fakeDatabase);
	var fakeDatabaseByteArray = Encoding.UTF8.GetBytes(fakeDatabaseString);
	await _cache.SetAsync("carstore", fakeDatabaseByteArray);
	return Ok(new { LoadedFromRedis = false, Data = fakeDatabase });
  • (Line: 4) Using 'GetAsync("key")' trying to fetch byte array of data from the store.
  • (Line: 5) Checking whether we got a response from the Redis store.
  • (Line: 7) Converting the byte array of data into the string.
  • (Line: 8) Converting the string to the collection of 'Car' types.
  • (Line: 9) Returning API response, here for our understanding added a flag property like 'LoadedFromRedis' to our response.
  • (Line: 12) If the data does not exist in the Redis store this line of code starts executing. Here serializing the collection of 'car' types to string.
  • (Line: 13) Converting string result to byte array.
  • (Line: 14) Using 'SetAsync' with help of 'key' and 'value'(byte array of data) stored into the Redis store so that the next client request to API endpoint can return a response directly from Redis store.
Now run the application, for the first request in the response we can observe 'LoadedFromRedis' return a false value.

Now for the second request, the 'LoadedFromRedis' property returns true, which confirms data coming from the Redis-store.

Cache Expiration:

The cache should have an expiry date. To define expiration we have two options that are mandatory for a good coding approach.
  • Absolute Expiration
  • Sliding Expiration
Absolute Expiration - Maximum time period to store in the cache After expiration Redis will automatically delete all keys and their values automatically.

Sliding Expiration - Maximum time period to store data without consuming by the application. If an application not using any particular keys for a specific time it is always good to clear them from the cache before its Absolute Expiration. This type of expiration will be called a Sliding Expiration. One important thing to remember sliding expiration is always less than Absolute Expiration time if you set Sliding Expiration more than Absolute Expiration id doesn't make any sense because data will be cleared after the Absolute expiration time.

Let's update our action method logic to use expiration.
public async Task<IActionResult> Get()
	var carsFromRedis = await _cache.GetAsync("carstore");
	if ((carsFromRedis?.Count() ?? 0) > 0)
		var carsString = Encoding.UTF8.GetString(carsFromRedis);
		var cars = JsonSerializer.Deserialize<List<Car>>(carsString);
		return Ok(new { LoadedFromRedis = true, Data = cars });

	var fakeDatabaseString = JsonSerializer.Serialize(fakeDatabase);
	var fakeDatabaseByteArray = Encoding.UTF8.GetBytes(fakeDatabaseString);
	var expiration = new DistributedCacheEntryOptions{
		AbsoluteExpirationRelativeToNow = TimeSpan.FromSeconds(20),
		SlidingExpiration = TimeSpan.FromSeconds(19)
	await _cache.SetAsync("carstore", fakeDatabaseByteArray, expiration);
	return Ok(new { LoadedFromRedis = false, Data = fakeDatabase });
  • (Line: 14-17) Defined 'Absolute Expiraiton' and 'Sliding Expiration' for our Redis-store.
  • (Line: 18) The 'SetAsync' had an overloaded method that can accept the expiration object.

Use RemoveAsync:

It is always good to have an endpoint to clear the data in Redis-store. The 'RemoveAsync' method will remove our cached data with respect to the key passed to it.
public async Task<IActionResult> Remove()
	await _cache.RemoveAsync("carstore");
	return Ok();

Support Me!
Buy Me A Coffee PayPal Me

Video Session:

Wrapping Up:

Hopefully, I think this article delivered some useful information on Use Azure Cache For Redis in the AspNetCore Application Distributed Cache technique. using I love to have your feedback, suggestions, and better techniques in the comment section below.

Follow Me:


Popular posts from this blog

.NET6 Web API CRUD Operation With Entity Framework Core

In this article, we are going to do a small demo on AspNetCore 6 Web API CRUD operations. What Is Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains a programming function that can be requested via HTTP calls to save or fetch the data for their respective clients. Some of the key characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build REST full services. Create A .NET6 Web API Application: Let's create a .Net6 Web API sample application to accomplish our

Angular 14 Reactive Forms Example

In this article, we will explore the Angular(14) reactive forms with an example. Reactive Forms: Angular reactive forms support model-driven techniques to handle the form's input values. The reactive forms state is immutable, any form filed change creates a new state for the form. Reactive forms are built around observable streams, where form inputs and values are provided as streams of input values, which can be accessed synchronously. Some key notations that involve in reactive forms are like: FormControl - each input element in the form is 'FormControl'. The 'FormControl' tracks the value and validation status of form fields. FormGroup - Track the value and validate the state of the group of 'FormControl'. FormBuilder - Angular service which can be used to create the 'FormGroup' or FormControl instance quickly. Form Array - That can hold infinite form control, this helps to create dynamic forms. Create An Angular(14) Application: Let'

Part-1 Angular JWT Authentication Using HTTP Only Cookie[Angular V13]

In this article, we are going to implement a sample angular application authentication using HTTP only cookie that contains a JWT token. HTTP Only JWT Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-Only cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use authentication with HTTP only JWT cookie then we no need to implement custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To implement JWT cookie authentication we need to set up an API. For that, I had created a mock authentication API(Using the NestJS Se

Unit Testing Asp.NetCore Web API Using xUnit[.NET6]

In this article, we are going to write test cases to an Asp.NetCore Web API(.NET6) application using the xUnit. xUnit For .NET: The xUnit for .Net is a free, open-source, community-focused unit testing tool for .NET applications. By default .Net also provides a xUnit project template to implement test cases. Unit test cases build upon the 'AAA' formula that means 'Arrange', 'Act' and 'Assert' Arrange - Declaring variables, objects, instantiating mocks, etc. Act - Calling or invoking the method that needs to be tested. Assert - The assert ensures that code behaves as expected means yielding expected output. Create An API And Unit Test Projects: Let's create a .Net6 Web API and xUnit sample applications to accomplish our demo. We can use either Visual Studio 2022 or Visual Studio Code(using .NET CLI commands) to create any.Net6 application. For this demo, I'm using the 'Visual Studio Code'(using the .NET CLI command) editor. Create a fo

A Small Guide On NestJS Queues

NestJS Application Queues helps to deal with application scaling and performance challenges. When To Use Queues?: API request that mostly involves in time taking operations like CPU bound operation, doing them synchronously which will result in thread blocking. So to avoid these issues, it is an appropriate way to make the CPU-bound operation separate background job.  In nestjs one of the best solutions for these kinds of tasks is to implement the Queues. For queueing mechanism in the nestjs application most recommended library is '@nestjs/bull'(Bull is nodejs queue library). The 'Bull' depends on Redis cache for data storage like a job. So in this queueing technique, we will create services like 'Producer' and 'Consumer'. The 'Producer' is used to push our jobs into the Redis stores. The consumer will read those jobs(eg: CPU Bound Operations) and process them. So by using this queues technique user requests processed very fastly because actually

Angular 14 State Management CRUD Example With NgRx(14)

In this article, we are going to implement the Angular(14) state management CRUD example with NgRx(14) NgRx Store For State Management: In an angular application to share consistent data between multiple components, we use NgRx state management. Using NgRx state helps to avoid unwanted API calls, easy to maintain consistent data, etc. The main building blocks for the NgRx store are: Actions - NgRx actions represents event to trigger the reducers to save the data into the stores. Reducer - Reducer's pure function, which is used to create a new state on data change. Store - The store is the model or entity that holds the data. Selector - Selector to fetch the slices of data from the store to angular components. Effects - Effects deals with external network calls like API. The effect gets executed based the action performed Ngrx State Management flow: The angular component needs data for binding.  So angular component calls an action that is responsible for invoking the API call.  Aft

Usage Of CancellationToken In Asp.Net Core Applications

When To Use CancellationToken?: In a web application request abortion or orphan, requests are quite common. On users disconnected by network interruption or navigating between multiple pages before proper response or closing of the browser, tabs make the request aborted or orphan. An orphan request can't deliver a response to the client, but it will execute all steps(like database calls, HTTP calls, etc) at the server. Complete execution of an orphan request at the server might not be a problem generally if at all requests need to work on time taking a job at the server in those cases might be nice to terminate the execution immediately. So CancellationToken can be used to terminate a request execution at the server immediately once the request is aborted or orphan. Here we are going to see some sample code snippets about implementing a CancellationToken for Entity FrameworkCore, Dapper ORM, and HttpClient calls in Asp.NetCore MVC application. Note: The sample codes I will show in

Blazor WebAssembly Custom Authentication From Scratch

In this article, we are going to explore and implement custom authentication from the scratch. In this sample, we will use JWT authentication for user authentication. Main Building Blocks Of Blazor WebAssembly Authentication: The core concepts of blazor webassembly authentication are: AuthenticationStateProvider Service AuthorizeView Component Task<AuthenticationState> Cascading Property CascadingAuthenticationState Component AuthorizeRouteView Component AuthenticationStateProvider Service - this provider holds the authentication information about the login user. The 'GetAuthenticationStateAsync()' method in the Authentication state provider returns user AuthenticationState. The 'NotifyAuthenticationStateChaged()' to notify the latest user information within the components which using this AuthenticationStateProvider. AuthorizeView Component - displays different content depending on the user authorization state. This component uses the AuthenticationStateProvider

How Response Caching Works In Asp.Net Core

What Is Response Caching?: Response Caching means storing of response output and using stored response until it's under it's the expiration time. Response Caching approach cuts down some requests to the server and also reduces some workload on the server. Response Caching Headers: Response Caching carried out by the few Http based headers information between client and server. Main Response Caching Headers are like below Cache-Control Pragma Vary Cache-Control Header: Cache-Control header is the main header type for the response caching. Cache-Control will be decorated with the following directives. public - this directive indicates any cache may store the response. private - this directive allows to store response with respect to a single user and can't be stored with shared cache stores. max-age - this directive represents a time to hold a response in the cache. no-cache - this directive represents no storing of response and always fetch the fr

Angular 14 Crud Example

In this article, we will implement CRUD operation in the Angular 14 application. Angular: Angular is a framework that can be used to build a single-page application. Angular applications are built with components that make our code simple and clean. Angular components compose of 3 files like TypeScript File(*.ts), Html File(*.html), CSS File(*.cs) Components typescript file and HTML file support 2-way binding which means data flow is bi-directional Component typescript file listens for all HTML events from the HTML file. Create Angular(14) Application: Let's create an Angular(14) application to begin our sample. Make sure to install the Angular CLI tool into our local machine because it provides easy CLI commands to play with the angular application. Command To Install Angular CLI npm install -g @angular/cli Run the below command to create the angular application. Command To Create Angular Application ng new name_of_your_app Note: While creating the app, you will see a noti