Caching considerations
Donut hole caching from Phill Haack!
The Repository Pattern
This thread on StackOverflow
The Output cache is a clear winner for fast and effective caching, but like Mr. Haack has mentioned, only use it when it’s the right tool for the job. The Output Cache can give a great bit of flexibility with regards to where the output is stored.
The current locations for the Output Cache are the following
from http://support.microsoft.com/kb/323290
- Any - This stores the output cache in the client's browser, on the proxy server (or any other server) that participates in the request, or on the server where the request is processed. By default, Any is selected.
- Client - This stores output cache in the client's browser.
- Downstream - This stores the output cache in any cache-capable devices (other than the origin server) that participate in the request.
- Server - This stores the output cache on the Web server.
- None - This turns off the output cache.
6dffd84f-aec0-4146-b574-b47ad3941735|1|4.0