►
From YouTube: CNCF Serverless WG Meeting - 2018-04-16
Description
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
A
B
C
B
E
E
A
E
E
So
we've
had
lists
of
those,
and
then
we
started
brainstorming
a
bit
about
what
are
the
type
of
ideas
we
could
come
up
with
for
showing
you
interrupt,
meaning
that
I
could
weep
produce
then
move
thought
the
vinspired
middleware
and
then
consume
them
in
some
interesting
ways.
So
we
had
some
of
those
ideas.
E
We
did
talk
about
the
demo
assumptions,
which
is
that
if
we
did
have
a
demo,
we
would
not
worry
about
some.
Some
of
the
you
know.
We
put
it
together
with
duct
tape
and
baling
wire
that
we
wouldn't
worry
about
some
of
the
issues
around
security
or
authentication,
etc
that
if
we
could
just
get
some
feeds
going,
that
would
be
sufficient
for
now,
but
the
longer
term
we'd
have
to
put
more
around
it
and
then
for
next
steps.
E
E
D
These
projects
that
are
supporting
this
and
first
off
this
is
this-
is
pretty
good
I.
Think
if
we're
gonna
go
announce
this
kind
of
event,
format
that
could
make
data
more
liquid,
more
portable,
and
we
have
all
these
people
already
supporting
it
in
this
early
stage.
I
think
that's
going
to
really
amplify.
That
message
are
all
these
going
to
what
level
of
support
or
all
these
projects
gonna
have
by
by
cloud
native
Khan,
which
is
like
20
days.
E
Think
people
were
going
back
to
research
what
they
may
be
able
to
do.
I
think
some
of
this
is
hinging
on
whether
Google
and
Microsoft
could
get
some
of
their
eventing.
They
get
cloud
event.
Events
generated
because
that's
somewhat
of
a
compelling
demo,
but
it's
a
you
know
it's
up
to
each
individual
to
be
able
to
state
what
they
can
or
can't
do
so.
F
So
I
can
tell
you
for
Microsoft
I,
send
email
on
Friday,
where
I
showed
you
what
the
mapping
might
be
from
particular
events.
The
minimal
thing
we'll
be
able
to
do
is
write
effectively
a
function
that
will
take
our
native
events
as
we
have
them
today
and
kind
of
map
them
into
the
cloud
events,
format
yep,
that's
the
minimal
thing
we
can
do
so
that
we
and
that
function
basically
gets
it.
It
becomes
a
quasi
subscriber,
so
you
create
a
functioning.
F
The
kind
of
the
function
has
a
target
that
it
pushes
to
and
then
it
it
gets
an
event
from
event
grid
and
basically
goes
translation
and
push
that
through.
So
we
can
build
that
in
relatively
short
time,
and
so
that's
yeah,
I
think
from
that's
from
a
coding
perspective.
That's
probably
going
to
be.
Our
contribution
is
to
say
give
me
your
eye
and
I'm
gonna
deliver
in
that
event,
for
you
and
the
event
is
gonna.
F
F
It
seems
to
be
nonsensical
in
this
context
here
to
make
anybody
understand
the
banker
at
events,
so
I
would
rather
go
and
do
the
translation,
where
you
know
I'm
getting
a
URI
I'm
to
push
to
or
an
HTTP
URL
in
a
case
or
HTTPS,
and
then
we're
gonna
deliver
the
the
clock,
events,
events
and
if
everything
goes,
goes
very
swimmingly,
then
we
might
be
able
to
do
without
that
function
and
push
straight
from
event
grid.
F
D
F
F
So
the
idea
there
would
be
that
you
can
go
and
upload
a
so.
If
we
go
with
some
nailing
idea,
which
was
one
of
the
things
that
we
haven't
list,
you
would
go
and
write
and
up
upload
a
file
to
an
storage
account
and
we
have
some
way
of
PowerShell
and/or
bash
tule
for
that
and
then,
as
the
file
gets
upload,
oh,
it
has
been
uploaded
you
that
event
gets
trigger
okay.
So
you
don't
keep
about
blob
storage.
It's
not
right!
Yeah!
It's
it's!
In
that
case,
it's
blob
storage,
yes,
okay!
F
So
that
seems
that
seems
the
easiest.
That's
one
of
our
canonical
samples
that
we
use
and
that's
something
that
will
you
that
will
work
for
our
thing
and
it
will
also
similarily
likely
work
for
other
platforms
that
you
have
this
created
event.
That's
why
we
picked
it,
and
so
that
would
be
the
proposal
from
our
side.
Like
put
you,
someone
pushes
uploads
a
file
into
blob,
store
and
then
and
then
even
gets
raised.
D
F
D
Okay,
yeah
well
I'm,
trying
to
figure
out
how
to
do
this.
I
would
love
to
show
some
stuff
off
during
the
talk.
Looks
like
we're.
Gonna
have
a
lot
of
stuff
to
show
off.
If
there's
a
way,
we
could
simplify
it
into
into
one
demo
that
I
could
do
during
the
talk
Devon.
That
would
be
a
lot
easier,
but
as
of
right
now,
it's
gonna
be
hard
to
incorporate
everyone.
I
think.
E
The
only
thought
that
I
have
around
being
able
to
encompass
multiple
would
be
like
a
traceroute
type
of
capability
where
you
would
consume
in
the
event
that
something
had
text
that
made
it
to
your
event
handler
and
then
pass
it
on
to
the
next
one.
But
it
becomes
complex.
Getting
everything
set
up
and
getting
ordering
right.
D
D
Incorporating
all
these
people
is
gonna
be
difficult.
It
also
depends
on
the
use
case
like
what
are
we?
What
use
case
are
we
targeting
in
this
and
what
is
what
is
this
kind
of
multi
cloud
scenario
that
we
need
to
actually
where
this
would,
where
the,
where
cloud
events
would
be
helpful,
I
think
that's
gonna
speak
a
lot
to
to
users,
so
honing
in
on
that
involving
a
few
people
in
that
I
think
would
be
I
think
would
be
pretty
good.
D
We
support
cloudy
bets
today
we
have
to
the
event
gateway
working
as
a
hosted
service.
The
role
it
would
play
in
this
world
is,
it
would
just
can't
it
would
be
a
broker
or
a
router
across
these
clouds.
Potentially,
so
you
wouldn't
have
to
map
directly
from
Clemens
Azure
functions
to
whatever's
receiving
it.
On
the
Google
side,
you
would
kind
of
send
it
off
from
the
Azure
function
to
the
event
gateway.
The
event
gateway
could
send
it
off
to
about
three
different
providers,
potentially
that.
D
A
B
B
D
D
F
Yeah
I
think
I
think
it
it's
it's
the
it's
a
very
tangible
one
right,
so
you
can
make
a
you
can
obviously
construct
all
kinds
of
workflow
cases
around
files
very
easily
and
the
I
think
what
we
discussed
last
week
when
you
learn
that
there
is
either
so
taking
a
JPEG
image
and
and
walk
watermarking.
It
mm-hmm,
which
you
can
take
as
a
story
of
let
me
see,
I,
might
have
yeah.
E
E
F
Yeah,
if
I
were,
if
I
were
doing
so
I'm
trying
to
find
a
slide
that
I've
made
for
something
here
dog,
so
so
there's
a
we
have
a.
We
have
a
scenario
that
for
something
else.
Where
you
upload
you
snap
a
photo
with
a
camera
you
uploaded
into
a
blog
from
the
blog.
Then
you
trigger
you
trigger
a
function.
The
function
then
runs
it
through
a
computer
vision
API
to
go
to
classify
that
picture
mm-hmm,
and
then
it
goes
with
that
classification.
It
goes
into
a
so.
F
F
I
mean
there's
all
kinds
of
you:
can
you
can
come
up
with
a
flow
where
you
start
with
a
picture
of
a
journalist
who's
in
the
field
with
their
camera,
and
you
know
where
they
are
and
then
they
kind
of
start
from
there
with
a
flow
that
ends
up
on
someone's
news
desk
and
they
can
go
and
pick
pic
pictures
for
the
event
that
they
put
on
the
website
and
you
can
go
and
make
that
all
very
event-driven.
So
it
goes
from
from
just
as
simple
it,
something
like
scenarios
to
something.
That's
more.
F
You
know
simulates
reality
a
little
bit
more
for
something,
that's
very
dynamic.
It
needs
to
be
pretty
fast
right
and
then,
of
course,
once
the
journalist
picks
that,
then
you
really
need
to
have
already
the
thumbnails
sitting
somewhere
in
your
in
your
blog
store.
So
you
can,
as
you
use
them
as
use
the
image
for
an
article,
all
the
thumbnails
already
there
and
can
be,
can
be
referenced.
It's
just
that's
just
a
tall
order
to
build
within
two
weeks
without
us,
having
identified
a
resource
who
will
do
it?
Yeah.
E
F
Yeah
I'm
not
I'm,
just
I'm,
just
giving
an
example
of
a
thing
that
we
that
might
be
doable
yeah.
It's
just
a
question
of
how
much
how
much
power
do
we
have
to
go
and
do
this
given
the
time
and
giving
really
given
resources,
because
that's
always
the
problem.
D
If
you
can
be
able
to
port
it
over
to
another
cloud
provider
easily
to
gain
access
to
a
managed
service,
that's
they're
really
good
at
that.
Maybe
the
other
providers
don't
have,
then
that
could
be
very
compelling
for
users.
So
perhaps
there's
a
story
here
where
some
image
is
uploaded
somewhere
and
the
event
is
kind
of
spread
around
to
do
all
types
of
different
processing
on
various
functions
located
on
different
providers.
D
But
those
functions
on
different
providers
should
try
and
use
some
cool
managed
service
that
may
may
be
they
that
they
offer
that
is
kind
of
unique
and
great,
and
to
do
some
type
of
processing
to
kind
of
tell
a
chapter
of
this
story.
Whatever
is
happening
with
this
image
I
like
Clements
story,
a
lot
about
this
journalist
taking
a
photo
in
the
field,
we
could
do
something
like
that.
D
The
photo
can
go
out
to
functions
everywhere
and
a
managed
service
can
go,
do
some
cool
processing
on
it,
but
that
would
be
a
cool
way
to
show
off.
You
know
not
just
kind
of
interrupt
but
say
hey.
This
is
a
means
of
gaining
access
to
a
lot
of
the
cool
services
that
the
cloud
providers
are
offering
that
not
not
a
single
cloud
providers
offering.
D
Okay,
I
think
the
way
to
do
this
is
perhaps
we
have
to
figure
out
what
that
story
is,
and
each
function
has
a
service
provider
who
wants
to
be
involved
needs
to
make
sure
they
support
HTTP,
of
course,
and
then
they
have
to
figure
out
what
they're
gonna
do
as
part
of
that
story
in
their
function.
Right.
D
F
F
D
Another
great
example
could
just
be
a
an
inventory
item,
a
photo
for
an
inventory
item.
No
there's
a
few
people
in
at
Nordstrom
who
are
kind
of
working
on
this
POC
to
build
an
event,
room
and
Nordstrom,
and
they
they
have
a
pretty
neat
workflow
around.
Just
a
new
inventory
item
gets
added,
someone
receives
an
event
to
go,
take
a
photo.
D
F
D
Perhaps
what
we
can
do
is
during
the
next
call
on
Thursday.
We
could
say:
here's
what
we
think
the
premise
of
the
demo
is
it's
going
to
be.
The
journalist
takes
the
photo
in
the
field
or
a
new
inventory
item
is
added
to
an
e-commerce
store
and
we
say
hey
this.
This
event
is
going
to
be
sent
out
to
any
cloud
provider,
but
it's
up
to
you
to
figure
out
what
you
want
to
do
in
your
function.
That's
gonna
add
value
to
that
to
that
story
overall,.
D
Yeah
I,
when
I
saw
that
demo
I
was
I,
really
liked
it,
because
it
it
was
an
event-driven
workflow
that
incorporated
like
a
human
element
right.
This
new
inventory
item
was
added
and
then
an
event
was
sent
that,
like
the
photo
needed
to
be
taken-
and
we
could
be
on
vacation
for
two
weeks
or
something
and
come
back
and
see
these
events
and
you
know,
take
photos
and
then
the
adventure
of
it
and
while
they're
gone.
D
Of
course,
the
adventure
would
workflow
is
paused,
but
as
soon
as
they
take
that
photo,
it
kicks
off
again
continues
where
it
left
off.
I
thought
that
was
pretty
cool.
I
love
that
demo,
but
doing
anything
with
like
text
messages
or
MMS
might
might
be
a
little
bit
more
technically
complicated.
Just
gonna
call
that
out.
D
I
think
it
was,
it
was
either
a
text
or
an
email,
Erik
Erikson's
who's
joining
the
cloud
events
call
from
Nordstrom.
He
worked
on
that
project,
so
he
could
describe
it
on
Thursday.
If
he's
on
the
call.
C
D
D
So
it
could
be
a
couple
of
things:
the
benefit
about
our
event
gateway,
those
who
just
publish
it
I
mean
the
whole
thing
is
designed
to
handle
cross
cloud
events
in
transport,
but
you
can
publish
an
event
to
that
at
one
place
and
it'll
broker
it
off
to
multiple
functions
via
synchronous
or
asynchronous
workflows
right.
So
we.
D
C
So
is
it
as
simple,
as
you
tell
us
where
that
thing
is
and
then
we
can
I
assume
you
could
probably
either
open
it
up
or
give
us
the
right
credentials
so
that
any
of
us
could
then
basically
push
events
to
the
gateway,
and
then
they
would
get.
Events
would
then
get
pushed
out
to
anybody
that
subscribed
to
it
and
that
way
we
can
test
this
offline.
C
D
Absolutely
it
exposes
endpoints,
which
you
could
send
it
different
events
to,
and
we
can
do
it
without
off
to
not
make
it
super
complicated
for
the
demo,
but
it
all
it
all
depends
on
what
story.
We're
gonna
tell
what
that
with
that
compelling
use
case
is
and
what
I
suggested
I
think
right
when
you
joined
the
call
is
that
naved
comes
from
somewhere,
maybe
it's
related
to
a
photo
and
that
event
is
then
sent
into
the
event
gateway,
which
then
triggers
multiple
functions
on
different
fast
providers,
who
all
do
some
interesting
processing
on
that
photo.
D
C
Okay,
now
it
sounds
good
to
me.
I
was
just
thinking
from
a
stepwise
progression.
The
easiest
thing
for
the
initial
first
step
might
just
be
to
tell
us
where
that
gateway
is
so
we
can
push
events
to
it
and
subscribe
to
it,
and
then
you
can
go
work
on
you
know
you
get
that
basic
flow
of
being
able
to
push
events,
receive
events
and
then
figure
out.
C
D
And
I
could
do
that.
It's
gonna
be
pretty
simple
to
emulate,
though
it's
just
gonna
be
a
basic
HTTP
request.
I
think
the
cloud
event
will
be
in
the
request
body.
So
all
the
all
the
fast
functions
really
have
to
do
is
expose
some
type
of
endpoint
and
then
receive
the
HTTP
request
and
pull
out
the
cloud
event
from
the
event
body.
So
you
have
to
write
some
code
at
the
beginning
of
their
function.
To
do
that,
we
can
start
setting
that
up.
You
know
right
away,
so
they
could
they
could
play
with
it.
D
D
Okay,
so
I
suggested
we
pitch
this
on
the
Thursday
call.
We
say:
here's
what
we
think
we're
doing
you
know,
whoever
wants
to
participate,
can
write
a
fast
function
and
figure
out
what
they
could
do
to
support
this
story.
I
think
it's
gonna
be
a
bit
over
the
top.
Initially
it
won't.
You
know
if
we
have.
You
know
several
fast
providers
involved
in
this
I.
Don't
know
if
it'll
be
a
real,
realistic
use
case.
C
D
Yeah
we
could
do
that
and
of
course
we
have
a
lot
of
integrations
already
with
AWS
stuff
and
I
got
a
chat
with
them.
I
got
to
check
in
and
see
how
they'd
like
to
be
involved,
but
yeah.
We
just
have
to
figure
out
what
that
story
is
kind
of
where
it
comes
from,
but
in
the
meantime,
we'll
we'll
set
up
a
partition
version
of
the
event
gateway
which
we
could
use
for
the
demo
cool.
F
F
Yeah
I
think
us
publishing
the
the
blob
events
for
now
is
is
probably
okay,
but
let
me
let
me
think
about
whether
we
want
to
go
and
also
consume
something
because
I
mean
and
the
minimum
at
a
minimum
will
have
a
some
function.
That
does
something
with
it.
I
mean
we
can
we
already
have
a
demo
that
does
the
thumbnail
piece
and
I
can
easily
rewrite
that
one
to
go
and
also
deal
with
that
cloud
of
it.
F
D
Great
and
I
don't
want
to
add
to
the
scope,
because
this
is
already
a
lot
but
yeah
this.
This
trance
translator
a
transformer
that
you're
building
I
do
believe
that
there
is
a
big
there's
potential
for
a
great
open
source
project
here,
which
is
just
a
simple
library
that
knows
how
to
transform
common
events
from
providers
into
cloud
events,
yeah,
I'm,
I'm,.
F
D
E
D
D
Okay,
well
I
believe
we
need
to
get
a
couple
story,
ideas
and
we
have
to,
but
we
could
keep
adding
them
to
the
agenda
doc,
and
this
is
what
we
should
present
on
Thursday
and
then
maybe
we
vote
on
something
not
sure
how
we
want
to
do
that.
But
we
should
try
and
pick
something
ASAP
on
Thursday
and
then
from
there.
We
should
ask
who
wants
to
participate?
Who
wants
to
write
a
fast
functions
and
say
the
criteria?
D
Probably
gonna
need
till
end
of
the
week,
but
not
sure
mine
might
be
able
to
send
it
out
sooner,
but
again
it's
just
going
to
receive
it's
just
going
to
receive
an
HTTP.
It's
just
gonna
send
out
an
HTTP
POST
request.
So
as
long
as
your
function
can
can
receive
HTTP
requests-
and
you
know
you
should
be
able
to
mock
it
pretty
easily
mm-hmm.
D
D
A
D
That
right
now
do
several
seconds
or
something
cuz.
This
is
ambitious,
but
I,
but
I
like
it
and
I
will
say
that
just
looking
over
the
list
of
people
and
projects
or
companies
and
projects
that
are
supporting
this
right
now,
it's
a
pretty
compelling
list
and
I
do
think
we're
gonna
make
an
impact.
It's
just
you
know,
even
if
we
don't
get
the
demo
for
whatever
reason,
just
by
showing
off
how
many
people
are
looking
to
support.
This
I
think
it's
going
to
it's
going
to
create
a
picture
of
possibility
and
layouts.