Re: RFC: Fission (http://fission.io/)
I think we should consider a working group or SIG for “serverless”
some of those solutions look naïve at best
there is a lot of overlap between k8s functionality and “serverless” on one hand, on the other it requires integration with multiple external frameworks e.g. APIs, PubSub, Logging, K/V state storage, event triggers/streamers, identity management. Each of those may have few overlapping cloud, open-source and commercial options with pros and cons. I don’t see how one company can deliver on it all (unless its AWS/GCP/Azure), it calls for collaboration.
the right path is to start with requirements and a framework/architecture which define the flows, layers, APIs and roles of components, what needs to be done at the orchestration layer (k8s/mesos/..), how external triggers or resources are plugged into it, how does it scale, development tools ...
I’m willing to take active part in such a workforce
From: cncf-toc-bounces@... [mailto:cncf-toc-bounces@...] On Behalf Of Alexis Richardson via cncf-toc
Sent: Friday, January 6, 2017 8:57 PM
To: Jonathan Boulle <jonathan.boulle@...>; Soam Vasani <soamvasani@...>
Cc: Soam Vasani <soam@...>; CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] RFC: Fission (http://fission.io/)
+1 especially compared to the cornucopia of new "serverless" libs that seem to have appeared of late....
On Fri, 6 Jan 2017, 18:53 Jonathan Boulle via cncf-toc, <cncf-toc@...> wrote: