构建以服务工作者为首的网页应用所获得的经验教训：批处理、乐观并发控制和测试
在研究离线优先的网页应用程序后，我整理了一份参考实现，展示了一些我希望早些时候就能看到的架构模式：
<p>有趣的挑战包括：
- 当用户在会话中途离线时，如何处理数据变更？
- 有什么好的策略可以在不丢失用户更改的情况下批量调用 API？
- 如何可靠地测试服务工作者的行为？
- 当多个用户离线编辑相同数据时，如何解决冲突？
<p>这不是一个框架，更像是一个带有可运行代码的文档案例研究。README 文件解释了架构决策和权衡。
<p>https://github.com/localnerve/jam-build
<p>期待大家对我采取的方法或其他人使用的替代模式的评论。
查看原文
After working on offline-first web applications, I put together a reference implementation that demonstrates some architectural patterns I wish I'd had examples of earlier:<p>The interesting challenges:
- How do you handle data mutations when users go offline mid-session?
- What's a good strategy for batching API calls without losing user changes?
- How do you test service worker behavior reliably?
- How do you resolve conflicts when multiple users edit the same data offline?<p>This isn't a framework - it's more like a documented case study with working code. The README explains the architecture decisions and tradeoffs.<p>https://github.com/localnerve/jam-build<p>Looking forward to comments on the approaches I took or alternative patterns others have used.