►
From YouTube: CNCF Serverless WG Meeting - 2018-03-21
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
A
A
A
D
I'll
be
curious
to
hear
kind
of
like
Kathy
and
and
or
Clemens
know.
Sarah
is
take
on
what
was
discussed,
but
it
it
kind
of
felt
like
we
devolved
again
like
things
went
off
the
rails
a
little
bit
really.
C
C
A
D
Sorry
I'm
trying
to
dig
down
it
so
where
the
points
actually
wound
up.
So
you
were
there
for
points.
A
D
No
I
think
we
actually,
we
did
make
some
progress
in
the
assumption
was
we
were
going
to
so
Clemens
and
or
anyone
else
interested
was
gonna
write
a
separate
action
related
to
a
write,
a
separate
issue
related
to
clarifying
middleware
that
was
really
kind
of
where
the
things
her
to
fall
apart
was
middleware
can
be.
You
know,
message
brokers,
it
can
be,
you
know,
API
gateways,
it
can
be
any
number
of
things
and
part
of
the
problem.
Were
you
here
for
this
by
the
way
Doug
I
had
you
left
by
that
point.
D
You
know,
use
cases
and
different
potential
implementations
of
what
middleware
will
actually
look
like
in
the
world,
because
it
was
driving
kind
of
a
you
know
from
an
IOT
perspective,
Freight
like
versus
using
message
pack
forces
like
a
cock-up
perspective
using
just
you
know,
schema
like
obviously
like
validated.
You
know
messages
say
like
the
Avro
or
whatever
it
is,
but
the
idea
just
generally
was
that
and.
D
E
Hi
doc,
this
is
khaki,
okay
copy
yeah,
so
I
think
you
know
we.
We
were
in
number
kind
of
number
three.
You
know
there
could
just
grow
up
and
we
talked
yeah
I.
Think
I,
just
follow
up
on
the
middle,
well,
I
think
we
would
always
said
we
agree.
We
will
add
some
example
there
like,
because
you
know
I,
don't
know
who
was
speaking
before
it's
a
harvester.
C
E
Then,
okay,
so
I
think
we
were
saying
you
know
yeah.
This
middleware
is
a
very
generic
terminology
or
like
more
clarification
on
that
it
could
based
on
this
definition
of
the
middle,
where
it
looks
like
it
could
be.
You
know
a
service
platform,
it
could
be
a
router
and
it
could
be
many
other
things
so
when
I
at
least
gave
some
example.
Okay,.
A
F
My
understanding
is,
we
were
through.
There
were
also
comments
that
were
filed
on
the
stock
on
this
part
of
the
document
after
we
left
and
then
I
addressed
them
all
so
I
think
we're.
My
understanding
is
were
done
with
this,
and
then
we
have
we
veered
into
a
discussion
of
one
of
the
items,
because
someone
asked
like
what
the
namespace
stories
about
so
talk
about
that
a
little
bit.
But
what
that
might
mean
we
don't
have
a.
We
might
do
a
clarification,
I
think
I
think
what
that
ends.
A
F
And
and
and
the
name
spit
the
name
space
I
want
to
keep
that
out,
because
the
name
space
is
basically
just
giving
out
or
framing
to
all
those
concepts.
But
I,
don't
think
you
can
really
talk,
argue
about
name
space
unless
the
the
inside
of
it
is
clear
so
which
means
the
topic
at
the
subject.
I
would
like
I,
don't
like
the
table,
the
name
space
discussion
and
talk
about
subject.
First
and
then
we
can
go
and
decide
whether
you
actually
need
the
names
right.
A
E
A
Not
okay,
okay,
so
I
heard
Kathy
speak.
Is
there
anybody
else
on
the
call
that
thinks
there's
something
that's
higher
priority?
Otherwise
we're
gonna
keep
heading
down
this
path.
A
E
Before
I
can
I
make
a
suggestion
before
we
dive
you
that
into
details
of
you
know
on
this
kind
of
first
cable,
like
a
high
level
of
you
know,
maybe
you
have
a
hierarchy.
You
know
on
relationship
between
these
terminologies
I,
don't
know
just
give
us
a
of
what
you
have
a
man.
I
know
that
we
can
dive
into
detail
of
each
each
field.
Yeah.
F
So
it's
a
two
stage:
it's
a
two
stage
model,
and
that
is
very
common.
As
I
explained
in
that
issue,
there
is
ample
precedent
in
existing
infrastructures
for
having
both
variations
of
both
of
those
fields
that
are
always
called
that,
but
there's
typically
this
two
stage,
classification.
So
from
a
higher
level
perspective.
F
Convention
dance
that
ultimately
from
if
you
look
at
it
from
really
high
up
it's
a
convention,
that's
the
producer
and
the
consumer
arrived
at
for
classifying
events
or
classified
messages,
so
that
the
consumer
has
a
reasonable
way
to
go
and
select
those
messages.
So
I
have
a
few
examples
here
that
I
show
in
the
topic
section.
So
let's
go
and
pick
so
that
the
US
cine
example
actually
peaked
right
out
of
the
IBM
and
queue
specification
where
the
and
are
actually
IBM
MQ
documentation
for
the
four
topics
and
topic
trees.
F
Where
you
have
it
and
you
can
go
in
and
read
this
and
I
can
probably
go
and
also
get
footnotes
if
anybody's
interested,
but
that
kind
of
gives
a
topology
a
classification
of
events
based
on
US
cities
and
they're,
grouped
by
country,
state
and
city.
Then
you
have
a
sheep
component
above
that.
That's
something
that
you
would
find
not
necessarily
in
this
nice
format.
It's
a
little
bit
more
convoluted
in
OPC
UA,
which
is
a
automation
standard.
Where
you
have
a
robot.
The
robot
has
a
number
of
drives.
The
third
drive
of
the
third
drive.
F
If
you
want
to
know
the
temperature,
so
you
have
a
logical
path
into
that
robot
towards
that
drive,
then
you
might
have
a
resource
path
and
it's
just
just
very
generic.
That's
what
but
most
of
the
services
that
we
run
and
and
most
other
people
have
there's
a
graph
of
resources
that
exist
and
you
drive.
You
have
a
path
through
that
resource
graph.
That's
a
tough
tough
example!
F
If
you're
mapping
and
you
are
expressing
as
their
consumer
expressing
interest
and
for
events
or
messages
related
to
that
particular
resource
path,
and
then
we
can
go
through
and
you
know
for
all
of
these.
For
all
of
these
examples,
the
the
the
the
theme
is
the
same,
there's
some
kind
of
a
resource
graph.
Sometimes
it's
a
tree.
Sometimes
it's
a
little
more.
F
Sometimes
it's
more
complicated,
but
you
typically
cutting
a
path
through
this,
and
this
is
how
you
are
finding
your
your
resources
or
subjects,
and
you
are
registering
interest
in
stuff
that
comes
out
of
those
contexts.
Sometimes
that
context
is
a
little
bit
larger,
so
I'm
interested
in
Francis.
Everything
that
that
robot
gives
me-
and
sometimes
that
is
a
little
bit
narrower
like
I-
want
to
have
everything
that
dr3
emits
from
that
Rover
robot
example,
and
sometimes
even
more.
An
error
and
I
want
to
have
a
particular
tell
that
particular
temperature
reading.
Only
from
that
robot.
F
F
Like
a
categorization,
and
even
in
the
case
of
what
I
just
showed
here
at
the
robot,
the
drive
you're
interested
in
in
the
temperature
interested
in
of
that
drive,
you
don't
actually
mean
the
drive
for
sale.
Yeah,
like
you,
don't
care
about
that
thing
with
a
serial
number,
but
if
technician
goes
it
goes
there
and
exchanges
the
drive,
which
means
the
physical
parts
and
puts
another
physical
part
in
there.
You
will
now
still
care
about
the
drive
as
an
abstract
thing
that
you're
watching
rather
than
you
know
the
thing
with
the
serial
number.
F
So
it's
a
bit
it's
a
higher
level
abstraction
model
typically
than
then
having
a
concrete
sender
that
you
care
about.
The
reason
why
this
topic
concept
is
so
successful
everywhere
is
that
it
provides
that
level
of
abstraction
that
everybody
can
go
and
map
there.
There
are
various
contexts
too,
so
you
send
you
sent
messages
that
are
belonging
to
a
topic
into
an
infrastructure
and
that
infrastructure
will
allow
than
others
subscribers
to
go
and
pick
messages
for
that
topic.
Now.
Topic
is
still
a
fairly
coarse,
coarse,
grains
grouping.
F
So
if
you
want
to
then
further
distinguish
messages
or
events
that
are
coming
out
of
that
topic,
which
means
let's
say
you
want
to
have
all
the
events
that
are
occurring
in
the
lighting
system
and
the
streetlight
system
of
Genoa
in
Alaska,
then
you
will
probably
want
to
be
a
little
bit
more
informed
and
filter
a
little
bit
more.
What
sort
of
what
what
kind
of
event
you're
looking
at
and
that's
what
the
subject
is
for
the
subject.
The
topic
is
the
thingy
King
Kong
subscribe
on.
You
say
I'm
interested
in
vents
from
this
topic.
F
So
the
topic
is
the
coarse
grout,
the
coarse
grain
thing
that
you
subscribe
for
and
then
the
subject
tells
you
what
this
particular
event
event
is
about.
That's
what
these
two
fields
are,
and
they
completely
replace
the
the
prior
notion.
So
topic
is
effectively
a
broader
definition
of
what
we
previously
had
a
source
and
then
subject
kind
of
collapses
onto
each
other.
The
notion
of
subject,
subject:
type
and
sort
the
subject
ID,
whereby
I
have
still
not
understood
what
the
subject
ID
stood
for.
B
If
I'm
understanding
properly
the
rob
the
robot
Drive
case,
you're
suggesting
that
the
temperature
it
depending
on
how
the
user
wants
to
model
this,
the
the
topic
could
actually
end
with
drives
three
and
then
the
temperature
could
actually
be
the
subject.
Absolutely.
Is
there
any
guidelines
how
to
make
a
distinction
based
on
usage
and
I'm
yeah.
F
So
it
would
actually
look
like
this,
where
you
have
a
robot,
but
the
Rowbotham
has
an
ID,
etc,
and
that
may
have
a
culture
it
drives
on
the
collection
of
draw
at
the
collection
is
then
the
collection
of
tries
is
obviously
a
little
bit
more.
You
know
specific
than
what
I
have
here
and
each
drive
has
an
identifier,
that's
logical
for
affecting
the
slot
where
that
sits,
and
you
would
put
a
an
observer
on
to
that
drive
and
then
the
observer
will
go
and
collect
the
information
items.
F
You
are
interested
in
from
that
drive,
and
so
you
would
compose
a
message
and
that
message
would
then
contain
all
the
items
that
you
have.
So
your
topic
would
be
the
drive
in
that
case
because
you're
particularly
interested
in
stuff
that
comes
I,
let
drive,
and
then
you
would
have
a
message
that
comes
out
of
that.
That
then
carries
you,
know
temperature
and
vibration
and
all
those
things
so
the
temperature
might
actually
just
be
in
the
payload
neck.
B
F
And
I
think
that
Matt
that
actually,
that
fits
the
case.
So,
let's
see
the
topic
concept
exists
in
Kafka.
It
exists
in
our
event.
Hubs
exists
in
event.
Current
exists
in
Apache,
ActiveMQ
exist
in
rabbitmq
exists
in
IBM,
MQ
exists
in
mosquito,
it
exists
in
5mq,
it
exists
I,
like
basically,
you
can
go
through
cops
of
broker,
but
their
event
oriented
or
whether
message
oriented
where
I
count
versus
the
mqtt
brokers
as
inventory
engine
and
every
single
one
of
them
has
at
least
the
topic
concept.
Then
there's
the
second
court.
F
F
F
It's
long
so
so
here's
I
actually
went,
and
so
this
entire
write-up
is
about
almost
nothing
but
topic
and
subject,
and
that's
why
I
wrote
it
to
declare
it
to
clarify
what
I
mean
and
also
but
I
felt
it
was
a
little
long
to
put
in
along
with
that
pull
request.
It
also
predates
the
pull
request.
So
SMS
has
a
subject.
Gcm
has
a
title
FCM
as
a
title,
but
they're
effectively
the
same
thing
functionally
Kafka
doesn't
have
a
subject
as
a
second
level.
A
second-order
field
because
Africa
is
gives
you
effectively.
F
Is
your
indication
above
the
messages
outside
of
the
partition,
ID
and
that's
a
design
choice
that
they
made
GMS
has
custom
properties
is
instead
of
a
standardized
subject,
fields,
IBM
mq
and
it
has
also
custom
properties
instead
of
the
standard
subject
field
the
ID,
mmq
AMQP
binding,
obviously
supports
Anka,
P
NP,
subject.
Field
and
nqt
also
has
no
subject
field
per
se,
but
also
they
added
custom
properties
in
ng
td5.
F
E
F
F
E
E
F
A
Architect
is
sharing
his
screen,
basically
and
just.
A
Actually
have
to
drop
in
a
sec,
so
marks
gonna
continue,
sharing
and
sort
of
Monterey
in
the
meeting
like
if
possible,
when
the
meetings
over.
Can
someone
write
into
the
agenda
doc
the
minutes
from
today
and
where
you
guys
left
off,
so
people
can
understand
what
was
discussed.
Okay.
Thank
you
guys
very
much
I'll
see
you
guys
tomorrow,
but
I
need
to
drop
right
now.
F
F
It's
it's
giving
you
an
alarm,
because
the
disk
read
was
less
than
so.
It's
a
it's
slow
disk.
So
what
I'm
doing
in
this
example
I'm
in
effect
that
you're
following
this
into
a
compliant
cloud?
Defense
event.
So
if
you
just
scroll
scroll
down
I,
do
this
stepwise,
so
I
can
go
in
and
tell
you
all
the
steps,
the
first
I'm
taking
that
that
event
and
I'm
sticking
that
into
a
I'm
sticking
it
into
a
container.
If
you
can
make
this
a
little
bit
bigger.
F
Okay,
no
now
I'm
effect
you're,
taking
the
event
that
I
got
and
put
that
into
the
data
field.
Of
that
event,
that's
the
first
step
that
I
do.
The
second
step
is
I'm.
Now
saying
what
that
event
that
I,
just
put
into
that
container
is
the
content.
Type
was
Jason
I'm
gonna
give
you
the
schema
URL,
which
points
to
the
schema
to
the
our
actual
schema
for
that
event.
F
So
these
are
the
first
two
steps,
then
I
go
and
give
it
an
event:
ID,
that's
the
the
literal
event
ID
then
I'm
just
pulling
up
from
that
event,
so
it's
I'm
using
the
event
that
he
asked
the
event
gave
it
to
me
and
I
also
pull
out
the
event
time.
The
next
the
event
has
a
type
and
I
explained
what
that
what
the
type
is
effectively
and
every
event.
F
F
Basically,
here
means
and
I'm
now
picking
from
a
few
candidates
right
what
I
think
what's
the
right
resource
type
is
and
I
make
a
discussion
so
for
your
storage
for
your
storage
problem
right,
the
right
topic
really
is
the
storage
account
and
in
that
storage
account
a
folder,
so
we
would
model
so
in
our
world.
We
would
model
this
as
subscriptions
good
resource
groups.
F
My
research
group
provider,
storage,
account
name,
slash
folder,
so
that
would
be
kind
of
the
topic
name
for
for
a
storage
account,
because
we
have
a
normal
resource
graph
in
Microsoft
and
the
global
in
imaginer.
In
that
global
resource
graph,
you
can
go
and
cut
a
path
right
to
the
storage
accounts
and
the
folder
in
that
storage
it
coming
that's
what
that
would
be,
and
that's
kind
of
what
I
lay
out
here.
So
hearings
in
specifically
I
pick
the
fully
qualified
path
to
the
specific
resource.
That's
how
I
picked
the
top.
F
So
the
topic
is
what
you,
what
you're,
what
you're
interested
in
right
in
a
coarse-grained
fashion.
So
this
could
be
a
storage
account.
It
could
be
a
VM.
It
could
be
like
all
of
our
200
services
that
we
have
an
azure
every
single
one
of
them
as
the
Rhys
is
mapped
into
this
resource
graph,
and
you
basically
take
a
click
in
place
and
that
resource
graph
that
can
go
in
the
middle
bet.
That
is
the
model
that
we
have
and
then
further
down.
F
So
I'm
interested
in
general
in
all
the
events
that
are
flowing
out
of
the
the
VM
host,
but
the
event
host
is
composed
of
multiple
slots
in
which
maybe
multiple
roles
and
so
I
want
to
catch
all
of
those
and
so
I'm
getting
the
information
about
which
exact
slot
and
which
exact
role
this
is
about
in
the
subject
field.
That's
the
mapping
that
I
did
for
something
that
has
nothing
to
do
with
the
dementing
system,
but
really
is
a
real
example.
F
And
then,
if
you
scroll
down,
I
did
the
same
thing
for
AWS
cloud
trail
right
where
I
did
I
take
a
cultural
event
as
it
is,
and
then
did
this
containment
mapping
thing
here
as
well.
In
fact,
you
seem
same
principle.
Well,
it
took
a
and
I
used
this
you
I,
don't
use
a
substitute
source
for
topic
and
literally
use
the
source
term
as
for
the
top
before
the
topic
field.
So
here
the
topic
is
so.
This
is
about
ec2.
F
It's
about
ec2,
Amazon,
AWS
u.s.
is,
and
that's
my
ec2
slot.
The
subject
is
the
in
the
particular
instance.
It's
the
event
type
stop
instances,
so
the
instances
got
stopped.
So
that's
easy.
I
can
understand
that
without
having
to
parse
anything
extra,
and
so
that's
how
that
maps,
and
then
it
took
from
software
AG
or
from
philosophy
from
an
IOT
platform,
simple
events
and
that's
the
door
sensor
was
triggered
and
not
that
in
the
exact
same
way
again,
I
have
the
source.
F
F
Events
and
I
don't
even
need
to
have
a
subject
in
this
case,
so
the
subject
is
something
that's
optional,
so
I
I'm
at
this
all
out,
because
that's
just
how
messaging
systems
use
those
fields
so
subject
is
something
that
you
sometimes
need,
and
sometimes,
though,
because
you
sometimes
need
to
have
a
further
qualification
that
you
can
go
in
this
patch
on
in
some
instances
whether
the
context
is
smaller,
you
don't
in
instances
where
the
context
is
larger.
You
do
and
topic
is
the
general
model
for
how
are
you
map
the
resource
graph
effectively?
F
C
C
I
F
This
is
well
we
actually,
we
so
I,
and
not
only
that
change.
The
name
I
also
change
the
definition,
so
I've
you've
been
using
source
here,
because
this
this
this
issue
predates
my
PR
for
changing
the
name
to
topic.
That's
the
only
reason,
because
I
wanted
to
refer
to
a
term
in
the
spec
right
and
that's
why,
but
but
I
think
so.
F
Well,
if
you
vary
the
messaging
protocol
like,
for
instance,
a
poppy
as
a
messaging
protocol
has
no
notion
of
from
and
with
good
reason,
because
the
problem
is
that
data
where
data
comes
from
turns
out
to
be
enormously
complicated,
typically
applications,
there's
an
application
at
the
application
layer,
above
that
you
have
a
fairly
complicated,
complicated
notion
of
data
provenance
with,
because
that
is,
if
you
build
sophisticated
systems,
because
that
includes
the
the
identity
under
which
the
process
runs.
It
might
include
the
person
who
is
operating
that
terminal.
F
D
Clemens
can
I
ask
a
clarifying
question
because
I
think,
if
I
understand
this
I
actually
really
like
the
distinction
here.
So
the
idea,
if
I
had
a
really
like
I'm
gonna,
create
a
really
simple
metaphor
here,
like
if
I
have
to
deliver
a
letter
to
you
and
I
can't
reach
you
so
I'm
gonna
hand
it
to
mark
and
Mark
is
gonna
hand
it
to
Kathy
and
Kathy
is
gonna
hand
it
to
you.
D
Ultimately,
the
topic
of
that
letter
has
never
changed,
but
what
presents
some
source
of
confusion
is
the
source
field,
because
the
source
field,
when
Clemens
receives
the
message,
is
Kathy,
though
actually
there's
a
chain
of
sources
along
the
way
that
you
actually
have
nothing
to
do
with
the
the
content
or
metadata
related
to
the
you
know,
the
message
being
the
envelope
that
to
be
delivered
to
Clemens.
So
the
idea
of
a
topic
here
ultimately,
is
a
cotton
to
me,
a
much
more
a
clear
statement
of
as
a
consumer.
D
F
D
Take
that
I
actually
really
like
this
distinction.
Quite
a
bit
my
question
for
you
actually
in
some
of
the
examples
you've
listed
like
we
have
like
robots,
/dr
I,
think
what
you're
and
correct
me
if
I'm
wrong
here
is
robot
and
identifier
cuz
I,
so
I
have
a
little
bit
of
confusion
here.
Right
like
USA,
Alaska
Juneau
is
very
clearly
country
state
city
right,
like
it's.
D
Specific,
like
that,
wouldn't
work
for
something
like
Japan
right
God
would
be
like
country
prefecture
right
like
something
along
those
lines.
Oh
they're.
Really.
What
you
have
here
is
it's
robots,
slash,
robot,
ID,
slash,
drives
right,
/,
yeah,
cray,
slash
temperature
right.
So
that's
where
my
a
little
bit
confusion
in
here
where
you
know
if
I
were
thinking
about
Kathy's
example,
which
is
let's
say
like
a
you
know,
I
put
an
object
into
an
s3
bucket.
Really
what
that
looks
like
is
slash.
F
D
F
F
C
D
I
think
the
more
logical
so
whether
the
were
like
the
actual
literal
namespace
right
that
indicates
like
if
I
were
to
go.
Look
at
you
know,
I
want
to
go
hit
a
describe
API
for
slash,
namespaces,
slashing
space,
ID
right,
I,
think
that's
what
Clements
is
trying
to
say.
These
are
like
not
not
generic
or
these
are
not
abstract.
You
are
eyes,
these
are
actually
concrete.
You
are
eyes
and
yes
they
so
there
will
be
well,
they
can't
be
whatever
you
like,
or
they
can
be
whatever
you
want
in
this
one.
F
Yes,
and
and
that's
what
you
would
typically
do
so
you
would
typically
go
and
and
have
innate
so
as
as
they
say
in
patent,
speak
in
an
embodiment
of
this,
you
will
have
a
some
kind
of
a
structure,
identifier,
a
your
I
that
well.
This
is
why
I
think
did
I
read
this
in
the
air.
I
think
it
should
be
a
your
I
and
I
and
I
write.
F
This
should
be
your
your
eyes,
specifically
because
I'm
keen
on
having
the
the
structure,
the
structuring
qualities
of
your
I
in
here
and
so,
and
it
gives
me
a
relative
or
absolute,
your
I,
but
I
want
to
have
the
the
structure
qualities
of
your
eyes.
So
you
will
have
a
you
know.
It
will
have
some.
The
the
event
will
be
about
some
context.
F
We
have
you
pick
a
topic
string
topic
string
the
topic
string
and
originates
from
a
context
in
your
application
and
typically
based
on
some
kind
of
a
object
that
is
in
your
context,
path
and
that's
what
you're
choosing
and
we
have
inside
of
that
context
that
you're
choosing
which
may
be
bigger
or
smaller
you're
gonna
have
another
uri,
potentially
a
sub
path.
If
you
will
that,
then
I
pinpoints
the
the
thing
that
the
event
is
about
and
that's
how
the
split
is
between
topic
and
subject.
F
F
So
that's
one
of
our
canonical
examples
right,
you're,
looking
at
a
bucket
and
now
you
want
to
be
informed
as
soon
as
an
object
is
created,
and
then
you
need
to
learn
what
that
path
is
of
that
object
and
that's
what
the
subject
is
and
the
reason
why
you
need
help
from
the
middleware
of
this
is
that
bucket
may
be
large
and
you
may
be
getting
hundreds
of
requests,
but
you're
really
only
interested
in
the
ones
that
have
the
suffix
jpg.
And
to
do
this,
you
need
to
give
the
middleware
a
generic
hint.
F
What
to
look
for
and
the
subject
field
is
one
that
you
can
do
a
longest
prefix
match
on
or
you
can
go
and
do
a
suffix
match
on
and
you
can
do
all
kinds
of
matching
on
and
that's
why
the
subject
field
as
one
of
factly
as
a
promoted
as
a
field
that
holds
data,
that's
promoted
from
the
event,
is
super
useful.
So
this
is
purely
for
the
benefit
of
the
middleware
to
enable
filtering
on
a
on
a
portion
of
the
contents
of
the
event.
E
So
climb
and
so
on.
So
if
I
understand
your
case,
so
you
are
so
this
topic
is
subject
is
for
the
to
assist
the
communication
between
the
subscriber
and
the
know
between
the
OSI
producer
event
producer
and
even
consumer
for
for
the
consumer
to
get
the
needed
information
right
is
that
for
that
purpose,
yeah.
F
F
That
is,
and
that
could
also
be
a
piece
that
lives
with
the
producer,
where
you
have
the
ability
to
go
in
and
send
send
messages
to
a
path
and
then
and
that's
what
the
topic
really
is
and
then
I
can
go
and
subscribe.
You
can
subscribe
to
on
that
path
and
you
can
either
subscribe
to
something
that's
further
down
in
the
path
and
you
get
fewer
messages
or
you
can't
go
and
subscribe
to
the
roots
of
that
path,
and
you
get
all
the
messages.
Okay,.
F
What
what
you
saw?
It
is
what
you
saw
in
the
example
that
I
that
I,
that
I,
that
I
gave
that's
in
the
item
in
the
process
that
I'm
suggesting
even
for
people
who
to
adopt
cloud
events,
is
containment
that
you
don't
change
any
of
your
of
your
existing
data
structures
at
all.
But
you
take
the
existing
data
records
as
you
have
the
new
stuff
them
into
the
data
fields
of
a
college
event.
F
Rapper,
and
then
you
take
the
club
and
then
you
take
fields
from
your
existing
event
and
just
and
promote
them
out
into
the
cloud
event.
Rapper,
that's
exactly
the
process
that
I've
been
doing.
So,
if
you
look,
if
you
look
at
an
example
again
so
look
at
the
here
here,
it
is
so
if
you
scroll
up
once
right,
this
is
the
original
end
of
yes
event.
If
you
scroll
down
the
exact
a
be
an
AWS
event
is
verbatim
could
contain
in
the
data
field
unchanged.
F
I
F
We
use
the
term
topic
instead,
yeah,
let's
yeah
exactly
so.
It's
a
topic
I
took
from
the
from
the
data,
and
this
data
is
obviously
just
a
log
record
from
from
from
yes,
I
took
the
their
generic
field
event
source,
which
is
the
ec2
system,
but
it's
not
really
the
source.
It's
like
the
system
level,
ec2
I,
took
the
data
center
and
then
took
the
account
ID,
and
that
made
a
a
reasonably
an
identifier
that
I
think
if
I
was
designing,
that
at
AWS
and
map
that
into
a
an
event
flow.
F
That's
how
I
would
design
that
I
would
say
subscribe
on
ec2
on
this
data
center
and
in
the
data
center.
On
this
particular
instance,
lot.
I
Actually,
I'm
not
sure
whether
that's
actually
true
for
that
particular
for
cloud
trail,
but
I
think
what
might
be
useful
is
if
you
could
set
up
a
set
of
examples
that
you
know
takes
a
AWS
is
three
records.
You
know
as
your
records
just
a
set
of
different
exits
or
tsa's
and
compose
these
headers
that
you
show
here
as
examples.
I
know
you've
done
a
couple
of
them,
but
I
think
it
would
be
useful
if
you
actually
use
the
term
topic
and
subject
that
you
have
here-
and
you
know
add
a
few
more
examples.
E
Think
that
that
probably
shows
you
knows,
because
now
we
all
have
a
very
generic
way
of
you
know
like
topic,
subject
right,
so
so,
when
you
send,
for
example,
as
a
consumer,
if
I
said
I
mean
I'm
like
I,
say:
I
need
this
topic
is
subject.
Well
that
event.
That
producer
knows
what
does
that
mean
what
so,
so,
how
could
I
say?
Okay,
if
I
need
this
information,
I'm
interested
in
topic
or
subject,
and
then
the
consumer
need
to
understand
what
you
know
and
I
mean.
E
What's
that
mean
right,
so
that
needs
to
be
well-defined,
the
other
way,
because
there's
so
many
different
scenarios,
I'm
just
thinking
you
know
how
many
sure
you
know,
people
like
to
use
this
and
then
to
be
compliant
with
this.
We
can't
Ronnie
you
so.
F
The
problem,
so
the
problem
I'm
Charlie
I'm
facing,
is
that
there
is
a
body
of
work
that
has
been
done
in
the
messaging
field.
Realized
in
countless
products
that
are
have
all
converged
on
this
notion
and
I
mean
I'm
having
a
hard
time
I'm
having
a
hard
time,
basically
communicating
the
industry
consensus
in
the
messaging
in
inventing
space.
That
already
exists
on
the
particular
something
of
of
having
a
topic
with
there's.
F
No
mountain
of
examples,
only--
core
secret,
because
that,
because
the
reality
is
that
what
we're
doing
in
the
messaging
space
as
we're
building
that
infrastructure
is
that
we
don't
take
a
stance
on
what
the
structure
of
these
topics
ought
to
be,
because
we
intentionally
leave
that
up
to
the
application
to
go
and
decide
how
it
wants
to
go
and
structure
those
things.
And
that
turns
out.
That
turns
out
to
be
to
be
beneficial.
F
So
all
the
examples
for
Asher,
for
instance,
will
look
pretty
much
exactly
alike
the
one
that
I
gave
you
that
that
I've
worked
out
and
asked
specifically
it
didn't
take
an
event
that
originates
from
my
org
will
look
exactly
the
same
across
all
the
same
services,
because
we
have
a
universal
graph
across
the
entire
platform,
where
we
can
identify
effectively
each
context,
and
so
the
natural
topic
path.
For
that
we're
using
is
the
effectively
the
resource
ID
for
for
that
resource.
So
I
can
give
you
a
hundred
examples,
but
they
will
all
look
the
same.
E
D
Well,
actually,
I,
like
the
idea.
I
think
this
was
the
request,
so
you've
done
a
really
awesome
job,
Clemens
kind
of
pulling
a
bunch
of
different
examples
in
let's
take
like
one
thing
like,
let's
say
like
doing
a
put
object
to
s3
as
your
object.
Storage
like
Oracle
object,
storage,
any
of
the
object
storages
across
all
the
clouds
right
like
yeah.
It's
a
firebase
even
and
just
do
the
the
mapping
of
that
one
specific
use
case
and
show
how
the
topic
and
subject
so
actually.
F
E
C
F
Can
do
that,
okay,
yeah
and-
and
so
here
and
I'm
actually
gonna
adjust,
because
I
can
go
and
edit
things
I'm
gonna
go
and
adjust,
because
this
also
predates
my
PR
I'm
going
to
edit
this
issue,
I'm
going
to
add
the
other
ones
to
go
and
make
it
topic
and
then
but
I
would
strongly
encourage
people
to
go
and
just
write.
3D
eat
the
bigger
issue.
F
I
wrote:
there's
a
lot
of
write
up
and
there's
a
lot
of
industry
context
in
there
with
you
know,
quotes
from
existing
system
or
links
out
actually
to
existing
systems.
There's
resource
collections.
In
fact,
you
should
see
how
IBM
IOT
does
it,
how
Microsoft
IOT
does
it
in
WS
IOT
it
does
it
and
to
illustrate
that
there's
industry
consensus
around
the
around
those
concepts
so
I
didn't
invent
those
I'm
gonna
I'm
gonna
have
a
like
two
or
three
slides
tomorrow
to
nail
down
that
concept,
probably
with
three
three
to
four
pictures:
yeah.
E
That
would
be
good.
Well,
if
you
can
give
example
say
you
know,
for
it.
I
just
gave
you
know,
use
Esther
days,
as
example.
If
I
need
some
information,
how?
How
should
I,
how
to
the
produce
I
mean
thus
consumer
feel
that
topic
is
produce
understands
that
we
need
to
define
some
something
there
for
the
defined
something
there
or
it
just
bite.
If
I
don't
know.
E
I
eat
it.
Yes,.
E
So
I
have
a
further
question
on
this
yeah.
It's
good,
it's
good
presentation.
So
for
the
issue
of
the
correlation
correlation,
I
ID,
write
correlation
poke,
so
how,
for
example,
I
find
I'm
interested
in
something
for
summarize
three
I'm
interested
in
the
information
same
thing
in
which
column
of
that
storage
right.
That's
what
I'm
interested
so
that
I
can
know
the
topic
and
the
subject
right
with
and
go
into
another
level
of
detail
in
that
column
which
file
especially
I'm
interested.
E
But
in
addition
to
that,
I
would
like
to
know
like
I
mentioned
before.
If
there
multiple
events
or
six,
why
is
you
know?
Storage,
but
the
other
could
be
another
event.
Source
could
be,
could
be
another
like,
for
example,
some.
Let
me
think
about
it.
Some
notification,
you
know,
event:
okay,
it's
not
a
storage,
okay,
another
notification
event,
but
these
two
event
might
might
be.
You
know
all
about
use
a
burglary
system,
okay
from
the
same
house.
E
Oh
there
are
so
many
houses
sending
me
all
this
information
right,
every
to
know,
okay,
which
you
know
which
storage
event
is
and
which
you
know,
which
has
simple
messaging
event.
These
two
events
are
coming
from
associate
with
the
same
house.
How
could
I
get
that
information
I?
Think
we
need
a
correlation
token
there
you
know
I
can.
H
F
F
F
What
typically
it
happens
is
that
people
use
a
some
middleware
to
go
and
create
that
correlation
that
happens
in
middleware
systems,
like
sometimes
you
do
this
with
with
stream
analytics,
where
you
have
temporal
correlation,
which
means
you
take
multiple
events
and
and
map
them
on
top
of
each
other,
because
they're
too
poorly
related,
and
you
only
want
to
have
a
view
over
the
temporal
stream.
So
you
use
a
stream
analytic
system
for
this.
F
Sometimes
you
have
the
problem
that
you
have
multiple
events
from
different
places
that
need
to
come
into
one
place
and
seek
for
them
separately
through
from
with
subscriptions
from
different
systems,
and
then
you
concentrate
them
in
something
like
an
actor
system
where
the
actor
acts.
On
behalf
of
the
context,
if
you
care
about
so
you
have
a
house
or
something
or
room
in
a
house,
and
then
you
have
an
actor
that
that
acts
on
behalf
of
that
they,
the
thing
that
happens
in
the
industry
right
now
is
the
concept
of
the
digital
twin
and
history.
F
Twins
are
basically
these
these
these
objects,
which
are
standing
in
for
any
arbitrary
context,
and
often
they
they
are
reflective
of
factory
floors
or
particular
machines
and
most
of
what
they
do
is
basically
they
go
and
concentrate
events
from
from
certain
sources.
They
typically
will
not
do
that,
though,
based
on
a
single
identifier
that
everybody
knows,
but
they
rather
will
do
this
from
from
different
from
different
information,
because
also
those
many
of
those
events
are
also
emitted
from
the
legacy
systems
that
don't
know
about
any
of
those
things.
F
So
so
setting
of
a
correlation
field
per
say
that
all
the
producers
need
to
go
and
set
it's
something
that
I
don't
see
as
common
enough
in
in
factional
usage.
That
I
would
put
that
into
the
standard,
but
it's
obviously
easy
for
you
like.
If
you
say
that's
the
way
we
want
to
go,
it's
obviously
easy
for
you
to
put
you
know,
a
correlation
ID
into
every
ura
event,
which
flows
in
through
the
common
infrastructure.
F
I
You
have
something
like
that:
ICU
Goods,
a
thing
called
a
resource
group,
and
you
talk
about
it's
a
scoping
construct
that
would
you
know,
finn's
or
group
up
a
number
of
different
resources
that
belong
to
specific
solution
does
not
mean
what
you're
at
we're
talking
about
here.
We're
really
saying
we
want
these
resources
to.
E
So,
okay,
so
you
just
mentioned
I
agree
with
you
that
the
correlation
ask
every
event
producer
to
add
a
correlation
ID
there.
It's
not.
We
had
that's
one
way
of
doing.
I
might
not.
You
know
I
report
even
producer
would
like
to
do
that
right.
Okay,
so
I
think
you
know
that's,
of
course.
If
you
know
the
event
source
can
put
a
correlation
ID
there,
that's
good!
Okay,
that's
a
really!
So
that's
what
we're
doing
but
might
not
be.
E
You
know
everyone
will
follow
that
another
way
is,
I
think
you
know
in
the
event,
so
the
eventually,
for
example,
for
that
burglary
system
right.
I
assume
that
the
motion
detector
and
the
door-open
detector
when
the
information
is
sent
out
there
will
be
some
like
how
not
house
a
House
member
something.
You
know
a
unique
identifier
for
that
house.
There
will
be
your
information
inside
is
inside
those
event
message.
You
know
just
different
vendors,
for
example
the
sensor
different
sensor,
vendors
and
different.
E
So
if
we
can
have
you
know
in
them,
I'm
thinking
you
know
if
we
can't
define
a
way,
you
know
we
do
not
know
where
it
is
put
right,
but
the
producer
knows,
for
example,
if
they
house,
member
or
IP,
address
to
identify
that
house,
okay,
whatever
what
he
was
acting,
they
know
where
they
put
it
right
because
they
are
equipment
for
that.
But
if
they
let
us
know
where
they
put
it.
So
there
is
a
that's
information
we
can.
You
know,
put
into
the
spec,
see
information.
H
E
F
A
proposal
for
you,
because
I
think
that
that
problem
that
you're
just
illustrating
is
it's
actually
solvable
within
the
scope
of
what
we
discussed
today,
because
because
you
just
talked
about
because
you
just
you
just
you
just
actually
led
with
the
fact
that
there's
a
there's
a
structure.
So
there
is
houses,
there's
buildings
you
care
about
and
each
house
hasn't
hasn't,
has
a
unique
ID.
Let's
say
you
have
you
have
country
organizations,
each
country,
organizations,
issues,
house,
IDs,
right
and
so
and
in
these
houses
interesting
stuff
that
you're
interested
in.
F
So
you
are
making
a
topic
in
your
infrastructure
in
the
Uwharrie
infrastructure.
That
is
that
that
has
a
number
slash,
a
topic
that
is
called
slash
de
slash
one
which
is
my
house.
Okay
and
all
of
all
the
all
the
objects
that
are
sitting
in
my
house
that
are
talking
with
your
system
will
now
publish
their
events
to
that
topic.
Slash
de
slash
war,
which
now
gives
you
a
perfect
place
where
you
can
go
and
pick
up
all
those
events,
because
you
only
need
to
go
and
subscribe
to
slash
the
EE
/
one
and
you're.
F
Getting
all
the
events
from
my
house
and
then
you
can
in
the
subject
is
then
the
identifier
of
the
actual
sensor
that
gives
you
the
information,
yeah?
Okay,
that's
what
that's
what
so?
That's
how
that
solves
your
problem,
your
problem,
you
solved
by
creating
a
a
a
broad
scope
that
you
can
go
and
subscribe
on,
and
it
would
not
be
as
simple
as
it
would
likely
not
be
as
simple
as
/ge
slash
ID,
but
something
that's
a
little
bit
more
sophisticated
yeah.
E
Yeah
yeah
I
think
we
are
along
the
same,
no
swords
throughout
it.
So
I
think
you
know
so
we
were
like
safe,
but
the
thing
is
that
when
I
goodnight-
so
actually
it's
not
like
you
know
on
the
consumer-
will
send
a
message
to
the
producer.
Say:
okay,
give
me
this
information,
I'd
like
to
say:
okay
mendicancy,
another
producer
fading,
an
information
of
that
past
say:
okay,
what
is
you
know,
the
correlation
poke
and
where
my
car,
you
know
the
house
member
is
located,
so
we
might
receive
that
message
right.
E
That's
I
can
just
go
directly
to
search.
You
know
inside
that
big
chunk
of
you
know
event
data
plus
its
metadata
I
can
just
you
know,
based
on
that.
I
can
just
extract
that
information.
For
example,
if
we
say
okay,
it's
a
it's
a
house
number,
okay,
that's
a
that's!
The
house
number
is
a
unique,
so
I
can
just
search
you
know,
house
address
I,
can
just
search
house,
I,
dress
and
then
I
get
the
value.
Of
course
the
value
could
be.
You
know
tremendous
house,
tragic
could
be
you
know.
E
Lewis
house
address
or
Kylie's
house
address.
The
value
varies,
but
I
know
what
string
I
need
to
search
I
just
search.
You
know,
house
address,
oh
that's
unique
and
for
another
use
case
it
could
be.
You
know,
I,
don't
know
something
like
for
travel
request,
ID,
so
I
search,
travel,
request,
ID.
Of
course
the
value
could
all
be
different
right.
Different
people
are
coming,
travel
requests,
but
really
you
know
the
producer
should
be
me.
You
know
because
he
knows
the
producer
knows
right.
E
F
E
F
You
are
now
interested
in
your
solution
from
all
events
emitted
from
one
building
and
you
want
to
have
them
in
real
right.
Yes,
that's
what
this
is
about,
hear
that
right,
it's
about
getting
at
that
information,
real,
fast
and
being
able
to
get
some
targeted
messages
towards
you
right,
just
as
a
just
as
a
as
a
reference
number.
F
We
currently
do
1.5
trillion
messages
a
day
just
in
terms
of
the
events,
so
you
have
to
be
able
to
get
to
get
to
a
few
events
very
specifically,
so
you
able
to
filter
on
them
what
you're
looking
for
there.
So
what
you're
looking
for
here
is
a
bit
is
the
ability
for
20
sensors,
which
are
in
one
house
exactly
and
be
correlated
together.
Exactly
you
can
get
the
events
for
all
of
those
20
with
affected
from
one
pipe
right.
Yep.
E
F
So
that's
what
the
topic
wants.
A
topic
model
allows
you
to
do
this,
because
all
of
you
are
all
of
your
resources
exist
on
a
graph.
The
graph
has
the
first
level
and
our
graph
that
we're
just
talking
about
has
two
levels.
First
level
of
the
graph
is
countries.
The
second
level
of
the
graph
is
identifies
for
individual
houses.
E
F
E
Okay,
let
me
okay
the
scenario
different
okay,
so
I'm,
a
service
platform,
okay,
Oh
for
somebody's
platform,
it's
going
to
handle
so
many
different
events,
so
many
different
uses
scenario
rice.
So,
while
using
scenario
is
interested
in
the
consumer,
the
the
burglar
system
helps
okay,
many
other
scenarios
so
as
a
service
platform,
so
I'm
the
service
platform,
I,
don't
know
whether
I'm
interested
I
do
not
really
I'm,
not
somebody's
platform.
It's
not
the
application
developer.
When
I
say
application,
I
mean
the
very
system:
okay,
developer
I'm,
not
super
user.
E
The
system
developer,
I'm,
just
a
middleware
or
platform,
not
you
know,
receive
the
even
erotic
to
your
function
to
your
application,
the
burglary,
a
detection
function
right
so
as
a
service
problem,
I
do
not
know
whether
I'm
interested
in
you
know
a
house
or
I'm
interested
in
the
tribe
or
request.
Id
I
have
no
idea,
but.
F
E
Okay,
so
okay,
so
I
would
need
the
application
developer,
which
is
a
burglary
detection
function.
Application
developer
I
need
him
to
let
to
tell
my
service
platform,
saying
oh
I'm
interested
you
know
in
this
house,
so
he
must.
Let
me
know
what
he
is
interested,
he,
okay,
the.
What
what
the
correlation
told
him
he's
needs,
what
the.
F
E
Token
so
supplement.
Let
me
know
nation
token,
that
token
can
be
a
path:
okay,
I'm.
Just
using
that.
As
you
know,
what
I
need?
Okay,
I'm,
not
saying
there
should
be
a
specific.
You
know
Cartesian
token
field
there,
of
course,
if
the
producer
putting
that
that's
fine,
but
it's
just
a
stream,
the
stream
could
be
a
URL
who
could
be
are
like
in
JSON
format
could
be
a
path
identifier,
okay,.
F
E
So
so
the
let's
go.
So
let's
see
just
okay,
let
me
so
then
I
need
the
application
developer.
The
function.
You
know
logic
developer,
to
tell
the
serratus
platform
saying:
okay,
I'm,
you
know,
might
cut
the
correlation
token
when
I
say
card,
eight,
okay,
it
just
me
that
means
okay
is
a
house
know.
Is
this
you
know
pass
to
that
house?
Member,
oh!
Is
that
your
eye?
You
know
to
that.
You
know
it's
a
travel
case
ID.
So
that's
why
I
need
a
field.
I
need
someone.
E
You
know
to
tell
the
the
service
platform
meet
the
function,
developers
how
it
what
he
needs
and
then
I
can.
Just
you
know
I
would
not
get
the
event
data
I
can
extract.
You
know
that
message
based
on
the
specification
of
that
token.
You
know
it's
tribal
ID
or
it's
a
what
and
then
you
know
to
extract
the
value
right.
If
you
say
it's
a
house
I'm
going
to
try
the
house
number
a
house
I
dress,
but.
F
F
E
It's
a
string
or
it's
just
a
string,
it
can
be
URI
ID
or
it
can
be
on
half
my
desire.
So
how
would
I
put
this
inside?
You
know
this
fact
so
that
you
know
the
function.
Developer
knows
okay,
he
needs
to
specify
this
and
then
they
the
you
know
the
was
act,
of
course,
if
the
even
producer
put
a
little
correlation
Hogan
as
a
key.
That's
good!
That's!
Okay!
Properly!
Perfectly
fine,
but
I
would
like
that
to
be
in
this.
So
I
will.
E
Let's
just
say
you
know
you
can
use
a
string
or
use
your
eye,
but
you
know
correlation
token.
Is
the
meaning
it's
what
it
means?
Otherwise,
if
we
just
say
topic,
you
know
the
the
function
developer
doesn't
know.
What's
that
topic,
what
topic
are
you?
It
turns
out.
A
lot
of
people
know
what
a
topic
is
right.
There
are
many
many
semantics
on
topic,
so
one
of
the
top.
It
will
be
a
correlation
token.
That's
my
point.
E
A
E
Just
yeah
your
site,
okay,
that's
good
weather!
Have
a
sometime
sorting
this
out,
I
mean
to
how
to
write
this
up.
Yeah,
okay,
have.