网络缓存策略？ [英] Strategies for Caching on the Web?

问题描述

在决定何时以及如何缓存时，您会考虑哪些问题，流程和问题。

What concerns, processes, and questions do you take into account when deciding when and how to cache. Is it always a no win situation?

这假定您一直坚持使用经过优化的代码库。

This presupposes you are stuck with a code base that has been optimized.

推荐答案

我最近一直在使用DotNetNuke来开发Web应用程序，每次实现时我都会考虑很多问题

I have been working with DotNetNuke most recently for web applications and there are a number of things that I consider each time I implement caching solutions.

• 是否所有用户都需要查看缓存的内容？


• 每位多久一次内容更改？


• 我可以缓存整个页面吗？


• 我需要手动清除缓存吗？


• 我是否可以对整个站点使用单一的缓存机制，还是需要多种解决方案？


• 如果信息以某种方式过时会产生什么影响？

• Do all users need to see cached content?
• How often does each bit of content change?
• Can I cache the entire page?
• Do I need a manual way to purge the cache?
• Can I use a single cache mechanism for the entire site, or do I need multiple solutions?
• What impacts occur if informaiton is somehow out of date?

这篇关于网络缓存策略？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！