Here's the draft agenda for tomorrow: https://docs.google.com/presentation/d/1EbZEvW7zlXS7DhNnL2GkWN8H5P3uz5DvBSXMcE4sE7U/edit?usp=sharing If you would like to add a topic, please let me know. We'll

Any opportunity to fold this line of thinking into the architecture patterns we are working as part of the architecture committee. One of the "patterns" groups represents a pivot to scaling function

All, Just in terms of process: please note that a WG needs TOC support to form. I'm waving my hand and saying "I am supportive". I don't know what the rest of the TOC think yet ;) Also we need to

Cathy, I agree that Workflows and Jobs are a natural extension to “Functions”, just likehttps://aws.amazon.com/step-functions/ I can share my views in the WG how it can be architected into

Thanks Swarna! Good points

Sharing this with TOC and Marketing, per A's suggestion. Regards, Swarna. ---------- Forwarded message ---------- From: Swarna K Podila <skpodila@...> Date: Mon, Apr 3, 2017 at 11:56 PM Subject: Fwd:

Sharing this with TOC and Marketing lists, per A's suggestion. -Swarna. ---------- Forwarded message ---------- From: Swarna K Podila <skpodila@...> Date: Mon, Apr 3, 2017 at 10:15 PM Subject: KubeCon

Hi all I'm in favour of a wg. But it needs to not overreach. An initial focus could be to parse the space (as Yaron and others did) and identify areas where the cncf can help. If we did this i

+1 on a CNCF WG. Will be happy to contribute to it. I see that different people have different perspectives on serverless or FaaS. I think it will he helpful to define the semantics of serverless

Hi all 1) new call time not set yet, still WED 8am PT I have not quite got to the bottom of new call times for the TOC yet, but I am hoping to find a spot on Tuesday. For APRIL we shall stick to

Doug, I agree, e.g. couple of 1st level topics to start with: Define what constitutes the “Event” and “Context” structures in the function call + expected response, so Functions can be made

One day we may be able to leverage common infrastructure, but for now I think a more realistic goal might be to focus on the end-user and see if we can push for an interoperability statement around

“serverless” Perf is a big issue, start-up time is just part of it, most implementation have huge per F call overhead Can see AWS Lambda avg call (after warm-up) is 500ms:

Glad to see lots of agreement on this thread and +1 to the idea of a WG/SIG. One comment though, Ryan said: > I agree with these, but I'd put performance as non-core because there are plenty of

I think this is one of the areas that the open source community could make the most impact in (relative to cloud platform implementations). Event bus and message bus are prevalent in many, many

+1 on a CNCF WG for serverless. Per a side conversation with Alexis this should be discussed at the TOC so it would be nice to have this added as an agenda item for an upcoming meeting. Mark

I agree with many of the points, had a bunch of 1:1 chats @ KubeCon on the need for more colaboration in that space There will be a bunch of implementations by cloud and OpenSource (I presented

I’m not a fan of the term “serverless” as most people tend to think “no servers” as opposed to “fewer” or “not having to deal with” servers. Of course, FaaS doesn’t quite roll off

Yes, I find this story inspiring from Benchling of moving their genome searching to Lambda and both reducing tail latency and dropping costs from thousands of dollars per month to

I agree. As well as fast startup time and zero cost for idle workloads.