我目前在研究各种不同的缓存机制在那里无论是免费或以一定的成本（最少preferably）的过程。

I am currently in the process of investigating the various different caching mechanisms out there whether they be free or at some cost (minimal preferably).

情况。目前，我们有负载均衡承载我们的Web应用程序与第三个服务器是一个SQL Server服务器。这个网站是一个网上商店，并在得到大量的打相当有规律。

The situation. Currently we have to load-balanced servers that host our web application with a third server being an SQL server. This site is a eShop, and it gets hit quite regularly at large volumes.

我被要求研究Memcached和统一从MS的缓存机制，但在这个过程中所遇到的AppFabric为好。

I have been asked to research the caching mechanisms of Memcached and Unity from MS, but in the process have come across AppFabric as well.

任何一个可以告诉我什么对于上述方案是最好的缓存机制？

Can any one please tell me what for the above scenario is the best caching mechanism?

我们正在使用与ASP.Net的.NET缓存机制，我们也意识到企业库缓存系统。

We are currently using the .net caching mechanism with ASP.Net and we are also aware of the Enterprise Library Caching system.

感谢。

推荐答案

如果你只是想缓存数据库，你可以使用内置的.NET缓存提供者，并使用SQL缓存依赖。这样，如果在你的数据库的任何数据，这将驱逐在两台服务器上的缓存。

If you're just wanting to cache your database, you can just use the built in .NET cache provider, and use the SQL Cache dependency. This way, if any data in your database, it will evict your cache on both servers.

与分布式高速缓存机制的缺点在于，仍然有大量的网络流量发生查询为整个缓存服务器缓存对象

The drawback with a distributed caching mechanism is that there's still a lot of network traffic that occurs to query for the cached objects across the cache servers.