How to manage cache in ASP.NET WebApi2?

Published on Author Code Father
How to manage cache in ASP.NET WebApi2?

You should store client specific information in Session instead of Cache. Cache should be for the whole application (shared)

However, it’s not recommended as web api is built with RESTful in mind and RESTful services should be stateless (APIs do not cache state). Stateless applications have many benefits:

  • Reduce Memory Usage
  • Better scalability: Your application scales better. Image what happens if you store information of millions of client at the same time.
  • Better in load balancing scenario: every server can handle every client without losing state.
  • Session expiration problem.

In case you want to store client state, you could do it anyway. Please try the suggestions in the following post: ASP.NET Web API session or something?

In general, caching state locally on the web server is bad (both Session and local MemoryCache). The cache could lose for many reasons:

  • App pool recycle.
  • Load balancing environment
  • Multiple worker processes in IIS

Regarding your requirements:

Each client get session information and access list from server for synchronization purpose on every second. According to access changed, client functionality will changed(Enable/Disable).

I’m not sure if you want to update the other clients with new access list immediately when a client sends synchronization call. If that’s the case, SignalR would be a better choice.

Otherwise, you could just store the updated access list somewhere (shared cache or even in database) and update the other clients whenever they reconnect with another request.