知识卡片
无服务器转移执行责任
无服务器函数按消息、请求或资源事件启动,完成后终止或冻结。平台承担监听、调度和资源管理,使代码聚焦业务操作;有的平台会复用执行实例,因此仍需理解跨请求资源状态。冷启动会增加延迟,短小快速动作和需求波动大的异步负载通常更适合。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 提供应用运行基础设施 · 查看原书依据
A key advantage of serverless code is that it can be simpler than code that runs continually on a server or in a container. Non-serverless code tends to need logic to manage whatever events it needs to respond to, such as opening ports to listen on, looping over multiple requests, and managing the use of
参考来源
- 位置:《Infrastructure As Code》第13章《提供应用运行基础设施》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch13.html)
- 结论依据:原文说明无服务器函数按消息、请求或资源事件启动,完成后终止或冻结;本卡据此解释其用途及适用边界。
- 原始内容:A key advantage of serverless code is that it can be simpler than code that runs continually on a server or in a container. Non-serverless code tends to need logic to manage whatever events it needs to respond to, such as opening ports to listen on, looping over multiple requests, and managing the use of