无状态还是有状态FaaS？我两个都要！
Stateless or stateful FaaS? I'll take both!
摘要：
无服务器计算已经成为一种非常流行的云技术，其伴随的FaaS（Function-as-a-Service）编程模型支持从客户端调用无状态函数。无服务器的发展正在发生，将其转移到网络边缘，并将其范围扩大到有状态函数。在本文中，我们认为，无状态与有状态不是应用程序本身的二分法，而是大多数（如果不是全部）应用程序的随时间变化的属性，在生产环境中收集的真实痕迹的分析证实。基于这一观察，我们提出了一个数学公式的资源分配问题，共同包括两个操作模式，称为λ与μ，这可以有效地解决在运行时的边缘编排。我们评估所提出的解决方案，通过模拟实验在现实的网络和工作负载条件下，这导致了一个系统的实际实现的方式，应用程序可以自由地适应其当前的操作模式，并优化其性能，在最低的运营成本从网络的角度来看。
英文摘要：
Serverless computing has emerged as a very popular cloud technology, together with its companion Function-as-a-Service (FaaS) programming model enabling invocations of stateless functions from clients. An evolution of serverless is now taking place, shifting it towards the edge of the network and broadening its scope to stateful functions, as well. In this paper we argue that stateless vs. stateful is not a dichotomy of the application per se, but rather a time-varying property of most (if not all) applications, as confirmed by the analysis of real traces collected in a production environment. Based on this observation, we propose a mathematical formulation of a resource allocation problem that jointly encompasses both operation modes, dubbed lambda vs. mu, which can be solved efficiently at run-time by an edge orchestrator. We evaluate the proposed solution via simulation experiments in realistic network and workload conditions, which leads the way to the practical realization of a system where applications can freely adapt their current operation mode and optimize their performance at a minimum cost of operation from the network's perspective.
机构、总结、中文摘要均由AI分析而来，可能存在错误，请以论文正文为准。
