►
From YouTube: CNCF Serverless WG Workflow Meeting - 2018-07-10
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
A
Good
I
think
we
can
start
now.
Other
people
can
try
later
so
today.
So
let
me
first
share
the
agenda.
I
think
first,
song
I'm
thinking
of
right
go
to
the
use
case,
discussion
and
I.
Think
some
of
people
already
put
some
use
cases
in
the
document
and
then
we
have
a
presentation
of
existing
offerings
and
features.
This
is
the
action
item
from
mass
meeting
and
then
we
can
go
through
some
review
comments.
On
the
proposal
document
I
saw
some
people
putting
the
reveal
comments.
A
A
A
For
me,
okay,
great
good,
thank
you.
So
let
me
first
goes
through
the
use
cases.
I
think
you
know
so
we
have
several
people
put
in,
so
these
people
put
in
some
use
case.
So
first,
this
use
case
I
put
in
this
use
case,
so
I'm
gonna
go
through
it.
It's
not
like
home
monitoring
use
case.
I,
think
you
know.
The
purpose
of
we
go
through.
The
use
case
is
to
one
purpose,
is
to
I
just
come
and
say
whether
we
need
a
human
state.
A
C
A
Okay,
good,
if
you
can
see
okay,
let
me
see
whether
this
will
make
it
Dodger.
We
always
have
you
yeah,
oh
I,
think
he
sorted
100,
maybe
okay,
okay,
so
so
this
does
shows
it's
a
home
monitoring
system.
Of
course
in
this
is
just
not
you
know.
I
really
did
help
the
home
monitoring
system
different
types,
but
this
is
just
her
monetary
application.
A
A
It's
not
a
waking
state
for
you
and
basically
you
know
the
first
event.
No
matter
is
event
is
at
or
open
or
motion
detection
event.
That'll
work,
Segura
the
function,
no,
the
workflow
to
start
any
of
these
two
event.
So
the
first
event
first
date
actually
is
an
event
state,
because
it's
waiting
for
an
even
any
event
count.
Then
you
know
is
going
to
start
the
workflow
and
the
enter
so.
A
That's
right,
okay,
so
it's
drawing
this
way,
I
think
to
another
way.
So
there
is
a
start.
You
know
it's
not
a
state,
but
you
know
there's
a
start,
start
start
how
to
say
starting
point
and
then
the
first
event
comes.
It's
a
mint
state.
Okay,
so
I
draw
this
way.
I
guess
different
people
differently.
This
is
just
representation
issue.
So
what
I
mean
is
you
know
in
this
state
when
the
event
one
or
even
two
counts?
Any
of
this
amount
is
going
to
transition
to
the
next
state?
Okay,
so
he
in
state
1.
A
So
when
any
of
the
event
comes,
workflow
starts,
and
then
you
know,
if
it's
door,
opening
event
is
going
to
transition
to
the
next
state.
If
it's
a
motion,
event
is
going
to
transition
to
it's
going
to
okay
to
trigger,
so
this
event
will
trigger
a
function
called
face.
Recognition
function
to
recognize.
E
A
Exactly
exactly
god,
that's
what
I
pick
a
shoebox
right
and
so
the
application.
You
know
this
application
monitoring.
You
know
you
could
receive
to
open
first
and
then
later
a
motion
detection
or
you
could
raise
your
motion,
detection
sensor,
event
first
and
then
later
at
opening,
but
right
so
it
depends
on
the
scenario.
So
that's
why
the
order
to
handle
this
scenario
this
state
needs
to
be
able
to
you
know
to
accept
you
know
multiple
events
and
then
different
events
could
branch
out
to
different
next
state,
as
you
just
mentioned
yeah.
A
So
if
it's
let's
go
so
if
it's
the
opening
event
on
it's
going
to
transition
to
state
two,
if
it's
an
emotion
event,
it's
going
to
first
figure
a
function
for
face,
recognition
to
recognize
with
its
family
member
or
not
family,
member
right,
if
it's
a
family
member,
so
of
course
that's
the
result
of
the
function,
one,
this
server
dysfunction.
If
it's
a
family
member
everything,
fine,
no
there's!
No!
This
is
a
force
or
not.
If
it's
not
family
member,
then
a
transition
to
the
next
state
which
I
gave
it
to
me
state
for
okay.
A
So
and
then
you
know
in
state,
for
you
know
it's
going
to
here,
it's
going
to
wait
for
another
event
to
see
whether
there's
a
door
open
event
or
window
opening
event,
I
simplified
it
a
bit
here.
I
didn't
mention
the
window
open
because
similar
to
the
open
man,
so
it's
going
to
wait
for
another
event
at
this
event
happens:
okay,
if
there's
you
know
it's
not
family
member
and
then
the
doors
the
front
door
was
open.
A
Then
you
know
it
is
it's
most
probably
it
could
be
a
burglary
I'm
broke
into
the
and
breaks
into
the
house
right
and
then
so
there
will
be
a
it's
going
to
trigger
another
function,
so
this
event
is
going
to
trigger
a
function
second
function,
which
will
send
a
message
to
the
two
contacts
on
the
fire:
okay,
so
whatever
every
home
becomes,
you
know
you
can
put
into
context
okay.
So
now,
let's
stop
here
I'm
going
to
go
to
the
left
side,
yeah.
A
That's
a
very
good
question,
so
this
should
be
okay,
so
there
should
be
a
timeout
right
over
there.
That's
how
I
think
you've
already
come
into
how
we
are
going
to
design
to
support
this
right.
So
that's
very
good!
You
know
there
should
be
a
timeout,
because
if
it's
long
time
between
the
gap
right,
it
doesn't
necessary
mean
it's
a
popular
right.
So
for
this
application
yeah
there
should
be
a
timeout
here.
Okay,
so
let
me
stop
this
I
go
to
the
side,
fix
the
door
opening
event.
A
There's
no
function
to
trigger
to
possessing
it.
It
just
go
to
statement
in
state.
Two
is
going
to
wait
for
another
event,
which
is
emotion
that
actually
event
again.
This
should
be
a
time
out
time
out
where
you
associate
with
this.
You
know
state,
and
then
you
know
when
they
get
a
motion
and
detection
event.
It's
got
the
same
thing,
so
the
door
is
going
to
do
a
face
recognition
if
it's
family
member,
that's
fine!
You
know
the
family
member
opens
the
front
door.
That's
okay!
A
If
you're,
not
family
member,
then
when
it's
going
to
go
to
state
3
so
at
stage
3
also
to
event
already
happen
twice
open.
The
other
is
motion
and
then
same
thing.
It
could
be
a
burglar
breaking
into
the
house,
so
it's
going
to
send
them
as
trigger
a
second
service
function,
send
the
message
to
the
contacts
under
fire.
So
these
tools,
and
now
we
come
to
either
state
3
or
stick
form.
Of
course,
only
in
the
reality,
only
one
pass
will
happen
right,
but
no
matter
which
has
happened.
A
So
when
we
come
to
here
so
now
we
are
wait
for
the
response.
How
is,
and
so
this
function
toward
ascend
text
message
and
email
to
the
context,
and
then
we
come
to
stay
five
stay
five
has
to
wait
for
another
external
event,
which
is
a
response
from
the
from
the
two
contacts.
So,
if
suppose,
say,
there's
a
response,
then
you
know
it's
going
to
do
automatic
language
processing
say
what
and
the
response
it
is.
Is
it
okay
response
or
not?
A
Okay,
because
when
when
this
message
sent
is
going
to
send
together
with
the
image
to
you,
know
it's
not
family
member
I
send
the
image
and
then,
if
the
response
say
always
okay,
everything,
fine
as
a
foursome,
if
you
say
so
now,
okay,
then
it's
going
to
trigger
a
notification
message
to
the
police
department.
You
know
all
those
emergency
department,
okay
and
then
now
come
back
to
save
life.
So
here,
if
they
timeout
suppose-
and
here
you
start
a
timeout
right-
if
it
came
out,
it's
going
to
automatically
what
that
means.
A
There's
no
response
from
the
from
the
two
contacts:
there's
no
text
response
or
email
response,
then
it's
going
to
call
automatically
dial
the
number
to
call
the
the
contact
and
then,
if
the
response
day,
okay,
so
not
okay!
So
then
you
know
it
goes
through
the
same
process.
I
simplify
a
little
bit
on
the
whole
because
our
purpose
is
not
to
really.
You
know.
These
are
home
monitoring
system.
I
just
uses
how
pond
monitoring
application
as
a
use
case,
so
when
they
need
to
migrate
to
serve
this
platform
right.
A
So
what
we
could
you
know
what
we
need
to
support
the
whole
workable,
so
we
I
think
we
already
see
that
we
need
the
event
state
because
they
are
similar
state.
That's
you
know,
wait
for
external
event.
Also.
We
need
to
support
by
timeout
in
that
state.
If
we
wait
for
an
event
right,
there
is
also.
Actually
it
also
shows.
We
need
to
correlate
this
event
because
a
door
open
and
the
motion
detection
we
need
to
know
they
come
from
the
same
house.
Otherwise
you
cannot
occur.
A
You
cannot
say,
okay
door
open
from
you
know,
for
example,
Rachel's
house
to
a
motion
detection
event
coming
from
Kathy's
house.
That's
not
right!
So
so
here
I
think
we
already
derive
some
requirements
say
we
need
to
support
event.
State
we
need
to
support.
You
know
was
that
the
time
in
a
timer
in
the
in
that
state
also,
we
need
to
support
the
correlation,
because
you
know
all
these
events
and
I
think
you
know
in
real
sorry,
some
movies
been
the
Soviets
perform
really
start
to
support
surveys.
Application
is
not
just
a
single
event.
A
A
So
this
is
this
use
case,
any
questions.
A
F
I
ran
ahead
and
put
a
couple
of
use
cases
there
in
general.
They
are
far
more
simpler
than
what
you
just
went
through
so
and
you
know
they're
they're,
not
the
complete
details,
it's
just
a
basic
cases
that
you
would
that
that
can
be
used
to
implement
the
basic
example.
Here's
one
it's
a
basic
loan
approval
process.
Of
course
you
can
add
far
more
complexity
to
it.
I.
G
A
A
F
Alright,
sorry,
so
let's
go
down
to
the
second
one
I'll
correct,
then,
okay,
so
let's
say
this
is
for
a
basic
employee
travel
booking
the
all,
but
the
gets
airline
tickets
from
from
our
employers.
So
this
is
what
it
would
look
like.
The
first
thing
is
the
employer
goes
at
the
employee.
Goes
sorry
a
little
bit
higher
up
there.
You
go.
F
Event,
one
is
the
employee
goes,
he/she,
submits
a
form
books,
a
ticket,
the
form
will
be
in
Terry,
Dana
storage
or
in
a
database
once
they
that
that's
that's
what's
shown
in
the
diagram
is
event
one.
Once
he
went,
one
happens,
state
one
will
go,
execute
basic
function,
one
which
is,
you
know,
call
it
a
travel
validation
function.
This
will
essentially
check
the
employer
employees
current
status
employed,
not
employed
current,
create
in
case
the
in
case.
The
employer
has
limits
on
grade,
like
some
employers
do
some
don't
after
he
does.
F
And
in
after
the
validation,
if
the
validation
succeeds,
an
email
will
be
sent
to
the
Meritor
to
the
employees
manager.
It's
all
part
of
the
function,
one
travel
validation
function
after
it
does
sense,
a
email
or
whatever
notification,
etc.
The
workflow
transitions
to
state
two.
It
stays
there
until
and
until
and
unless
the
manager
basically
approves
or
rejects
it.
And
someone
just
said
yes:
there'll
be
a
timeout.
There
they'll
always
be
a
default
timeout.
F
F
So,
let's
take
the
simple
case:
the
manager
approves
or
disapproves
the
as
soon
as
even
comes
state
to
will
transition
to
the
next
state,
I've
called
it
an
approved
state
I
could
as
well
have
called
it
just
the
state
three
state,
four
in
in
the
approved
state,
it's
essentially
as
few
as
yes,
you
are
checking
for
the
results
of
the
event.
He
went
to
if
it's
a
yes,
then
in
transition
to
state
three.
If
it's
a
no
that's
it
approver,
the
employee
travel
request
was
not
granted.
It
ends
once
you
move
to
state
three.
F
The
next
thing
is
you
see,
essentially
just
like
AWS
start
multiple
parallel
functions.
You
basically
check
the
price
for
a
line,
a
a
line,
B
etc.
After
you
get
all
the
other
responses
back
you
transition
to
state
for
in
state
four.
You
essentially
compare
the
function,
not
necessarily
for
pricey.
Compared
for
time.
You
can
pay
for
quality
factors.
F
Whatever
your
business
logic
is
after
you
do
that
you
finally
figure
out
which
which
airline
you're
gonna
poke
at
you
move
to
state
five
and
then
fi
you
finally
go
ahead,
do
the
actual
booking
and
that's
where
the
workflow
ends.
You
know
it's
just
an
exemplary
workflow
that
I'm
trying
to
illustrate
for
the
case
of
yeah.
D
I
think
I'm
still
not
able
to
wrap
my
head
around
right
same
question
when
we
start
having
states
that
waiting
for
another
function
to
come
in.
That's
the
equivalent
of
me
running
a
service
waiting
for
a
request
to
come
in.
It's
completely
beats
the
concept
of
server.
Let's
ride,
why
can't
we
have
this?
Is
you
busy.
D
Waiting
for,
like
the
manager
approval
over
here,
so
we
can
have
a
function
which
is
basically
approve,
sorry
to
create
a
ticket
so
booked
a
ticket.
Somebody
does
that
and
that
creates
tricks
of
validation.
That's
great
and
then
extends
another
function
to
send
an
email
to
your
manager
and
that's
where
the
workflow
ends.
Now,
when
the
manager.
C
D
H
F
Well,
that's
the
beauty
of
the
implementation.
There
are
multiple
ways
to
do
it.
If
you
do
it
using
golang
using
thread,
EIU
Fred
will
be
wearing
that's
one
way
to
do
it.
That's
that
that
that
explains
your
explanation,
is
you
basically
save
the
state
to
a
database
and
basically,
at
that
point,
just
wait
and
when
the
thread
kicks
in.
D
F
The
whole
point
of
this
is
so
what
you
are
suggesting
is
what
AWS
does
it's?
Basically,
you
break
a
workflow
into
multiples
into
multiple
step
functions
and
you
are
basically
interconnecting
the
step
functions
using
essentially
lambda
for
inclusions.
So
that's
one
way
to
look
at
it.
I
think
a
more
with
that,
if
you
have
to
troubleshoot
at
hey,
it's
like
you
have
a
workflow
consisting
of
let's
say
a
WSS,
some
examples.
You
have
something
like
seven,
eight
different
step
step
functions,
all
of
them
interconnected,
using
lambda
functions.
F
If
you
have
to
start
troubleshooting
a
workflow
one
is
currently
in
step
function
three
and
it
is
stuck
in
function
for
would
that
be
easier
and
remember
that
itself
that
workflow
itself
will
scales.
So
you
could
have
n
instances
of
a
workflow
instance.
One
is
run
currently
running.
Step
function,
three!
It's
stuck
in
the
middle
of
function!
Three!
Now
there
is
here
right
now,
every
workflow,
that's
it
it's
its
own
self-contained
instance.
If
you
need
to
troubleshoot
this
hey,
the
first
instance
of
this
workflow
is
currently
stuck
in
state.
Do
we
need
to
troubleshoot
that?
D
This
will
be
more
difficult.
The
reason
is
because
I
have
so
many
people
stuck
in
different
states,
and
then
we
gonna
get
a
manager
response.
We
have
to
make
sure
this
manager
response
is
gonna.
Go
unlock.
This
workflow,
like
there's
gonna,
be
a
lot
of
correlation
lot
of
state
keeping
that
will
need
to
happen
in
this
case.
D
I
I
D
D
So
for
a
developer,
I
think
this
is
gonna,
be
a
lot
more
complex,
because
now
you
have
these
different
states
which
are
wait,
States,
so
I
have.
This
is
going
to
leak
into
so
many
of
my
workflows
that
are
open
and
that
I
need
to
have
something.
That's
gonna
go
clean
out.
These
states,
which
are
timed
out.
A
Well,
I
think
you
are
mixing
the
users
perspective
with
some
with
a
back-end
implementation.
I
think
all
those
complication
you
mentioned
is
a
fact,
an
implementation.
It's
all
the
users
perspective
from
the
user
perspective.
You
only
need
to
draw
this
workflow
just
one
motor
flow,
but
you
are
back
and
you
to
take
care
of.
You
know.
You
know
when
we
you
know
are
like
you
know,
to
move
to
the
next
state
like
how
to
correlate.
You
know
this
event,
that's
your
back-end,
it's
not
the
user.
Your
user
doesn't
care
how
you
do
it
right.
A
I
know
you're
going
to
implement
the
workflow
understood
if
we
mix
the
users
perspective
of
them.
You
know
the
users
interface
with
the
back
and
imitation.
You
know,
then
you
are
going
to
I.
Think
it's
not
right
the
background.
You
know
you
can
do
whatever
you
like
right.
There
could
be
in
a
simple
implementation.
They
could
be
complicated
information,
but
that's
not
you
know,
I
think
what
we
we
were
really.
You
know
address
a
lot
here,
but
from
users
perspective,
he
just
need
to
you
know
to
specify
this
one
workflow.
A
Instead
of
specifying
a
multiple
workflows,
that's
all
user
need
to
do
user,
doesn't
care
how
you
are
going
to.
You
know
transition
to
how
you're
going
to
implement
this.
You
know
how
you
correlate
all
these
events
together.
How
you
scale
out
also
now
come
back
to
the
implementation
plan
appeal.
So,
let's
just
say:
okay,
it's
my
workflow,
multiple
workflows.
Then
they
use
I
need
to
configure
multiple
workflows.
They
need
to
configure
how
these
work
clothes,
you
know
associate
because
they
all
belong
to
the
same
enterprise
right.
A
D
Absolutely
right,
I
think
I
am
thinking
definitely
more
from
how
I'm
gonna
make
sure.
Once
we
define
this
language,
how
we're
gonna
make
sure
that
we'll
be
able
to
actually
edit
her
to
it
and
implement
it.
So
you
guys
are
right,
I
think
from
a
developer
who's
using
a
service
that
is
following
this
language.
It's
definitely
easy,
but
I'm
really
worried
that
people
will
not
be
able
to
implement
this
well
and
that
might
lead
to
a
bad
experience.
So
I'm
yeah,
you
guys,
are
right.
I'm
thinking
from
a
different
perspective,.
A
Okay,
great
so
now
we
can
talk
about
how
the
back
end
you
should
implement
it.
Of
course,
I
think
different
companies.
It's
going
to
implement
a
different
way
right,
but
you
know,
actually
it's
not
really
complicated,
I
see
what,
if
you
really
think
through
it,
I
trade.
There
are
ways
to
make
it
simple.
I
think
you
know.
One
thing
you
know
you
mentioned
say:
are
we
can
postpone
that
discussion
to
later.
F
A
J
D
D
J
D
J
A
Okay,
yeah
I.
Think
your
point
is
you
know
there
are
existing
ways
to
support
this
right
to
implement
this
right.
That's
your
point,
right,
okay,
good
I,
think
you
know
we
need
to
write
some
meeting
minutes
for
this
discussion,
because
I
think
the
the
questions
asked
I.
Other
people
could
have
the
same
questions
right
and
then
we
clarified,
and
then
we
talked
about
this.
So
let
me
write
some
meeting
minutes.
Okay.
So
here
how
monitoring
is
stay?
We
already
see
multiple
events
of
the
knowledge
they've
got
to
okay,
I
think
so.
D
F
So
there's
just
a
point
I'd
like
to
add,
for
this
complicated
thing:
I
mean
someone's
worked
on
AWS
extensively,
even
though
AWS
right
now,
the
step
functions
doesn't
provide
even
support
if
you
go
inside
the
message
boards
and
if
you
look
inside
the
customer
request,
customers
are
requesting
that
we
want
events
to
be
supported.
It's
and
AWS
is
responses
yeah.
We
don't
comment
on
current
things.
Just
you
just
you
just
keep
that
in
perspective.
That
customers
do
want
this
support.
That's
that's
one
thing
being
what
I
was
looking
at
and.
D
I'm
not
surprised
at
all,
but
there's
a
reason
that
area
Bluest
did
not
introduce
it
in
the
first
version,
and
that
is
what
my
point
is
like
service
will
not
solve
everything
in
the
world
and
we
should
not
try
and
boil
the
ocean.
That's
my
biggest
concern
right.
We're
going
to
come
up
with
this
thing.
That's
going
to
be
difficult
for
companies
to
implement
and
we'll
have
a
spec
and
people
not
going
to
use
that
like
I.
Don't
want
to
end
it
at
that
point,
like
that's
my
only
thing.
A
D
A
A
Ch,
a
oh
I
know
yes,
so
now,
let's
go
back
to
maybe
someone
would
help.
If
can
help
right
is
meeting
minutes
are
a
bit.
That
would
be
good,
so
so
this
is
one
work
for
so
we
clarified
this
right
and
then
I
think
you're
agree.
J
D
A
A
A
F
F
J
F
F
A
K
Is
there
an
explicit
requirement
for
them
to
baby
and
these
functions
could
technically
be
HTTP
endpoints
man
event
underneath
the
cloud
events,
definition
yeah,
you
can
deliver
an
event
say
anything
anything
that
implements
the
cloud
events,
transport
inspectors
and
I.
Think
that's
something
again
when
we
think
about
this.
I
think
it's
worth
considering
that
in
terms
of
the
API
is
that
we
define.
How
does
that.
K
F
K
I
Go
ahead,
go
ahead.
Yeah
I
could
see
that
card
events
could
actually
be
what
is
passed
between
each
state.
What
has
brought
in
through
the
events
you
know
like
event,
one
event
to
that
could
actually
be
a
cloud
event
any
anywhere
where
a
function
is
a
vote.
That's
a
cloud
event
and
an
information
between
that's
sent
between
one
state
and
the
next
state
could
be
cloud
event,
so
they
can
be
passed
through
the
workflow.
A
K
I
think
I
think
the
triggering
of
a
function
even
would
potentially
be
a
slight
expansion
on
to
the
HCP.
This
transport
specification,
it's
saral,
can't
be
something
might
be
a
little
bit
more
details
specifically
associated
with
steps.
Also
from
what
I've
seen
from
these
these
potential
workflows
there's
also.
Sometimes,
then
he
eats
for
a
response
coming
from
a
function,
that's
being
invoked
and
being
given
an
event
which
we
don't
have
a
specification
for
there.
K
I
A
A
A
F
This
in
so
yeah
I
can
probably
I
mean,
so
this
is
basically
illustrating
if
how
you
can
implement
a
workflow
for
streaming
video
on
demand,
so
you
basically
put
a
massive
video
file,
MPEG
mp4
whatever,
and
then
you
basically
go
through
a
worker,
so
it
basically
trans
output
is
multiple
streaming.
Media
streaming
format,
see
the
mp4
HLS
or
so
again
going
through
the
workflow.
Once
the
instance
starts,
if
the
minute,
a
user
uploads
a
video
with
metadata,
it
basically
triggers
either
most
probably
an
objective
and
I
would
assume
it'll
good.
F
This
will
this
will
transition
state
one
to
implement
function?
One
function,
one
will
probably
be
an
injection
function,
so
the
injection
function
was
essentially
it
analyzes
the
video.
Well,
what
is
its
resolution?
1080P
1080i
720p,
blah
blah
blah
it?
Can
it
can
store
that
information
to
database.
It
also
sends
all
this
all
this
information,
the
response
of
the
function,
one
it
sends
it
to
state
to
the
minute.
It
goes
to
state
two
depending
upon
the
analysis
that
was
done
as
function,
one.
F
It
goes
ahead
and
depending
upon
the
metadata
file,
it
goes
out
and
starts
multiple
transcoding
functions
again.
I
would
assume
that
the
input
will
specify
what
kind
of
stream
formats
you
want,
one,
either
mp4
or
mp4
and
HLS
or
mp4
and
HLS
or
blah
blah
blah
whatever
anyway,
depending
on
that
state,
you
will
basically
go
ahead
and
start
multiple
transcoding
functions
as
soon
as
now.
These
will
be
asynchronous
so
that
because
it
will
take
a
long
time
so
the
functions
have
started.
F
You
now
go
you
story
and
you
basically
wait
in
state
3
as
each
and
every
as
let's
say
at
some
point
in
time.
The
mp4
transcoding
is
done.
Event
3
will
come
when
even
three
comes.
It
will
basically
look
at
it.
So
you
see
if
it's
complete
and
basically
update
the
database
and
then
a
function
3
will
copy
the
the
file
either
to
an
output,
storage
or
whatever,
and
then
again
go
to
the
next
state,
which
says
whether
all
events
are
completed.
F
If
not,
it
goes
waits
for
even
4
and
5
and
basically
the
same
thing
happens
and
then
finally,
the
workflow
ends.
So
at
the
end
of
the
input
of
the
workflow,
you
have
submitted
one
single
massive
video
file.
The
output
is
depending
upon
what
kind
of
streaming
formats
you
want.
The
output
is
those
particular
screaming
for
a
nicely
arranged
on
the
output
storage.
A
Yeah
I
think
you
know
this
later.
You
know
it
can
always
put
in
comments
so,
but
I
think
you
know
so
far.
It
was
a
point
of
view.
You
know
the
user
will
specify
such
a
workflow
and
then
back
and
we'll
take
this
workflow
and
then
to
implement
and
to
see
how
to
manage
all
these
service
functions
to
instantiate
service
functions,
to
support
this
right
and
also
use
what
role
to
arbitrate
on
this
service
functions.
J
C
A
F
A
J
A
Other
people
draw
me
if
you
want
to
put
your
name
like
you
know:
cha-cha-cha-cha
syrup,
right,
yeah,
okay,
so
I
think
you
know
we
also
derived
some.
We
can
see
I
think
we
want
to
summarize
here
or
need
to
define
this
and
also
I.
Think
you
know
I.
Think
we
agree.
Do
you
agree
that
you
know
we
need
a
state
in
a
state?
A
F
Are
you
saying
that's
what
needs
to
be
in
the
standard
or
that's
just
something
for
them,
for
this
particular
workflow
I
think
what
Bryan
is
saying
is
we
need
to
standardize
the
events
the
way
they
we
pass.
The
events
between
the
states
and
the
response
of
the
functions,
I'm,
not
sure
if
we
want
to
I,
mean
and
Bryan
can
basically
add
whether
you
also
mean
passing
information
between
the
states.
Is
that
part
of
this?
This
workgroup
that
we
are
going
to
do
yeah.
K
It's
great
great
question
I
may
not
buy
my
perspective.
Is
that
again
we're
here
to
try
to
find
I'm
a
specification
that
our
systems
can
adhere
to
in
order
to
be
able
to
participate
in
kind
of
a
distributed?
Workflow.
So
I
think
that,
in
terms
of
what
we
could
potentially
try
to
delivery
here
would
be
things
along
the
lines
of
an
API
specification
for
delivery
of
events.
A
A
A
K
Yeah,
so
that's
some
summarizes
what
I
had
just
mentioned
again:
I'm,
not
saying
that
we
should
you
go.
Do
all
these
but
I'm,
saying
that
these
are
some
scenarios
that
we
could
potentially
think
about
it
in
terms
of
potentially
the
finding
that's
directly
associated
with
this
potential
workflow
engine
work.
A
So
I
think
what
wife's
I'm
agreeing
and
some
parole
somehow
black.
It's.
K
A
A
So
I
think,
okay,
okay,
good,
so
now,
I
think
we
only
have
like
eight
minutes.
Let
me
quickly
go
so
the
next
Prudential
is
this
offers
I
think
this
is
talk
about
how
we
can
probably
support
it.
Let
me
see
whether
I
can
share
I
think
actually
in
this
document,
I
think
I
already
put
in
something
which,
like
the
workflow,
that
how
we
define
something-
it's
not
really
it's
still
in
draft
state,
but
I
think
you
know
one
way
to
do
it.
A
Probably
we
can
change
these
in
all
this
changes.
You
know
to
action
to
function
mode,
to
make
it
more
clear
and
then
these
are
the
functions.
The
real
functions,
so
function
mode
is
Right.
Synchronous,
asynchronous
I,
think
you
know
most
fresh
a
is
like
you
know,
it's
a
one
event
or
two
event
trigger
eight.
So
this
is
that
this
state
and
then
they
will
be
I.
Think
here
there
are
some.
A
You
know
on
matching
this
there's
a
time
out
here,
there's
a
results:
they
match
what
we're
do
and
then
you
know
and
some
retry
mechanism
and
what's
the
next
date
and
then
there's
another
state
with
operation
state
which
doesn't
need
any
event,
checker
I,
think
a
while
the
use
case
this
is
to
address
the
other.
This
use
case,
for
example,
I,
think
so
in
this
state,
there's
no
event
trigger
you
just
do
the
sum
function,
okay
or
in
in
this
state.
You
do
not
any
event
trigger.
A
So
there
are
several
state
states,
different
states
to
model
different
I
mean
different
steps
and
then
there's
a
switch
state
which
I
think
is
a
branching
out
state.
The
pannier
you
match
what
value,
and
then
you
comparison,
how
you
compare
it
and
then
you
go
to
the
next
state.
I
think
this
I
dragged
the
switch
state
address.
You
know
some
use
case
like
this.
This
is
switch
state
right,
you
go
to
different
state
or
let
me
see
whether
there
are
other
yeah
here.
Also
as
neurons.
A
You
branch
out
in
the
state
diagram
lie
here,
branch
out
and
then
it's
like
a
switch
state,
so
you
go
to
different
next
state,
so
I
think
you
know
this.
One
I
will
not
go
into
detail,
but
we
can
take
a
look
at
this
and
then
to
see
whether
this
makes
sense.
Oh
I
see
some
comments
already,
so
maybe
I
think
I
would
like
to
use
last
few
minutes
to
go
through
the
comments
before
that.
We
need
to
you
know
different
presentation
and
the
on
the
solution.
A
C
A
A
C
A
A
A
A
The
users,
for
you
know,
specify
the
workflow.
It's
not
it's
really
not
really
on
topic
and
should
implement
it,
because
we
cannot
define
us
standard
away
for
the
background.
Indentation
loss
yeah
will
be
left
out
for
I
mean
different
implementation
like
and
different
plug-in
to
do
it
right,
but
we
can
discuss
that.
That's
no
problem
but
I
think
the,
though,
is
to
for
the
end
users
specification
and
how
we
can
provide
specification
for
the
front
and
user
to
specify
the
workflow
okay,
and
so,
if
you
are
fine
with
that,
that's
good.
A
D
D
A
D
A
Because
we
need
to
have
that
okay,
I'd
start
state.
This
state
takes
input
as
a
new
trustee
state
of
them.
Okay,
so
for
this
one
yeah
I
think
we
can
discuss
this.
You
know
whether
we
won't
have
a
start
state
or
the
operational
state,
operation,
state
or
events.
They
could
be
used
as
a
start
state
to
pass
the
whatever
input
information
on
now.
Here
are
you
there.
A
Yeah
yeah
I
think
so
so
this
is.
We
can
discuss
later
because
I'm
thinking,
okay,
if
the
first,
if
the
state
machine
or
the
workflow,
is
triggered
by
an
event.
If
the
event
has
not
come.
If
we
have
a
start
state,
then
that
means
we
have
to
start
it.
How
is
started
since
we
do
not
want
to
waste
resources
and
the
you
know,
I'm
starting
the
workflow
before
the
event
arrives.
A
B
A
I
We
can
approach
this
two
ways:
either
we
can
have
an
explicit
start
state
or
we
can
have
a
field
within
you
know
within
each
state
that
could
be
marked
as
a
boolean
within
each
state.
To
say
this
is
the
start
state,
so
it
could
be
done
other
way,
and
if
we
do
the
second
approach,
then
any
state
an
event
state
and
operation
stay
to
switch
state.
Any
one
of
these
states
could
be
marked
as
the
as
the
start
state.