►
From YouTube: CNCF Serverless WG Meeting - 2018-04-09
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.
B
C
A
E
C
A
C
C
C
F
F
So
if
you
are
adding
something
to
a
storage
account
or
blog
and
blog,
that
storage
account
was
raising
invent
about
that
blob,
pre
created
and
then
you
can
go
and
react
to
it
so
and
we're
combining
that
in
our
world
with
Azure
functions,
so
that's
our
equivalent
Atlantis
and
also
with
agile
logic
apps,
which
is
a
there's
a
AWS
state
for
that
as
well.
It's
a
workflow
kind
of
a
workflow
serverless
workflow
engine
is
that
the
same
as
step
function,
so
they
don't
know
exactly
yeah.
That's
that's
lame.
F
F
You
can
you
can
process
events
later
and
we
also
integrate
them
with
queues,
so
that's
kind
of
our
internal
flow
that
we
that
we
use,
and
obviously
we
want
to
go
and
open
it
up
to
everybody
else.
So
the
events
that
are
being
emitted
today
from
Asia
are
already
subject
to
a
set
of
constraints
that
we
set.
F
So
it's
not
completely
Wild
West
how
teams
can
express
their
events
that
follow
through
event
grid
and
what
we're
planning
to
do
is
do
a
mapping
of
that
canonical
format
that
we
have
the
cloud
events
and
then
just
make
it
possible
for
us
to
go
and
push
towards
cloud
event.
Consumers
and
also
receive
from
cloud
events.
Users.
F
C
F
We
can
make
a
we
can
make
a
mock
up
of
how
that
will
look
fairly
quickly.
We
can
do
that
within
a
week
or
two
I'm.
Obviously,
if
product
integration
is
something
that
will
take
a
little
bit
more
time,
also
because
of
where
we
are
in
terms
of
stability
but
and
specs,
this
ability
I
mean,
but
we
can
make
something
that
looks
very
much
like
what
it
will
look
like
within
a
very
sure
time,
because
we
have
a
pretty
clear
notion.
Look
at
you,
okay,.
C
It
and
then
a
as
I've
mentioned
in
the
past.
We
have
a
open
source
project
called
dispatch
which
layers
above
open
files
and
wrath.
You
can
take
every
choice
of
facets
underneath
that
we
were
using
cloud
events
as
a
common
substrate
with
it
within
our
event,
bus,
it's
a
in
fact.
Yesterday
I
was
doing
doing
some
updates
to
it
based
off
of
it
goes
originally
implemented,
maybe
a
month
or
so
back
where
we
have
a
different
spec
and
I
updated
it.
Typically,
the
spec.
F
C
G
H
C
G
C
G
I'll
chime
in
I,
we
have
an
analogous
use,
face,
an
analogous
situation
where
sources
and
functions-
and
you
know
can
also
do
analogous
prototyping.
We
obviously
wouldn't
go
into
production
when
the
specs
in
flux,
but
creating
a
bridge.
That's
that
can
go
between
the
things.
I
think
it's
the
demo
that
I've
been
itching
to
create.
I
Guys
this
is
Chad,
so
at
Oracle
we've
got
a
couple
layers
to
this.
One
would
be
our
event
service,
there's
nobody
on
the
call
at
the
moment
representing
the
event
service,
but
they're
integrating
cloud
events
into
there,
so
that
they
can
both
receive
in
the
mid
cloud
events
and
transform
into
a
cloud
events
format
that
service
will
be
receiving
events
from
a
lot
of
different
work,
hole,
applications
and
fast
offerings.
I
need
to
check
with
them
exactly
what
we're
going
to
be
announcing
around
CNCs
Kubik
on
timeframe.
G
G
I
mean
I,
think
Austin
has
been
working
on
the
and
somebody
I
forgotten
his
name
working
on
the
website
very
much
in
anticipation
like
we
want
to
have
a
nicer
presence
on
the
Internet
that
that
I
think
that,
like
we,
we
want
the
what
we've
talked
about
is
that
the
repo
and
the
website
would
be
like
welcoming
to
people,
whereas
right
now,
it's
it's
getting
there,
but
it's
not
quite
there.
C
C
J
G
Just
so
that
I
have
it
for
the
notes
and
I've
looked
at
colliculus,
but
I'm
not
sure
I
could
say
it
as
accurately
as
you.
What
are
the
like
sort
of?
What
are
the
key
attributes
of
cube
list
as
a
fast
in
terms
of
what
it
supports
for
either
emitting
or
consuming
events,
but.
G
K
G
A
C
G
F
Go
ahead,
I
think
for
a
demo.
One
thing
we
should
probably
think
about
is
a
kind
of
if-then
scenario
where
we
that
is
easy
for
us
all
of
us
to
do
and
to
realize
like
there's
something
that
happens
and
have
an
implementation
of
that
and
then
there's
a
routing
routing
of
some
sort
from
peer
to
peer
to
Milla
we're
involved
to
get
that
to
the
receiver
and
then
the
receiver
does
something,
but
and
that
implemented
in
a
very
variety
of
different
infrastructures
and
then
go
and
plug
and
play
and
play
them
busy
to
make
it.
F
F
G
Yeah
when
we
were
first
talking
about
interrupts
demo,
I
was
kind
of
thinking.
Cuz.
We
had
like
kind
of
set
aside
the
whole
like
how
these
things
get
set
up,
that
we
could
just
happily
like
in
one
event,
sort
like
magic
happens
for
how
these
things
are
connected
and
an
event
source,
an
event
source
emits
an
event
right
that
then
triggers
functions
on
different
destinations
right,
so
you
could
have
like
so
like
we
could
construct
it
so
that
we
have
a
like
cloud,
firestore
project
or
Google
Cloud
storage
project
that
emits
an
event
right.
G
That
goes
through
our
little
prototype
and
then
that
with
some
kind
of
hokey
registration
system
that
we
do
behind
the
scenes-
or
maybe
we
put
in
a
file,
so
it's
clear
that
we
can
other
people
can
add
to
it.
You
know
we
just
or
get
up
just
like
it's,
some
kind
of
like
placeholder,
connector
thing
registration
and
then
and
then
we
can
show
how
that
is
consumed
at
different
places.
G
F
F
Let's,
let's
make
a
super
abstract,
create
a
new
object,
the
create
new
object,
if
you
make
a
create
new
object
and
delete,
object,
gesture,
that's
something
that
is
generic
enough,
so
that
everybody
can
go
in
and
interpret
that
in
a
way,
and
it
makes
sense
for
some
emitting
system.
We
look
for
that
for
the
for
the
demo.
G
F
Yeah
I'd
be
happy
if
we
had
end
providers
and
end
consumers
and
we
could
go
and
just
make
them
all
plug
the
plot
even
talk
together.
But
for
that
we
need
to
have
a
all
the
all.
The
emitters
obviously
need
to
be
different
implementations
of
the
same
thing
and
that's
why
I
mean
for
something
that's
very
simple
and
canonical
is.
C
G
I
mean
like
thought
about:
one
of
the
classic
examples
is
like
either
like
somebody
put
something
in
a
datastore
and
it
kicks
off
some
kind
of
a
business
analysis
right
data
analysis
or,
like
you
know,
the
classic
I
want
to
put
an
image
on
some
kind
of
like
we
all
have
like
many
of
the
folks
in
Rome.
Have
cloud
storage
things
right
and
then
you
know,
and
then
that
does
something
with
it.
Thumbnails
thumbnails.
F
G
G
C
C
G
Like
that,
that's
cute,
that's
actually!
That,
then,
can
we
share
it
on
social
media
I
love
that
idea.
So
then
we
have
it.
What's
the
other
one,
so
the
you
could
have
the
like
user
signs
up
for
when
for
app
add
lead
in
CRM
I
like
so
that,
like
you
know
you
that
sort
of
general,
like
sort
of
database
event
to.
G
I
Like
the
watermark
idea,
I
mean
we
could
show
how
anything
can
a
minute
event
based
on
various
bad
storage
solutions
that
we
had
and
then
any
of
the
any
of
the
consumers.
On
the
other
end
you
check
instead
of
functions
or
workers
or
whatever
you
want
to
call
them
and
and
but
they
receive
the
event,
because
they
know
that
event
type
looks
like
so
in
any
publisher
competitive.
I
You
know
some
mediary
and
any
of
the
consumers
because
they
know
exactly
the
tonight
looks
like
and
they
all
end
a
petition
to
some
Twitter
account
or
something
with
you
yeah
mr.
Blatter
nerd
image
I
mean
it
is
sort
of
the
quintessential
example
of
a
service
today,
an
event
driven
outside
to
get
away
from
it.
Yeah.
G
It's
simpler
to
just
have
an
example
of
an
event
that
we're
like
for
a
first
pass,
getting
an
event
where
all
of
the
data
is
in
the
event
and
you
can
operate
on.
Text
might
be
easier
for
people
to
like
understand
the
concept,
because
the
code
is
much
simpler,
it
doesn't
depend
on
other
libraries
and
it
would
also
be
inclusive
of
the
folks
who
don't
have
storage
offerings.
G
F
Why
I'm
always
using
I
like
I,
used
to
spin
certain
you
sail
fleet
thing
as
a
as
an
example,
because
that
actually
picks
up
a
bunch
of
the
ep.
It's
something
that
lots
of
people
can
relate
to
when
they're
building
business,
apps
and
then
I
basically
say
hey,
and
you
react
to
this
by
crediting
extension
into
your
application
and
that's
something
that
seems
to
be
resonating
I'm,
not
saying
where
we
should
use
that
exact
thing,
but
using
something.
G
G
C
C
F
G
G
Right
I
mean
this
was
part
of
our
point.
One
milestone
anyhow
right
because
I
I
think
there'll
be
I.
Think
our
Cloud
Storage
events
don't
actually
put
the
like.
We
don't
encode
the
actual
image
in
the
event
and
I
think
that
that
is
desirable,
because
you
might
not
want
to
act
on
the
whole
image
and
that's
like
a
potentially
a
lot
of
data.
You.
G
C
G
G
F
I
think
it's
actually
good
to
make
a
point
of
that,
that
you
know
if
you
go
and
send
it
a
cloud
event
and
you're
referencing
a
resource
in
that
cloud
event
the
receiving
that
clouded
and
doesn't
give
you
access
to
that
resource
necessary.
It
just
says
something
changed
and
if
you
want
to
get
the
details
then
still
need
to
have
a
way
around
it
to
going
access.
It
I.
G
G
C
F
Oh
yeah,
so
from
an
architecture
perspective
from
the
Sierra
like
from
the
CRM
system
that
I
was
talking
about.
I
was
not
thinking
about
that
being
a
database
raised
event,
but
it's
effectively
when
that
is
logically
created
in
seden
CRM
app.
The
CRM
app
raises
that
as
an
event.
So
it's
not.
This
is
not
a
trigger,
but
rather
a
something
that
the
CRM
app
does
as
a
I
just
created
a
new
object
inside
of
it
and
in
addition
to
storing
it,
I'm
also
going
to
raise
the.
G
G
G
F
G
C
C
Yeah
but
it
was
accepted,
it
didn't
it
was
consumed
and
then
the
new
event
was
produced,
and
so,
when
you
think
think
about
interrupts,
you
should
be
able
to
accept
it
from
anywhere
and
deliver
just
someplace
else.
F
G
I
think
the
routing
where
I
don't
know
if
we're
there
yet
to
have
consistent
routing
across
multiple
providers,
yeah
the.
F
F
F
It's
not
it's
not
gonna
work,
so
basically,
when
for
all
the
the
delivery,
the
details
of
the
delivery,
like
the
the
true
like
specific
needs
and
security
pieces,
there
will
be
some
special
accommodations
effectively
for
every,
certainly
for
every
target
and
mostly
for
every
middleware.
That's
there
and
then
we
have
to
go
and
figure
out
over
the
fullness
of
time
as
people
say
how
didn't
how
to
even
those
out
yeah.
G
G
G
B
G
A
F
That's
part
of
I
think
that's
part
of
this
common,
the
the
this
conflict
conflict
dependence,
because
all
of
those
things
will
be
different,
I
think
that's
part
of
the
we're
gonna
go
and
combine
things,
but
and
we're
gonna
make
sure
that
the
flow
is
compliance,
but
I,
don't
think
the
subscription
gesture
per
se
so
that
we
can
be
prescriptive
about
and
I'm
kind
of
everybody
will
want
to
show
their
own
thing
right.
Well,.
A
G
H
F
G
G
I
think
the
challenge
is
is
that
we
have
not
aligned
on
what
it
means
to
have
to
register
trigger
and
what
exactly
that
is,
and
so,
while
that's
interesting,
I
think
that
it
may
be
ambitious
for
three
weeks
from
now.
So
I
think
that
you
know
I
mean
Austin's,
not
here
and
I
know
that
he's
very
much
interested
like
they
have
their
gateway.
G
So
I
think
we
need
to
sort
of
hear
from
the
people
who
would
do
those
things
how
they
envision
it
and
I
think
that
if
we
move
forward-
and
we
have
these-
are
the
specific
events
we're
going
to
interrupt
with
and
there's
still
some
detail
to
work
out
about,
I'm
sure
right,
we'll
be
like.
Oh
no,
that's
not
what
I
imagined
it
to
be
when
we
get
into
the
exact
format
of
that.
Well,
then
illustrate
what
exactly
the
interrupt
is
and
then.
F
As
far
as
it
can
go,
is
you
could
say,
I'm
gonna
push
those
events
with
that
it
should
be
message:
format
effectively:
I'm
using
HTTP,
POST
and
I'm.
Gonna
react
to
HTTP
posts
on
my
function
on
my
HTTP
gateway
for
the
functions,
but
then
there's
the
end,
but
then
still,
there's
gonna
be
a
bunch
of
things
which
are
unresolved.
In
terms
of
you
know,
what
is
the
hosting
that
I
need
to
go
and
get
at
this
thing
or
do
anything
Agip,
and
how
does
all
those
things
work?
We're
not
gonna
get
to
that.
F
G
F
Have
I
think
I
have
a
version
of
that
yeah
I
can
I
can
I
can
try
it's
I'm
already
spending
most
of
my
day
on
this,
so
I.
E
F
A
C
F
That's
a
that's
a
good
step
towards
that
I
also
have
MQTT
name
could
be
mappings
already
written
I.
Just
don't
want
to
overload
people
with
review
stuff,
so
I'm
holding
those
holding
off
on
those
but
I
just
wrote.
Those
and
key
name
compete
mappings,
just
to
prove
that
what
we
have
is
will
go
and
that
cleanly
into
those
and
they
sit
in
my
a
personal
repo.