无原创，纯转发http://drafts.miantiao.mehttp://drafts.miantiao.me/posts/152http://drafts.miantiao.me/posts/152Mon, 06 Jul 2026 14:39:53 GMT让 Cloudflare Workers 拥有专属缓存：更低的延迟与零 CPU 开销<br /><br />Cloudflare 宣布推出 <b>Workers Cache</b>。以往，Worker 总是运行在缓存的前面；而现在，Cloudflare 的多级缓存（Tiered Cache）可以直接放置在你的 Worker 前面。<br /><br />当请求命中缓存时，你的 Worker 代码根本不会执行。这不仅能让页面加载体验如静态网页般飞快，还能将这部分请求的 CPU 计费直接降为零。<br /><br /><b>核心特性</b><br /><br />• <b>极简配置</b>：只需在 Wrangler 配置文件中开启一行配置，即可通过标准的 HTTP 响应头（如 <code>Cache-Control</code> 和 <code>Vary</code>）直接控制缓存。<br />• <b>丝滑的异步更新</b>：原生支持 <code>stale-while-revalidate</code>。当缓存过期时，系统会先将旧页面立即返回给用户，并在后台异步运行 Worker 更新缓存，让用户实现“零等待”。<br />• <b>属于 Worker 自己的缓存</b>：它摆脱了传统域名（Zone）的规则限制，缓存直接跟随 Worker 移动。无论是在自定义域名、<code>workers.dev</code> 还是预览 URL 中，都能无缝工作。<br />• <b>多租户安全（</b><code>ctx.props</code><b>）</b>：可以将用户 ID 或租户 ID 编入缓存键，从而在边缘安全地为不同登录用户缓存个性化的 API 响应。<br />• <b>应用内微服务级组合</b>：缓存不仅能挡在最外层，还可以塞入同一个 Worker 的不同入口点（Entrypoints）之间，让你的架构设计更加灵活。<br /><br />目前，Astro 框架已经率先提供原生集成支持。所有方案（包括免费版）的 Worker 即日起均可启用该功能。<br /><br /><a href="https://blog.cloudflare.com/workers-cache/" target="_blank" rel="noopener" title="https://blog.cloudflare.com/workers-cache/">https://blog.cloudflare.com/workers-cache/</a><br /><br /><a href="/search/result?q=%23Cloudflare" title="#Cloudflare">#Cloudflare</a> <a href="/search/result?q=%23Serverless" title="#Serverless">#Serverless</a> <a href="/search/result?q=%23Web%E5%BC%80%E5%8F%91" title="#Web开发">#Web开发</a> <a href="/search/result?q=%23%E7%BC%93%E5%AD%98%E6%8A%80%E6%9C%AF" title="#缓存技术">#缓存技术</a> <a href="/search/result?q=%23CloudflareWorkers" title="#CloudflareWorkers">#CloudflareWorkers</a><a class="tgme_widget_message_link_preview" href="https://blog.cloudflare.com/workers-cache/" target="_blank" rel="noopener" title="We are launching Workers Cache, a regionally tiered cache that sits directly in front of your Worker entrypoints. Infinitely composable, configured via standard HTTP headers"> <div class="link_preview_site_name accent_color">The Cloudflare Blog</div> <img class="link_preview_image" alt="Your Worker can now have its own cache in front of it" src="https://drafts.miantiao.me/static/https://cdn4.telesco.pe/file/T_aG8mFHbuKWZa0RehnTNucx0b-U_5vcqTVSnLkyS-dAIfFbMVYneP-yoCOocurv6h5-6F5GtTK8hyThhRXoWgAh-ujJE3Vg8gHYza6UNWJ-bn6bncD0q6nscN565QCyuUOsNw7heicf6YDMk9pZsaTjBmtF4JE6AJ1afJEB3oo7UedQlQp-DKw3LKut1jSAz-awEYsjj0gA39G1c6RHQY9_jmEm0QTLHc2ZVGTzwzwIs7oBnXBbg3LSs_LfzkY4e15u9ur-GQiyrrXRHP0WOf97PH1Y3_bYx6076Rq4AitH1WRo3u0snbPNczMNR2kJYHJNTQdVirMtr5aAd1DAow.jpg" width="1200" height="630" loading="eager" /> <div class="link_preview_title">Your Worker can now have its own cache in front of it</div> <div class="link_preview_description">We are launching Workers Cache, a regionally tiered cache that sits directly in front of your Worker entrypoints. Infinitely composable, configured via standard HTTP headers</div> </a>