AppFabric vs Unity vs. Memcached, or possibly any other caching mechanisms for multiple servers

I am currently studying various caching mechanisms, regardless of whether they are free or for a small fee (minimally desirable).

Situation. Currently, we need to have load-balanced servers that host our web application, with the third server being the SQL server. This site is an eShop, and it becomes fairly regular on large volumes.

I was asked to explore MS's Memcached and Unity caching mechanisms, but AppFabric also met in this process.

Can someone tell me what is the best caching mechanism for the above scenario?

We are currently using the .net caching mechanism with ASP.Net, and we also know about the corporate library caching system.

Thanks.

+6
caching asp.net-mvc
source share
1 answer

If you just want to cache your database, you can simply use the built-in .NET cache provider and use the SQL Cache dependency. That way, if any data in your database crowds out your cache on both servers.

The disadvantage of the distributed caching mechanism is that there is still a lot of network traffic that occurs to request cached objects on cache servers.

+3
source share

All Articles