How to Response Caching in ASP.NET Core NCache

By Sriram Mannava

In this exhaustive guide, we will look into the different ways in which we can cache responses in ASP.NET Core and distributed caching using NCache.

What is Response Caching?

Caching refers to the technique of persisting frequently accessed data in a high-speed memory and querying the memory for all subsequent requests. Response Caching is a technique of caching the response data based on a unique selector – generally request paths. In this technique an application server does not need to process and generate a response for the same request again since the response is served from the cache. This results in reduced processing load on the servers and improved turnaround times for clients.

When NOT to cache Responses

As the name suggests, Response Caching results in returning cached responses to requesting clients. This can create ambiguity and conflicts when we try to cache responses of frequently changing entities. Also, it is recommended to ONLY CACHE GET REQUESTS and NOT any other actions, as caching any other actions can result in conflict between data in cache and in the back-end.