前端应用
micro-frontend-caching
更新于 2026-10-13
Micro Frontends · 缓存规则
Caching rules for Micro Frontends: explicit invalidation owners, versioned keys and stampede protection.
- 技术栈
- Micro Frontends
- 主题
- 缓存
- 条目
- 9 条
- 版本
- v0.2.0
✓ 应当这么做
- ✓ Name the invalidation owner for every cache entry
- ✓ Version cache keys so a deploy can invalidate without a purge
- ✓ Protect against stampedes with single-flight or jittered expiry
✕ 常见反模式
- ✕ Caching data whose correctness depends on user-specific authorisation without scoping the key
- ✕ Infinite TTLs with no owner
- ✕ Treating the cache as durable storage
◎ 交付前验证
- ◎ Production build completes and the bundle budget is respected
- ◎ No critical CSS purged by the optimizer (spot-check key pages)
- ◎ Lighthouse/axe pass on the main route after the change
同分类条目
40 篇前端应用
React 工程规则
React 19 delivery rules: pure render, server actions and stable list identity
前端应用
Next.js 工程规则
Next.js 15 App Router rules: async cookies/headers and server/client boundary discipline
前端应用
Nuxt 工程规则
Nuxt 3 rules: data fetching composables and SSR-safe state
前端应用
Vue 工程规则
Vue 3 Composition API rules: pure computed state and typed props
前端应用
Svelte 工程规则
Svelte 5 rules: runes-based reactivity and effect discipline
前端应用
Solid 工程规则
Solid.js rules: fine-grained reactivity without dependency-array leakage