►
From YouTube: CNCF Serverless WG Workflow Meeting - 2018-07-03
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
B
A
Good,
so
it's
okay
thanks!
Everyone
for
joining
this
meeting.
I
know
it's
a
for
us
people.
This
is
the
day
before
the
holiday.
It's
good
I
would
like
to
post
the
link
of
this
sub
race,
this
one.
No,
not
this
one,
a
function
craft.
This
work
flow
language,
pink.
Let
me
post
that
today,
there
okay,
so
that
maybe
I
post
it
here.
C
A
Good
good
I
think
he
know
so
he
seems
this
is
the
first
meeting.
It's
open
discussion,
okay,
so
this
is
what
I
put
into
the
agenda.
Like
you
know,
I'm
thinking
of
you
know,
we
should
define
some
use
cases
and
then
we
I
think
another
very
important
work
item
missed.
We
define
the
scope
of
the
service
work
flow
and
then
we
can
define
the
ghost
of
this.
Also,
the
ghost
of
the
subgroup
right.
What
is
output
and
then
we
can
type
into
the
detail
of
the
you
know
the.
A
A
Maybe
first
I
know
Kay:
let's
go
to
this
document
I
so
in
this
document
have
not
any
use
cases
yet,
but
we
I
think
we
can
start.
You
know
for
the
use
cases
so
what's
also
sort
of
other
people,
any
suggestion.
Yeah.
D
Hi
this
is
Tim
Bray
from
AWS.
Some
some
use
cases
would
be
handy,
a
very,
very,
very
useful,
I
think
in
order
you
know
to
qualify
what
the
effort
is
trying
to
achieve
here.
Also,
I
noticed
out
there
in
the
world
of
workflows
there
there
are
sort
of
generally
speaking,
two
approaches.
There's
the
state
machine,
specific
approach
which
you
know.
D
What's
your
sure
draft
seems
to
be
taking
and
there's
a
dependency
graph
approach,
which
is
quite
a
different
flavor,
which
is
what,
for
example,
Apache
airflow
uses
which
treats
a
workflow
or
more
or
less
like
a
make
file
right.
You
say:
here's
what
I
need
to
do
that
I
need
these
dependencies,
those
have
those
dependencies
and
then
the
workflow
system
works
through
them.
It's
not
instantly
obvious,
which
sorry,
it
seems
clear
to
me
that
neither
is
universally
the
best
solution,
but
they
are
well
suited
for
different
kinds
of
use
cases
right
at
the
moment.
D
Airflow
is
getting
terrific
traction
out
there
in
the
ML
community
who
have
to
do
you
know
ml
people
have
to
do
a
tremendous,
not
a
file
shuffling
and
processing
and
QA
raising,
and
so
on.
So
I
would
think
that
you
know
look
at
the
survey
of
the
current
state
of
the
art,
along
with
air
flow,
there's
Luigi,
which
is
another.
You
know
popular
open
source.
D
You
know,
generously
licensed
workflow
system
and
and
there's
a
step
functions,
which
is
the
one
thing
I
work
on
at
AWS,
so
so
yeah
I
would
think
it
might
be
interesting
to
you
know,
contrast
what's
out
there
in
the
field
and
use
that
to
to
figure
out
what
you
know
unique
purpose.
This
effort
is
purposes.
Obviously
this
effort
is
trying
to
achieve
yeah.
A
Yeah
I
think
you
know
I
think
that
though
okay,
those
comes
to
the
ghost
of
the
subgroup
right,
which
is
a
purpose
way,
I
mean
we
work
on
this
right.
So
Mike
a
case.
We
would
like
to
define
I,
wouldn't
say
it's
a
standard,
but
it's
a
it's
a
consistent
way
for
the
user
to
specify
its
the
workflow
on
the
application
workflow
requirement,
so
that
no
matter
which
somebody's
platform,
the
user
is
you
know,
is
using.
It
can
be
portable
across
different
platforms.
E
Yeah
this
Brian
from
surplus
yeah
I
would
agree
with
that.
I
would
also
say
that
one
potential
interesting
angle
to
that
might
be
the
ability
to
be
able
to
break
up
a
workflow
in
such
a
way
where
parts
of
it
could
be
spread
to
different
assistants
and
pending
upon
you
know.
If
the
workload
reaches
across
multiple
clouds.
Sometimes
it
can
be
beneficial
to
have
a
portion
of
the
workflow,
much
closer
to
the
pieces
that
it's
using
before
it
goes
back
to
orchestrate
with
the
rest
of
it.
It's
just
something
to
kind
of
consider.
There.
A
A
I
think
you
know
that's
a
making
right
so
with
a
state
machine
or
whatever
mechanism
right.
You
know.
The
state
machine
can
also
do
that.
I
think
dependency
graph.
So
we
can
discuss
that
so
I
think
Ronnie
would
like
also
to
specific
to
either
work
say.
You
know
the
workflow
split
up
across
different
multiple
crops,
how
we
do
that
right?
Yes,
that's
right!
Okay,
not
just
in
addition
to
okay.
A
A
A
Okay
with
this,
so
okay,
so
I
think
you
know.
Maybe
the
first
step
is,
you
know
we
add
some
use
cases
first
to
this
document,
not
here
to
this
document
already
a
dissection
use
cases.
So
anyone
would
like
to
add
this,
and
people
would
like
to
sign
up
for
this.
I
can
write
some
add
some.
How
about
team?
Would
you
like
to
awesome
a.
D
A
So
use
cases
now,
let's
see
okay,
so
the
scope
of
the
surveys
up
workflow,
which
you
know
document
here.
This
is
kind
of
not
this
here.
This
is
again.
This
is
kind
of
like
a
scope
I
can
put
into
this.
As
you
know,
anyone
would
like
to
add
I
mean
any
comment
on
this
I
see
some
basically
should
be
out
of
scope
for
workflows,
which
one
are
you
refer
to,
where
the.
A
Actually,
here
should
be,
you
know
actually
in
the
world
application
workflow.
So
so
that's
why?
Okay
for
the
in
the
event
club
events,
we
define
some
may
for
some
property
values,
some
property
or
we
could
quit
labels
right,
but
how
they
are
used.
I
think
they
know
they
should
be
different
here.
It's
a
workflow
that
you
know
which
involves
multiple
events.
That's
going
to
be
defined
here,
it's
going
to
be
different
here,
like
which
label.
In
that
event,
poverty
should
be
used
to
correlate.
You
know
all
the
events.
C
A
G
I,
don't
think
we
should
pull
that
into
workflow,
so
I
think
there's
a
bigger
question
here.
Sorry
guys,
I
joined
a
few
minutes
late
I
think
there
is
a
concept
of
workflow
where
something
triggers
a
workflow
which
leads
to
different
steps
and
different
decision
points
and
whatnot.
But
right
now,
in
this
write
up
we're
combining
a
lot
of
things
which
I
feel
is
gonna,
make
it
really
difficult
for
us
to
actually
make
progress.
So
the
two
things
which
I,
like
particularly
think
we
should
pull
out
of
this
one.
A
So
maybe
I
think
I
know
I.
Think
I
understand
your
key
concerns.
This
will
make
the
workflow
complicated
right.
I
think
you
know
how
about
we
wait
until
the
use
case
right,
yeah
I
can
put
in
a
use
case
for
that.
So
you
can
see
why
we
need
this.
Okay
and
also
I.
Think
your
other
comment
is
once
you
know.
We
put
some
use
case.
You
can
see.
Okay,.
G
C
A
A
So
what
kind
of
label
to
use
to
carry
those
two
events,
because
there
could
be
multiple
instances,
each
IVA
each
of
the
two
events.
So
that's
why
we
need
to
in
the
workflow
definition
we
need
to
have
a
place
for
the
user
to
specify
which
label
should
be
used
to
correlate
those
event.
Instances
to
the
same
workflow
instance.
G
J
C
C
A
C
A
G
The
yeah,
the
second
thing,
I,
had
around
kind
of
scope
and
what
we
should
put
in
here
not
right
now,
Kathy
your
document
talks
about
different
step
of
the
workflow
being
blocked
on
receiving
new
events.
Like
that's
another
thing,
I
feel
is
like.
We
should
think
if
we
really
want
that
in
scope
or
not,
but
I'm
concerned
about
that.
G
So
maybe
if
you
scroll
down
to
your
diagram
below
right,
I
have
a
comment:
okay,
where
you
have
like
that
one
happening
and
after
that
event
one
end
to
happen
which
needs
to
function
one,
but
what,
if
even
one
end
to
happen
while
we
run
function,
step
4,
like
I,
feel
with
this
kind
of
combining
steps
and
function,
executions
and
decisions
and
new
events
since
I'm
not
able
to
wrap
my
head
around
it.
Okay,.
A
Let
me
try
to
clarify
this,
so
this
diagram
shows
how
user,
once
the
workflow
to
to
execute
okay,
so
the
user
from
this
diagram,
what
it
means,
the
user
won't
say:
okay
in
step,
one
you
know
it
needs
to
for
this
application,
you
need
to
wait
for
event,
1
and
event
2
to
happen
and
then
trigger
function.
1,
okay,
yeah,.
H
A
Even
when
he
went
to
does
not
happen,
the
user
does
not
want
to
execute
any
other
function.
Okay,
that's
what
the
use
of
Wow,
okay.
Of
course
the
user
can
say.
Oh
it's
just
an
example.
The
user
comes
a
spacer
in
step,
1
I,
just
seq
function,
1
without
any
events,
just
like
in
step,
2,
there's
no
event
trigger
the
user,
just
say
Oh
once
you
go
to
the
step.
2
just
execute
this
function
without
waiting
for
any
event.
So
this
or
this
or
not
this
just
example,
I
miss
tire.
G
A
That's
again
goes
back
to
the
use
case
yeah
for
that
case,
if
you
just
see
the
first
step,
the
workflow
is
event
trigger,
but
in
the
media's
and
do
not
need
event
trigger
I
think
we
are
restricting
to
restricting.
You
know
very
treat
you
to
some
use
case.
We
cannot
support.
You
know
some
use
cases,
that's
why
let's
see
in
some
case
a
for
example.
That
just
give
me
an
example
like
in
our
travel
travel
approval,
application
right.
You
first
use
event
this
okay,
someone's
making
travel,
requests
right.
A
That's
why
you
bet
so
you
do
some
validation
or
whatever
right
and
then
later
you
want
to
say:
okay,
okay,
if
it's
approved,
then
you
want
to
receive
approval
event
from
some
another
event.
It's
a
proven.
It's
not
travel
request
event
and
then
later
you
could
also
involve
some.
You
know
ticket
once
approved,
you
are
going
to
shop
around
for
tickets
right.
So
then
the
you
need
to
receive
another
event
is
about
ticket
price
for
different
airlines.
So
just
for
us
tribal
I'd
say
our
travel
application
system,
it's
not
a
complicated
system.
J
I
mean
this
has
a
distinct
advantage
in
that
you're
able
to
coordinate.
You
know,
events
from
multiple
different
sources
that
are
required
at
different
times
within
a
single
work
flow
I
mean.
If
you
don't
do
that,
and
you
have
to
start
up
different
workflows.
Then
you
have
the
overall
problem
still
managing
that
multiple
workflows,
you
know
bringing
together
into
a
single
workflow.
With
these
you
know,
steps
is
a
distinct
advantage
here.
Yeah.
G
J
I
mean
essentially
that's,
you
know,
essentially
no
different
from
you
know.
Looking
at
a
simple
faz
function,
where
you,
you
know,
you're
a
receiving
event,
you
you
have
to
set
up
the
the
mapping.
You
know
the
association
between
the
event
and
the
function
that
this
would
be
done
in
a
similar
fashion.
G
A
Right
yeah,
so
look
inside
the
workflow
right.
There
are
many
steps,
each
step
it
just
like
you
know.
It's
no
difference
from
you
know
a
single,
a
single
like
you
know,
event
trigger
a
function
right.
The
event
could
come
from
different
sources.
It
could
be
a
storage
event.
It
could
be
a
messaging
event.
It
could
be,
you
know,
a
straining,
even
yeah,
any
kind
of
event.
It
just
say
you
know
you
call.
We
saw
workflow,
you
coordinate
all
these
stats
together.
They
thought
that's
what
application
really
involve.
G
G
In
my
mind,
I
kind
of
like
think
those
two
differently,
I
think
I'm
thinking
more
of
orchestrating
and
chaining
a
lot
of
functions
rather
than
a
traditional
kind
of
workflow
pipeline,
in
my
mind
and
kind
of
if
we
take
in
these
use
cases
of
things
being
blocked
on
you
and
how
long
are
the
blocks?
Well,
we
are
the
events
coming
from
like
it
does
complicate
our
whole
whole
system
quite
a
bit,
but
as
I
said
right,
if
we
have
use
cases
for
the
well,
then
I
guess
we
should
so
I.
G
A
A
Okay,
I
think
we
can,
let's
document
the
use
case.
I
think
I
think
it's
very
beneficial,
because
if
we
just
if
we
say
okay,
just
a
series
of
functions
without
any,
you
know
in
the
we
do
not.
You
know
allow
in
well
in
the
middle
of
the
steps
we
do
not
allow
the
event
to
trigger
I
think
we
are
restricting
ourselves
to
where
I
should
why
some
use
cases.
I
A
E
Kathy
something
that
might
be
useful
as
part
of
the
this
group
would
be
helping
to
tie
this
into
the
cloud
event
specification
itself,
so
that
we
can
understand.
You
have,
for
instance,
how
they
transport
binding,
which
trigger
the
workflow
or,
in
this
particular
case,
because
the
fact
that
you
have
both
functions
and
function
response
as
well
as
events
being
delivered
to
a
function.
E
It
be
pre-cleared
that
there
need
to
be
some
consistency
around
how
to
be
able
to
deal
with
responses,
as
well
as
what
the
that
kind
of
event
delivery
envelope
is
going
to
look
like
so
anyway.
It's
just
just
call
you
out
that
I
think
there's
some
kind
of
lower
level
details
here,
that
we
want
to
make
sure
that
we
can
connect
the
dots
between
what
we've
been
working
on
and
in
the
system.
Okay,.
A
So
you're
talking
about,
we
would
like
to
talk
about
how
the
function
result
we'll
be
well
behind
or
something
like
that
right,
yeah,
exactly
I'm
sure
result
yeah,
that's
we
will
go
yeah
when
we
really
dive
into
detail
of
defining
or
this
yeah
we're
going
to
go
to
there
right,
but
yeah.
That's
a
good
comment.
A
C
Don't
we
have
to
think
of
how
are
you
going
to
or
whether
we
have
to
persist
the
state
of
the
flow
in
certain
stages,
because
I
now
I
think
we
are
talking
about
long-running
workflows
right
because
we
are
receiving
in
it's
in
the
middle
and
so
on?
So
there
can
be
cases
where
the
runtime
a
crash
between
overflow
and
in
such
situations
we
may
need
to
versus
the
state
or
checkpoint
the
web
flow
and
have
that
literary
started
later
so
do
we.
E
C
E
C
Maybe
one
thing
we
need
to
consider:
I'm,
not
sure
that
we
have
to
consider
is:
do
we
need
to
define
the
points
the
Vectra
needs
to
be
persisted,
like
usually
in
a
traditional
cross.
We
usually
persist
after
receiving
receiving
a
message,
and
so
on
so
do
we
have
to
define
respect
that
any
implemented
here
to
persist
away
from
this
certain
stages.
A
A
G
I
It
seems
like
you
know
whether
we're
gonna
have
to
process
state
depends
on
how
it's
used
to
model
this
right.
Cuz,
you
look
at
Kathy's
graph
there,
the
way
she's
laid
it
out.
It
definitely
implies
some
sort
of
state.
You
could
very
easily
rewrite
this
graph
to
make
it
look
like
every
step
is
a
completely
independent
function.
C
I
G
Like
there
is
a
concert
or
workflow,
but
there's
also
a
combination
of
like
aggregation
of
let's
say,
function
and
application,
so
they're
two
different
things
like
workflow
should
really
handle
things
that
are
kind
of
dependent
on
actual
happening
versus
yeah
I
have
five,
they
could
get
calls
with
different
events
and
I
just
want
to
keep
that
in
mind
right.
If
step,
four
only
happens,
and
even
three
comes
true
like
can,
can
that
be
sewn
function
doesn't
need
to
mean
overflow,
maybe
does.
But
let's
think
through
that
I.
A
Think
we
put
all
this
function
and
application,
which
involves
these
events,
and
these
functions
together
as
a
workflow
has
advantage
of
you
know
you
can
orchestrate
them,
and
you
know
together
and
then
pass
the
information
together
pass
the
information
between
them.
We
can
define
all
this
in.
You
know
in
the
workflow,
okay.
H
A
I
I
A
I
A
Event
is
eternal
event,
so
it
only
one.
So
when
this
event
three
could
happen,
okay
earlier
right,
any
event
could
happen
anytime
during
this
step
right,
but
only
when
the
step
four,
when
you
reach
the
step
four,
the
user
said
only
when
you
reach
step
four,
and
you
know
that
event
will
take
effect.
To
that
event,
three
will
take
effect
and
trigger
function.
Five,
so.
I
A
A
Okay,
so
let
me
clarify
this:
okay
I
think
you
know
from
the
users,
so
I
think
the
workflow
we
want,
if
defined
here,
is
the
workflow
that
user
specify
its
desired
work
flow,
behavior,
okay,
it's
not
like
how
the
system
or
the
service
platform
should
support
this
support.
This
I
think
that
the
supreme
is
two
so
one
so
I,
I'm
I,
go
of
what
I'm
thinking
here
is.
We
need
to,
you
know,
provide
a
mechanism
for
the
user
to
define
what
he
or
she
wants.
Okay,
Oh
somebody's
perform
is
not
to
support.
A
This
is
out
the
workflow
I.
Think
that's
a
separate
thing.
I
think
you
are
right
this
the
back
end.
You
know
service
platform
really
need
to
consider
how
we
should
support
high.
You
know
issue
support.
It
should
support
it
right
for
some
if
the
event
comes
early,
how
he's
reporting
how
the
platform
goes
here.
B
A
Users
point
of
view:
the
user
does
not
care
how
you're
going
to
support
it,
the
user
doesn't
care,
say,
okay,
the
event
comes
early
comes
late
or
whatever
right.
What
the
user
space
right
adjusts?
Okay,
they
just
it.
What
the
user
just
want
is
when
you
reach
the
step
for
that
which
means
function,
one
has
completed
and
then
the
result
is
function,
result
one
and
then
function
two
has
completed
and
the
only
one
all
this
happened.
A
I
want
function
file
to
be
to
be
triggered
when
you
meant
three
cups,
that's
what
the
user
was
right.
Yeah.
G
Yeah
but
but
the
user
cares
if
the
result
ends
up
being
different
right,
so
I
think
the
specification
does
need
to
take
care
of
like
I
our
goal
with
all
these
specifications
that
we
should
be
able
to
take
our
flows
from
one
provider
to
another.
Now,
if
one
provider
is
dropping
even
three
and
the
other
is
not,
that
is
having
a
big
impact
on
the
final
result
of
the
workflow,
so
the
user
does
care.
Okay,.
A
G
A
J
F
A
I
think
that
it's
a
cute,
oh
thank
you,
I,
think
that's
like
an
invitation.
Right,
I
think
you
know
for
the
you
from
the
users
point
of
view,
so
how
you
are
going
to
say
the
user.
Why
does
a
user
need
to
care
say?
Oh
you
are
you
implementing
this
using
a
your
curator
or
you're,
not
curate
or
you
you,
you
throw
away
the
user
just
say:
okay,
this
is
what
I
want
I
want
when
the
event
three
happens
in
step,
four
I
seek
your
function,
5
ID!
Why
does
the
user
need
to
worry?
G
A
G
So
then
we
need
to
define
what
if
it
came
two
years
earlier,
like
we
had
to
define
some
of
those
things
in
that.
That
is
how
Mike,
when
I,
was
thinking
over
this
last
night.
This
this
amount
of
complexity
is
what
actually
was
making
me
feel
like.
We
should
keep
it
simple
and
keep
the
events
out,
but
if
this
group,
we
need
to
take
that
in
I'm
happy
to
go
that
route,
but
we
need
to
define
those
things.
Then
we
need
to
define
that
certification.
Okay,.
A
G
But
that's
not
that's
not
good
enough
right
like
how
much
early
like
what.
If
even
three
happened.
Six
months
earlier
and
my
workflow
started
now
like
it's
somewhere,
somebody
expecting
now
expected
to
keep
like
that.
Even
three
four
six
months,
I'm,
assuming
not
so
I,
think
we
will
have
to
define
those
things.
If
we
go
down
this
model.
I
E
Little
piece
here
might
be
again:
if
we're,
if
we're
trying
to
define
how
steps
actually
tap
into
and
wait
for,
that's
then
part
of
that
configuration
could
be
actually
responsible
for
configuring.
You
know.
Is
it
listening
at
the
point
of
time
that
it
reaches
the
step?
Is
it
pulling
from
something
that
has
a
you
know,
an
event
log
and
it's
just
looking
for
the
first
event
of
this
nature.
I
Agreed-
and
it's
interesting
to
me
is
when,
when
you
look
at
it
as
an
event,
it
gets
sent
from
step
two
to
step
four.
That's
when
I
stopped
looking
at
this
as
a
grandiose
workflow
thing,
even
though
we
may
have
to
look
at
it
more
as
individual
functions
where
there
may
be
multiple
events
coming
into
each
one,
yeah.
E
A
A
Good
so
let's
see
any
other
I
see
what's
the
time.
Okay,.
C
I
Go
ahead,
you
can,
sir,
the
next
bullet
I'm
finishing
up.
Okay,.
C
A
H
C
G
A
I
A
Babe,
if
you
say,
is
a
bring
break
it
into
a
set
up
in
the
independent
steps.
If
there
are
multiple
steps,
then
yes,
it
still
workflow.
So
that's
fine,
but
if
you
say
just
bring
break
it
up
into
just
one
step,
then
there's
no
workflow,
that's
my
point
break
it
into
like,
for
example,
you
say:
okay
step,
one
step,
two
step.
Three,
these
three
are
one
workflow
and
another.
Is
you
know
a
step?
Four
or
you
know
it's
fine.
You
know,
if
you
say
just
single
step,
then
there's
no
workflow
right.
I
What
my
point
is,
you
could
model
step
four
as
part
of
a
larger
workflow
or
you
can
model
step
four
as
step
four
gets
invoked
when
event
three
happens
and
when
an
event
from
Step
two
happens.
Oh
okay,
that's
right!
That's
what
I'm
you
can
model
it
either
way
and
you
get
the
same
result.
It's
just
two
different
ways
to
look
at
your
problem:
decide
which
way
we're
gonna
choose
to
look
at
it.
Oh
okay,.
A
Yeah,
that's
fine,
actually,
I
would
say
this
is
just
an
example.
If
you
break
in
the
map,
if
the
user
want
to
break
them
up,
that's
fine.
We
just
need
have
a
vehicle.
No
matter,
you
know
what
kind
of
workflow
they
use
I
want
to
write.
We
can
support
it.
Okay,
that's
up
to
the
user.
This
is
just
an
example.
Another
example
could
only
have
you
know
two
steps,
so
I
think
that's
fine.
If
you
mean
that
you
know,
maybe
you
want
Clara
might
actually
be
more
and
also
I'm.
G
Completely
different
questions:
okay,
how
much
had
people
on
this
group
kind
of
looked
at
other
people
who
are
doing
something
similar
in
industry
right
like
we
not?
We
know
the
first
one
while
I
don't
know
kind
of
copy-paste
from
others.
I
don't
want
you
I
want
to
at
least
get
influenced
and
see.
What's
been
working
out
there
and
was
not
working
out
there.
I've
only
looked
at
ASL,
so,
like
I
ended
up
mentioning
that
a
couple
of
times
I,
don't
know
Kathy.
A
A
I
One
of
the
things
we
did,
we
first
started
the
service
working
group
itself
when
we
put
together
that
white
paper
was
basically
talked
about.
What's
currently
out
there
in
the
industry
today
and
so
verna
I
think
you
have
a
very
good
point
there.
Maybe
it
would
make
sense
to
happy
will
give
very
quick
presentations
of
what's
out
there
today,
so
everybody's
on
the
same
page,
about
current
state-of-the-art.
G
A
That's
right,
I
think
it's
a
natural
I,
don't
think
you
know
like
you
know,
the
power
are
not
solved
about
well
so
means
something
on
you
know.
Noah
has
a
never
solved
right,
I
think
we're
trying
to
come
up
with
a
common
model.
That
kind
be
you
know
what
is
a
portable
across
all
different
platforms,
for
example,
on
step
function,
support
similar
functionality,
no
no
Microsoft
Azure,
also
similar
and
yeah.
So.
I
A
C
You
can
also
think
about
how
we
differentiate
function
way
across
from
traditional
work
force
if
you
take
traditional
Electress
such
as
VPN
minute
so
on.
So
what
are
the
differences?
Are
you
going
to
have
in
here
compared
to
them,
but
that
will
make
us
easy
to
understand,
understand
what
we
are
going
to
do
here.
A
I
A
I
A
I
think
you
know
let's
take
presentation
on
the
phone
call
next
week,
so
who
would
like
to
let's
just
decide
who
would
like
to
give
a
presentation.
So
anyone
what
I
to
give
our
presentation
is
there
like
people?
There
would
like
to
give
a
presentation.
I
C
I
C
H
H
I
G
A
A
We
can
get
someone
okay,
maybe
some
someone
can
at
least
name
their
okay.
That's
fine!
That's
good!
So
we
have
I
think
we
have
enough
people
to
do
the
presentation.
So
next,
let's
do
the
presentation
and
then
we
can
add
the
use
case.
I
think
that's
good.
We
have
five
more
minutes.
Any
other
suggestion.
A
So
here
I
have
a
comment,
say
you
say
not
solutions,
Newcomb
problems
that
depends
on
how
we
define
the
new
problems.
You
know
if
it's
just
some
flow
rate
it
easier
right,
because
different
platform
will
address
could
solve.
The
scope
is
different.
B
G
H
A
A
Me
say
right:
okay,
good!
So,
let's
see
okay,
reduce
power
flow,
independent
function,
cause
into
a
second
soso
table,
I.
C
A
I
A
A
B
B
K
A
A
As
far
as
I
know,
you
know
a
double
a
step
function,
use
a
state
machine
way
to
do
it,
I
feel
that
I
feel
still
machine.
It's
more
straightforward
way
to
it,
and
also
allow
is
function.
Graph
is
also
that
way.
I
think
the
logic
apps
is
also
similar
way,
but
anyone
would
like
to
draft.
K
B
G
B
A
You
nice
much
better,
okay,
okay,
good!
Thank
you,
I
think
we're
running
out
of
time.
That's
good!
So
we're
going
to
continue
our
discussion
next
next
week.
Next
Tuesday
welcome
to
I
think
we
welcome
to
do
the
presentation
on
each
I
eat
a
solution.