Hi Qian,
There’s a deployment time process, where the user uploads their functions to
the serverless platform. At that time, the system packages/containerizes the
function code and stores the container (or lightweight VM) in a registry. From
there, a serverless endpoint is setup and linked to
Thanks John for the detailed info which really helps me understand the
requirements better.
For each request, the serverless runtime launches one copy of the
> containerized function.
Can you please elaborate a bit more on this? What did you mean for the
`containerized function`? Is it just a
Hi Qian,
After looking into the open source options for widely-used serverless
frameworks, I noted these five:
* Oracle-backed Fn: https://fnproject.io/
* Kubeless: https://kubeless.io/
* Fission: https://fission.io/
* OpenFaaS: https://www.openfaas.com/
* Apache OpenWhisk:
Hi John,
Thanks for your suggestion!
> That is, how do you run serverless workloads that require access to
persistent data and how do you schedule your serverless functions so that
they execute with good data locality to ensure decent performance.
If you are talking about the workload
Hello All,
In going through the mail archive before subscribing to this list, it seems
there have been a number of discussions around what Mesos should do as a
project. One use case that might be worth considering is ‘serverless’
workloads. This would be something where the Kubernetes
