►
From YouTube: OCB: Event-driven Applications with Kogito Serverless Workflows and Knative Ricardo Zanini (Red Hat)
Description
Benefits of business automation such as increased productivity, cost reduction, and improved visibility and communication are important across architectures and runtime platforms. Often thought of as monolithic, business automation has gained high interest in cloud and container-based architectures. Workflow orchestration and automation are now key pieces in developing serverless applications in multi-cloud environments. Using Kogito, a cloud-native business automation runtime, and CNCF Serverless Workflow Project, a vendor-neutral and portable workflow language, we will show how to get up and running with business automation in the cloud and create highly productive and scalable cloud-native applications on top of Knative infrastructure.
A
All
right,
everybody
welcome
back
to
another
openshift
commons
briefing.
Today
we
have
ricardo,
zanini
who's
from
red
hat
and
a
senior
software
engineer
and
we're
going
to
have
a
topic
that
I
don't
really
know
a
lot
about,
because
I
haven't
heard
a
lot
about
it,
which
is
why
we've
invited
him
here
to
talk
about
event,
driven
applications
using
pagido,
serverless,
workflows
with
nk
native
and
so
k
native
we've
had
a
lot
of
talks
about,
but
is,
I
think,
I'm
pronouncing
it
mashing
up
the
name
wrong,
but
we'll.
A
B
B
I
work
with
the
cogito
actually
project
and
I'm
also
helping
the
cncf
serverless
workflow
project
specification
as
well,
so
we
work
in
the
both
ends
in
the
doing
the
specification
side,
you
know
specif
specifying
the
workflow
dsl
and
also
in
the
implementation
in
the
coaching
engine.
Well,
let's
get
it
started.
Let
me
see
if
I
can
all
right
in
the
gina
today,
I'm
going
to
introduce
you
guys
the
servos
workflow
specification
and
what
we
are
doing
there.
You
know
just
a
brief
introduction
to
the
to
the
project.
B
I
I
will
try
to
not
talk
too
much
about
it,
because
there's
a
lot
of
facilities
that
you,
you
should
take
a
look
in
the
specification
and
figure
yourself
for
all
other
details
and
about
the
implementation
itself
that
we
are
working
on
right
now.
That
is
the
coach,
the
project
that
we
call.
It
is
a
business
application
project
for
you
know
for
the
for
designing,
creating
business
applications.
B
And
after
that
I
will
introduce
a
small
use
case.
You
know
if
for
someone
to
feel
comfortable
they,
this
is
like
a
online
store
or
they're
processing.
So
it
is
super
simple
use
case.
Everyone
is
super
familiar,
I
hope
so
and
we
are
going
to
run
a
super
short
demo
as
well
exemplifying
how
the
the
workflow
is
reacting
from
events
and
what
he
is
doing
on
a
k
native
overall
platform.
B
So
about
the
the
cncf
serverless
workflow
specification,
we
we
say
cncf
because
the
serverless
workflow
project
it
is
a
a
sandbox
project
on
cncf
institution.
So
you
can
go
there
in
the
sandbox
project
and
you
see
the
serverless
workflow
specification
project
in
there
and
we
are
accepting
contributions
and
then
it
is
open
source
patch
to
licensing.
You
can
go
there
and
then
you
know
figure
things
out,
ask
questions
and
then
maybe
introduce
some
new
features
that
you
like
or
intro.
B
If
you're
for
him
to
implement
the
specification
as
well,
we
can
help
we
have
sdks.
We
have
a
lot
of
tools
around
the
specifications
that
can
help
you
in
order
to
understand,
to
implement,
maybe
use
the
specification
in
your
company
as
well.
So
what
it
is,
the
the
service
workflow
specification.
It
is
something
that
we
are
targeting.
It
is
to
create
a
declarative,
workflow
language,
so
based
and
to
target
for
a
specifically
serverless
computing
technology
domain.
B
B
But
within
you
know,
having
this
in
mind
in
the
in
the
in
the
workflow
language
as
well.
This
quote,
I
I
I
brought
from
the
website,
so
you
can
go
there
and
visit
the
website
and
understand
what
it
is
with
more.
You
know
details
about
that.
Why
why
we
start
with
this
no
crazy
project?
Why
why
it
is
important
for
us
well,
first,
that
we
believe
that
workflows
can
capture
and
organize
business
requirements.
B
So
what
it
is
you
can
you
know
instead
of
grab
your
maybe
java,
go
or
python
code
and
bring
to
your
business
analyst
and
expansion,
hey
here's.
What
we
are
doing
this
service
here
is
what
is
going
on
there.
You
know
look
at
this
these
conditionals
here
we
are
doing
this
and
that,
instead
of
that,
you
can
just
bring
the
workflow
to
your
business
to
your
business
person
and
explain
to
them
what
is
happening
there
and
they
can
understand.
B
They
can
even
help
you,
you
know
design
their
workflow
or
they
can
even
create
it
work
for
themselves
and
handle
it
to
you
in
order
to
have
that
run
into
a
runtime.
Maybe
so
that's
one
of
the
the
the
idea
behind
it.
The
specification
also
targets
the
vendor
neutral
platform,
independent
workflow
language.
So
what
this
means
means
that
we
do
not
tie
the
specification
with
a
specific
vendor.
It's
not
coach,
there's
not
anything
like
that.
B
It
is
just
the
specification
anyone
out
there
can
take
this
specification
implements
in
your
runtime
and
have
a
workflow
runtime
running.
You
know,
based
on
the
specification
that
is
platform
dependent
because
we're
not
tied
within
a
specific
technology.
We
do
not
say
hey
the
the
workflow
must
be
implemented
in
java,
for
instance,
this
is
not
the
case,
so
anyone
can
just
bring
the
specification
and
share
and
use
that
as
they
please
in
the
in
their
in
their
implementations.
B
So
imagine
that
having
this
common
way
of
describing
our
workflow,
we
can,
you
know,
potentialize
and
create
creating
some
common
libraries
to
be
shared.
Among
all
the
the
the
the
run.
Time
is
the
implement
the
implementations
itself.
We
can
create
tooling
around
it
influx
infrastructure
around
it
around
all
the
workflow
and
having
all
of
them.
B
You
know
to
have
a
common
way
to
describe
something
and
and
create
something
together.
That's
the
the
the
the
nice
of
the
being
on
open
source
specification
so
like,
like
I
said,
being
vendor
neutral,
we
increase
portability,
productivity
and
learning
curve.
You
don't
have
to
learn
all
of
those
workflow
language
that
is,
that
is
out
there,
because
nowadays,
if
you
go
in
the
it
news,
you
see
that
every
day
every
week
we
have
a
new
workflow
engine
out
there.
B
So,
instead
of
that,
we
are
proposing
this
like
on
a
specification
that
can
be
run
in
lots
of
runtimes
and
those
runtimes
can
be.
You
know
offered
by
to
be
run
on
kubernetes
on
openshift.
You
know,
google
cloud
can
have
a
runtime
for
the
specification
as
well
aws
azure,
whatever
cloud
provided
out
there,
they
can
offer
their
own
workflow
service
based
on
the
specification.
B
B
If
I
go
to
through
this
branch
on
my
workflow
and
we
use
the
cloud
vendor
specification
to
define
these
events
in
their
workflow
definition
file
in
in
the
workflow
definition
itself,
you
can
also
run
and
and
not
run
but
call
external
restful
services-
friends,
for
instance,
using
the
workflow
specification,
and
we
use
the
open
api
to
declare
how
you
can.
You
know
create
those
calls
from
the
workflow
itself.
B
So
when
you,
when
you,
for
instance,
you
you
want
to
call
when
you
you
receive
an
order,
you
want
to
call
an
external
service
to
validate
your
order
to
do
something
else,
and
it
is
a
restful
end
point
you
can.
You
know
express
that
call
using
the
open
api
specification,
so
you
you,
you
bring
the
open
api
interface
into
the
to
the
workflow
when
you
specify
which
function
in
there.
That
is
defined
in
the
open
api
specification
that
you
you
wish
to
call
using
the
workflow
dsl.
B
B
Well,
the
workflow
itself
is
based
on
a
state
machine
diagram.
It
is,
I
say
that
is
based,
because
you
know
we
have
start
and
end
conditions
in
in
our
in
our
workflow.
So
when
you
start
and
you
go
from
stage
to
state,
you
know
in
a
fluent
manner,
so
each
state
is
is
responsible
to
do
something.
It
is
responsible,
for
instance,
to
produce
an
event
or
to
call
an
external
function
or
to
decide
to
split
between
two
brands
or
to
go
to
one
branch
or
to
go
to.
B
The
specification
has
like
those
three
main:
this
is
the
backbone
of
a
workflow.
Let's
say
this
way:
we
have
functions,
events
and,
of
course,
the
control
logic
of
the
work.
The
first
thing
is
the
functions
we
define.
The
functions
is,
for
instance,
a
call
which
will
restful
service
or
a
car
to
a
grfc
api
as
well.
B
So
you
can
define
the
functions,
the
the
the
spec
file
of
the
open
api,
for
instance
the
id
of
the
function
that
you
would
like
to
call
in
in
this
section
of
the
workflow.
In
the
event
section,
you
declare
the
how
you're
going
to
consume
and
how
you're
going
to
produce
the
those
events
within
your
workflow.
B
If
I
stay,
you
know
on
one
or
other
details
well,
every
time
that
we
like
present
the
specification
talk
about
specification
events,
people
ask
about
implementations
so
well,
it
is
nice
to
have
a
specification,
and
it
is
also
have
now
it's
nice
to
have
an
implementation
right,
because
that's
the
point
of
having
a
specification,
you
don't
you
don't
just
create
a
specification
to
be
in
there.
You
can
create
specifications
implemented.
B
So
we
we
took
this
specification
now
talking
about
the
coached
projects.
We
thought
we
took
the
the
specification
say:
hey,
there's
a
petition
here
and
we
can
actually
implement
as
a
specification
and
offer
to
our
users
a
way
of
then
to
declare
their
workflow
using
chase
on
our
emo
files
in
a
declarative
way,
and
also
if
there
are
other
vendors
out
there,
implementing
this
specification,
they
can
migrate
to
kojita
easily.
B
You
know
using
the
same
the
same
thing
that
they
learn
with
this
with
this
dsl
in
other
implementations,
with
kojitsu
as
well.
So
this
is
our
work
in
progress,
so
we
are
in
in
tech
preview.
Actually,
right
now,
you
know
community
community
wise.
Of
course,
there
is
some
limitations
of
the
of
the
implementation
that
we
that
we
also
we
are
working
towards
to
implement,
but
the
basic
things
are
there
and
I'm
going
to
show
you
guys
about
a
little
bit
about
the
code
itself.
B
It
is
I
I
like
to
call
this
like
a
cloud
native
solution.
You
know
it
is
a
project
with
lots
of
components.
So
I'm
calling
like
a
cloud
native
solution
for
you
to
build
business
applications,
so
business
applications
that
you
can
solve
business
problems
and
then
what
I
mean
by
that
it
is
like
we
have
an
engine
with
that
is
capable
to
process
rules
in
a
specific
domain
or
even
the
assault.
B
So
imagine
that
you're,
your
insurance
company
and
you
want
to
define
how
you're
going
to
process
that
that
you
know
super
details,
lots
of
computations
and
calculations
that
it
is
more
or
less
cumbersome
to
have
that.
You
know
in
your
in
your
code
base,
so
you're
externalizing
rules
and
you
have
all
all
of
them
defined
on
those
on
those
rules,
and
you
can
give
to
the
engineer
in
order
to
run
it.
You
have
also.
We
have
also
an
engine
capable
to
run
and
complex
decisions
based
on
the
dmn
standard.
B
We
have,
of
course,
the
serverless
orchestration
feature
that
is
super
brand
new,
something
that
we
are
working
now,
that
is,
the
implementation
of
the
cncf
service
workforce.
In
a
specification
we
also
have
an
agent
capable
to
run
bpmn
based
files,
and
we
offer
some
tools
focused
on
cloud
for
so
far
you
can
bring
everything
all
your
business
applications
that
you
created
with
code
to
the
cloud,
so
we
have
a
specific
tooling
for
that.
B
We
have
like
editors,
since
it
is
a
business
application
driven
project.
It
is,
of
course
we
we
have
editors
for
you
to
design
and
create
your
bpmn
process
for
you
to
create
and
design
your
dmn
decisions
as
well
your
your
rules
and
that
you
can
download
on
a
vs
code
marketplace.
We
have
an
online
editor
as
well.
If
you,
if
you
go
bpmn.new
or
dmn.new,
you
see
our
online
editor
there
and
you
can
start.
You
know,
scratching
your
process
or
your
dmn
right
away.
B
You
can
also
download
from
our
website
the
standalone
editors.
We
are
an
engine
like
I
said,
based
on
drew's
gbpm
and
optic
planner.
It's
you,
of
course,
if
you're
a
long-term
java
developer.
Of
course,
you
should
heard
about
those
during
your
career
like
through
zbpm
they're,
super
famous
yeah
popular.
Let's
say,
let's
correct
the
correct
word:
there's
super
popular
frameworks
out
there,
children
rules
and
process
babies
on
vpn.
B
B
B
Let's
go
to
the
to
the
use
case
straightforward.
It
is
imagine
that
you
have
this
online
store
right
and
after
new
new
orders,
you
create
an
event
in
your
in
your
architecture,
every
new
order.
We
create
a
new
event
and
then
this
event
is
complete,
is
being
consumed
by
this
order.
Approval
service,
so
the
the
services
will
be
some
sorts
of
rules,
and
you
know
some
sort
of
business
requirements.
They
say
if
it's
approved
or
not.
B
So
and
then
you
came
up
with
okay.
So
what
what
about
like?
Creating
a
pre-processing
workflow?
So
when
it
comes
to
new
order
event,
we
are,
we
can.
We
are
able
to.
You
know,
split
this
process
inside.
Like
two
events,
you
can
create
two
events.
After
of
this,
this
workflow
within
this
workflow.
We
create
a
shipping
handling
event
and
a
fraud
evaluation
event.
So
each
component
in
the
architecture
can
listen
to
this
event
and
react
upon
it
and
do
whatever
they
want
with
that.
B
B
Also,
we
finish
with
the
shipping
validation.
We
meet
a
a
new
event,
saying
like
shipping
verified
or
something
like
that
and
after
the
fraud
evaluation
service,
you
know
is
finished.
Like
you
can
say,
hey
this.
This
looks
like
a
fraud
does
not
look
like
looks
like
a
fraud
can
be
anything
and
in
the
end
we
have
our
order
approval
service
again,
and
you
can
correlate
all
those
events
you
know
by
like,
for
instance,
the
order
id
and
say
hey.
B
I
received
the
shipping
approval,
I
received
the
evaluation
approval
and
I
received
this
new
order
event,
so
I
can
correlate
the
three
of
them
and
then
they
can
proceed
doing
whatever
they
want.
So
this
is
a
a
small
excerpt
for
of
a
small
processing
use
case
in
our
example.
So
I
have
like
five
services
running
around.
None
of
them
knows
about
each
other.
B
They
just
listen
about
events,
so
that
can
be
you
know,
a
an
event-driven
architecture
and
even
driven
applications,
they're
just
reacting
upon
events
and
and
meeting
new
events,
and
it
can
add
new
components
in
your
architecture.
So
you
can
you
you
have
this
flexibility
of
creating
things
around
your
architecture,
removing
an
event
adding
another.
So,
for
instance,
tomorrow
you
won't
ship
internationally
anymore,
and
you
just
you
know,
remove
the
international
shipping
validation
service.
B
There's
no
use
anymore
right,
you
can
you,
you
won't
have
to
you,
know,
code,
something
new
or
anything
like
that.
Just
remove
an
event
from
the
from
your
you
just
remove
a
service
from
your
architecture,
and
you
stop
doing
that
thing
or
no.
Well,
I
wish
to
add
some
new
capabilities,
so
I
add
a
new
service
in
order
to
listen
this
event
and
do
whatever
they
want.
B
So
this
is
more
or
less
what
an
event-driven
architecture
can
the
benefits
of
an
event-driven
architecture
can
give
to.
You
know:
async
processing,
this
kind
of
flexibility.
You
know,
composition
and
orchestration
of
events.
That's
why
we
we
we
are
talking
today.
You
know
like
about
the
workflows,
for
instance.
So,
let's
try
to
zoom
in
into
this
first
service,
the
word
pre-processing
workflow.
B
Let's
say
how
it
is
doing
its
thing,
so
I
draw
this
workflow
like
in
order
to
pre-process
my
order,
so
I
receive
disney
word
event
and
I
will
process
the
order.
I
split
into
into
two
parallel
states
saying
I
will
handle
fraud
in
one
state
and
I
will
handle
shipping
in
another
state,
so
I
can
figure
if
I,
which
kind
of
events
I
need
to
you
know
produce
for
my
architecture,
so
this
is
happening
inside
that
processing
workflow
service.
B
So
I
I
broke
the
workflow
into
three
workflows.
I
have
the
main
workflow
the
water
workflow,
and
I
have
one
state
here
that
we
call
the
parlour
state.
You
know
calling
those
two
subfloors,
the
fraud
handling
workflow
the
shipping
handling.
So
let's
take
a
look
at
it.
The
first
part
of
the
workflow
it
is
the
I
call
the
headers.
You
know
the
when
we
we
describe,
we,
we
give
some
information
about
the
workflow,
so
the
name
of
the
workflow,
the
identification
of
the
workflow.
A
B
The
second
part
I
have
the
events
definition
when
I
define
how
I
will
consume
that
event.
So
let's
say
that
in
in
this
particular
use
case,
I
have
the
order
event,
type
cloud
event
type.
So
someone
out
there,
you
know
any
service
out.
There
is
creating
it's
producing
the
this
ordered
event
cloud
event
for
me
and
I'm
and
I'm
capable
of
listening
to
it.
B
So
the
first
state
that
receives
the
receiving
order,
it
is
capable
of
you,
know,
listen
listening
to
this
event,
the
other
event
here
that
we
tie
with
the
name
like
order
event
name.
I
I
have
the
the
the
event
by
his
name.
It
is
the
order
event
here
and
when
I
receive
this
event,
I
say
transition
to
process
order
and
this
state
process
order,
which
I
call
if
I
parallel,
I
will
create
the
branch
fraud
handling
shipping
handling.
B
It
is
maintained
by
by
the
service,
workflow
community
specification
community
and
you
can
go
there
see
if
the
source
code
do
whatever
you
want,
download
it,
and
please
hate
five
in
the
the
plugin
itself-
and
we
have
this
nice
feature
that
is,
you
can
generate
diagram
using
any
workflow
file,
so
it
uses
the
you
know
this
def
simplification
of
the
event
diagram
from
uml.
So
we
have
a
start.
We
receive
the
order,
it
is
an
event
state.
B
We
process
the
order
in
a
parallel
state
and
we
create
two
branches.
So
let's
take
a
look
into
the
first
one,
the
fraud
handling
workflow
same
thing.
I
have
the
name
the,
which
state
that
I
want
to
start
the
version
and
the
events
that
I'm
going
to
produce.
So
I'm
going
to
produce
a
type
event:
orders,
dot,
fraud,
evaluation
and,
let's
take
a
look
into
the
states.
So
we
have
a
data
conditioning
here,
which
is
when
we
we.
We
start
this
workflow.
B
We
analyze
the
data
inside
the
the
the
input
of
the
of
my
workflow
and
we
perform
a
json
path
expression
into
this
into
this
data,
and
if
the
total
of
my
order
is
is
greater
than
one
thousand,
I
would
say
that
we
need
fraud,
verification
if
it
is
under
one
thousand.
I
I
won't
need
fraud,
verification.
Of
course.
This
is
super,
lame
an
example
in
real
use
case.
You
won't
do
things
like
that.
B
B
Of
the
the
customer,
whatever
thing
you
want,
you
know,
and
then
you
can
say
to
the
to
the
workflow:
hey
this,
this
order
looks
like
they
need
to
perform,
is
to
be
validated
the
defraud,
or
something
like
that.
So
for
this
case
for
to
to
simplify
the
conditions,
we
have
this
event
type
switch,
and
I
have
this
conditions
in
here
very
lame,
but
it
is.
B
It
is
super
nice
and
I
inject
into
the
into
my
data
state,
a
new
con,
a
new,
a
new
attribute
to
my
my
workflow.
The
fraud
evaluation
equals
true,
and
then
I
produce
the
event.
Fraud,
evaluation
and
this
event
contains
in
the
data
attributes
everything
that
I
created
here
in
the
workflow.
So
it
goes
with
the
fraud
evaluation
equals
true
and
the
order
information
as
well.
So
anyone
that
is
interested
in
in
the
in
the
orders
that
fraud
evaluation
event
can
do
something
with
it
all
right.
B
B
The
other
workflow
is
the
shipping
handling
workflow
that
is
being
executed
at
the
same
time
as
the
as
the
other
one,
more
or
less
the
same
thing.
We
have
now
two
types
of
events.
We
have
international
shipping
order
event
and
we
have
domestic
shipping
other
events.
So,
depending
on
the
context
of
my
order,
I
will
emit
reproduce
an
event
like
an
international
event:
a
shipping
order
event
or
a
domestic
shipping
event
and
more
or
less
the
same
thing
that
we
did
there.
B
B
So
for
the
mask
shipping,
I'm
going
to
add
a
new
attribute
to
my
to
my
data,
that
is,
shipping
domestic.
Otherwise,
I'm
adding
a
shipping
international
to
my
data
and
I
will
produce
an
international
ship
in
order
and
now
you
produce
a
domestic
shipping
order
again
super
simple,
but
you
can,
you
know,
see
the
the
powerful
work
of
something
so
imagine
that
you
that
you're
talking
with
a
business
person
and
they
can
bring
the
dsl
to
them
and
explain
hey.
This
is
what
is
happening
inside
the
these
microservices.
B
This
is
what
what
which
kind
of
events
that
we
are
creating
there
you're
consuming
and
what
we
are
doing
with
it.
So,
for
instance,
in
a
real
use
case,
you
can
say:
hey,
I'm
calling
this
google
service
and
we
can
receive
this
kind
of
information
and
we
can
process
the
information
as
as
we
pleased
using
the
workflow.
B
Diagram
here,
so
we
have
this:
the
shipping
handling
state,
it
is
a
sweet
state
and
we
go
with,
can
be
a
domestic
shipping
or
can
be
on
international
shipping
as
well
as
you
see.
In
the
end,
we
are
going
to
produce
an
event
being
international
or
domestic
shipping
whatsoever
and
we
are
going
to
win.
B
Well,
that's
what
looks
like
the
event
when
you
when
you,
when
you
see
it
in
this.
In
this
perspective,
and
of
course
this
is
the
when
you
are
designing
and
we
are
creating
your
workflow
when
it
turns
out
to
you,
know,
to
deploy
and
to
into
a
kubernetes
or
on
our
opinion
cluster,
for
instance,
or
in
the
cloud
you
can
use
the
capabilities
of
the
cochito.
B
B
You
know
running
within
the
platform
itself
and,
of
course,
for
this
use
case
specifically
for
this
working
with
events
with
k-native.
We
need
the
the
service
platform.
This
also
works
on
kubernetes,
but
on
kubernetes
you,
you
can
build
within
a
cluster.
You
have
to
build
the
image
yourself
and
then
push
the
image
to
the
cluster
and
the
cluster
operator.
You
take
your
image
and
it
will
do
you
perform
the
same
steps?
B
You
create
the
kubernetes
resources
to
create
the
native
resources
for
you,
and
you
know
for
for
your
service
to
be
connected
with
the
the
canadian
broker.
In
this
case
diane.
I
see
that
we
have
some.
You
know
a
chat
going
on
there.
You
you'd
like
me
to
stop
here
and
or
we
can
answer
the
questions
after
the.
A
B
All
right,
no
problem,
yeah,
I
know
if
I'm
I'm
rushing
or
not.
So
you
tell
me
all
right
when,
once
we
have
the
the
service
deployed
on
openshift,
this
is
more
sorry
about
it.
The
other
technical
details,
but
this
is
how
it
looks
like
from
the
cogito
operator
perspective,
how
we
deploy
the
service
in
there.
So
our
service
will
be
like
an
event
source
or
this
event
source
can
be
any
other
thing.
B
In
this
case
we
have
the
the
serverless
workflow
in
here
and
we
are
listening
to
the
new
ordered
events
coming
from
the
canadian
broker
and
we
consuming
using
canada
eventing
triggers
and
that
triggers
you
know
an
event
for
us
to
listen
to
it.
So
the
art
element
comes
here
into
the
broker
and
we
listen
to
it
and
we
start
our
workflow.
Our
workflow
will
produce
events
to
the
broker
using
sync
bindings,
so
we
produce
events
to
the
candidate
broker
and
any
other
service
out
there.
B
Any
other
you
know
can
be
a
canadian
service
can
be
any
deployable
pod
or
anything
else.
You
know
in
the
in
the
in
the
spectrum
of
the
kind
of
servant
platform
to
be
listening
to
this
event
and
to
react
upon
it,
and
that
this
is
what
we
are
going
to
see
in
this
short
demonstration.
Let
me
see,
I
think
this
is
not.
Let
me
try
to
zoom
that.
B
All
right,
so
I'm
I'm
producing
an
event
to
the
platform
and
can
indeed
the
country
is
u.s.
The
total
value
is
1001
and
is
an
iphone
12
order.
So
I'm
going
to
push
this
event
to
the
platform
and
you
see
what
what
will
happen
in
there
so
in
in
this
terminal.
Here
I
have
three
listeners
of
our
k
native
of
ours,
our
workflow
event
producing
events.
So
in
the
top
most
we
have
the
fraud
evaluation
service.
B
So
we
are
listening
to
the
events
from
the
front
evaluation
service.
We
have
the
I'm
sorry,
the
shipping
international
here
in
the
left
and
the
domestic
shipping
here
in
the
right.
So
us
one
event
comes
to
the
either
through
the
fraud
evaluation
or
to
the
international
or
domestic
shipping
services.
You
will
see
the
the
produced
event
in
here.
B
It
is
like
a
fire
and
forget
type
of
event.
It's
taking
some
time
because
maintenance
connection
is
not
that
good.
So
I
push
the
event
and
we
can
see
that
we
didn't
have
any
pods
and
listening
to
that,
because
those
are
cognitive
services
and
we
receive
a
fraud
evaluation
because
the
the
the
value
is
above
a
thousand
dollars
and
we
received
a
domestic
shipping
because
the
country
that
we
ship
the
our
our
iphone
it
is
within
us.
It
is
a
water
from
the
u.s.
B
B
Yeah,
you
already
saw
those
like
you
could
because
I'm
I'm
I'm
fetching
for
the
pods
of
the
shipping
international
service,
and
you
see
there
is
no
resources
in
there
and
yeah.
I
know
what
is
happening.
I
don't
know
if
I
need
to
refresh
this,
but
whatever-
and
you
see
that
is
this
event
coming
in
here
and
this
event
coming
in
here.
B
So
there
is
some
extensions
and
as
well,
so
we
have
some
information
about
the
the
the
process
itself
and
here
you
can
see
that
the
fraud
evaluation
service
received
the
fraud
evaluation
equals
true
and
the
domestic
shipping
service
received
the
shipping
domestic.
You
know
and
this
shipping
domestically
does
not.
It
is
in
here,
but
the
front
evaluation
is
not
in
here
because
we
we
run
one
after
the
other.
B
Well,
let's
see,
if
yeah
we
can
see
the
deposit
here
and
you
and
because
we
were
talking
canada
will,
you
know,
destroy
the
pods
because
they
are
not
being
used.
So
that's
why
we
are
seeing
terminating
me
here.
So
let's
say
that
we
have,
I
don't
know,
maybe
a
new
order
from
italy
and
that's
above
a
thousand
dollars
as
well.
B
When
I'm
gonna
send
it
quickly
this
time,
because
the
pod
is
already
there,
I'm
I'm
creating
the
ship
international
pod
in
order
to
to
listen
to
this
event
and
react
upon
it
and
the
same
thing,
you
won't
see
fraud
nor
domestic
here,
because
we
entering
that
that
branch
that
we
just
receive
you
know
from
the
international
shipping
so
now
try
to
imagine
this
in
a
real
use
case.
Where
you
you
have.
B
You
know
to
equalize
your
resources,
you
have
to
save
resources
in
order
to
have
you
know
a
more
profit,
a
company.
So
in
this
case
let's
say
that
you
receive,
I
don't
know,
maybe
nine
percent
of
your
orders.
They
are
there,
they
are
domestic,
so
you
don't
have
to
have
like
the
international
shipping
handling.
You
know,
services,
be
you
know
up
there,
all
the
time
you
can
have
the
workflow
to
you
know,
control
all
the
logics
and
can
break
through
into
category
categories.
B
You
can
break
your
domain
into
more
specific
things
and
you
know
be
flexible
enough
to
distribute
your
services
around
your
your
architecture
and
you
won't
have
all
the
you
know
you
what
waste
resources
into
something
that
you
want.
You
know
need
for
some
times,
so
this
is
a
a
a
nice,
a
nice
example
or
a
nice
use
case
for
you
to
maybe
reevaluate
some
of
those
things
that
we
are
doing
because
normally
people
create,
like
oh
huge
microservices.
They
are
doing
a
lot
of
things
and
maybe
sometimes
it
is
nice.
B
I
just
to
break
into
you,
know
specific
parts
and
and
make
them
you
know
run
into
this
fashion
like
I
can
create,
like
lots
of
domestic
orders
or
lots
of
international
orders
and
having
this
part
of
my
system
not
producing
services
on
producing
events,
not
whatsoever,
so
I
can
reduce
my
cost
and
sometimes
that
will
help
a
lot.
Well,
let's
get
back,
there's
some
much
more
things
that
I'd
like
to
discuss.
There
is
no
lots
of
of
detailed
facilities
about
it.
B
I
know
that
was
you
know,
super
quick
and
brief
things.
I
introduced
lots
of
concepts.
You
know
like
the
the
cloud
events,
sorry,
the
the
the
service
workflow
specification,
the
the
project
the
house
is
deployed,
it
can
native
there's
lots
of
things
out
there
and
also
lots
of
resources.
You
can
go
there
in
this
on
our
websites
and
see
what
we
are
doing
and
the
the
use
case
that
we
are
capable
to.
You
know
to
keep
to
help.
You
solve
your
business
problems
so
reach
out
to
me
as
well.
B
I
have
twitter
account.
You
can
send
me
a
dm
message
or
send
an
email
or
reach
out
to
into
github
or
whatever
I'm
up
there.
You
can
see
and
our
I
I'd
like.
I
would
like
also
to
you
know,
to
ask
you
guys
to
take
a
look
in
the
blog
as
well.
We
are
trying
to
update
a
blog
like
twice
a
week
with
new
content
and
to
give
people.
B
You
know
an
understanding
of
what
we
are
doing
in
cogito
and
the
business
applications
in
general
and
how
we
can
you
can
solve
your
business
problems
and,
if
you're
curious
about
the
demonstration
the
example
itself,
you
can
go
into
this
we're
holding
here
and
see
all
the
source
code.
You
see
the
the
workflow.
I
create
some
scripts
in
there
for
you
to
deploy
in
your
kubernetes
instance.
I
have
we
have
the
the
image
already
being
there.
B
You
know
the
docker
file,
sorry
already
in
there,
so
you
can
go
download
the
docker
file
run,
use
the
image
run,
the
the
image
locally.
There's
you
can
play
around
this
demonstration,
whatever
you
want-
and
I
was
I'd
like
to
also
invite
you
to
see
this.
The
the
the
presentation
from
last
year
that
t
homier
and
I
did
siobhan-
is
much
better
than
me
explaining
the
the
cloud
the
servers
growth
specification.
B
Then
there
we
go
through
more
details
about
the
specification
and,
if
you're
curious
about
it,
just
go
in
there
and,
of
course,
the
servers
workflow.io
website.
You
have
all
the
links
that
you
that
you
need
to
know
there,
our
slack
channel
our
main
list,
our
weekly
meeting
and
everything
else
you
see
in
the
resources.
Okay.
Well,
thank
you!
That's
it!
I
don't
know
if
we
have
any
questions.
B
B
The
crystal
operator
as
well
is
coded,
and
we
have
this
support
for
the
native
eventing
platform.
So
we
created
a
specific
native
eventing
resources
for
it.
So
for
the
candidate
venting
part,
that's
that's
why,
but
for
the
canadian
serving
part,
no
can
be
whatever
thing
the
outskirts
can
be.
You
know
regular
deployments,
whatever.
That's
no
particular
reason.
B
Oh
yeah,
of
course,
because
this
is
a
a
java
project,
it's
a
straight
through
maybe
in
java
project
in
our
in
the
in
the
example
itself.
I
have
the
a
redmi
file
here
that
I
explained
how,
let's
see
how
you
can
create
this:
a
serverless
workflow
code
project
from
the
from
scratch
using
is
in
java.
So
you
have
to
know
java
but
yeah,
you
can
add
a
custom
code
and
you
can
call
this
custom
code
using
a
workflow.
We
have
a
specific
in
the
code
implementation.
B
We
have
specific
functions
that
you
can
declare
in
here,
for
you
know
like
the
you
can
give
a
name
and
then
you
can
in
the
metadata
space
we
we
have
a
what
you
call
like
a
service
internal
calling.
So
you
can
you
can
call
it
any
java
being
from
the
workflow
so
yeah
you
can
do
it,
but
from
the
from
the
specification
point
of
view
we
have
the
jq
capabilities.
B
So
you
can.
You
can
like
create
a
function
expression
and
then
you
know
externalize
this.
You
know
we
can
define
here
a
function.
That
is
an
expression
as
a
function
function,
and
you
can,
you
know,
declare
any
if
you're,
if
your
custom
code,
it
is
now
related
to
data
handling
with
the
the
input
you
can
just
create
the
expression
and
in
here
in
the
workflow
itself,
and
that
we
work.
B
A
B
Yeah,
absolutely
let
me
let
me
share.
Let
me
let
me
show
you
the
specification
itself
yeah
you
can.
You
can
call
any
any
any
functions.
You
know
we
have
three
in
the
specification.
We
expect
the
restful
service
invocation
or,
if
see,
service,
invocation
and
also
expressions
like
I
said
before
in
the
restful,
you
can
define
like
a
function
like
this,
let's
say:
send
order
confirmation
and
the
operation
of
this
function.
B
B
B
Will
we
read
this
the
this
this
specification
and
we
will
generate
code
client
code
to
call
this
rest
service,
so
yeah
you
can
call
it.
You
know
a
a
third-party
api
and
do
whatever
you
want
is
within
your
workflow.
So
after
receiving
the
the
the
payload
of
the
the
the
response
of
the
list
paths,
you
can
do
whatever
you
want
in
your
workflow
yeah,
that's
correct.
B
B
Quickly,
oh
we're
on
top
of
the
hour,
but
let
me
let
this
is
the
yeah
here
in
the
events
you
can.
You
declare
the
correlation
in
here
so
in
this
use
case
that
I
that
I
brought
in
the
end
in
the
final
order
process.
So
if
that
process
would
be
like
a
workflow
service
as
well,
because
I
don't
know
what
it
is.
B
It's
just
an
example
that
I
gave,
but
if
it
is
a
workflow
as
well,
you
can
you
can
create
the
correlation
in
here
in
the
in
the
workflow
and
say
the
event
say:
hey
the
the
attribute
name.
It
is
order
id
for
instance,
and
then
you
can
re
when
you
receive
everything
else,
you
would
do
whatever
you
want
in
kojito.
We
don't
have
stateful
yet
for
the
for
the
for
the
service
workflow,
but
we
are
working
on
it.
B
B
Well,
chemo
is,
for
I'd,
say,
integration
most
of
the
time
you
know
implementations
of
integrations
and
we
do
not
target
integrations.
So
we
you
cannot
like
ftp
a
file
or
send
an
email,
or
do
you
know
things
like
that?
It
is
not
what
we
we
are
discussing
here
and,
of
course
you
can
implement
a
pipeline
in
came
okay.
B
B
B
B
B
And
knowledge
based-
and
it
is,
I
believe,
is
based
on.
Of
course,
the
the
founders
can
explain
much
better
than
I,
but
from
this
quote
koji
to
ergoson
from
renee
this
card
is,
you
can
read
the
video
but
yeah
and
the
k
because
kubernetes
you
know
it
is
a
cloud-based
platform.
So
that's
why
that's
called
kojita.
I
don't
know
if
I
answered
your
question.
Hopefully.
A
B
A
B
Well,
like
I
said,
questions
is
a
work
in
progress
of
the
server's
workflow
specification,
so
the
workflow
specifications
going
super
in
the
community.
We
are
creating
great
things
in
their
great
big
companies
are
interested
in
investigation.
This
is
a
very
nice
thing
from
the
community
side.
We
are
about
to
release
1.0
from
in
the
specification.
So
this
is
a
nice
thing.
B
Hopefully
we
see
more
people
trying
to
implementing
it
and
from
college
to
side
we
are
keen
to
implement
everything
that
we,
that
is
there
in
the
specification
to
be
100
percent
compatible
with
the
the
specification
we
are
about
to
to
bring
jq
to
the
engine.
So
you
can,
you
know,
create
jq
expressions
in
your
in
your
workflow,
and
so
you
can,
you
know,
transform
or
you
know,
do
whatever
you
want
with
the
data
within
the
workflow
and,
of
course
state.
B
This
is
a
very
important
thing
that
we
are
we're
looking
for.
You
know
implementing
the
in
the
specific
in
the
in
the
engine
as
well,
as
was,
as
you
know,
error
handling,
compensation
and
all
of
those
workflow
patterns
that
we
don't
have
yet
from
the
workflow.
So
from
the
serverless
workflow
perspective,
but
yeah,
that's
there's,
there's
there's
a
lot
of
work
to
do
in
there
and
from
the
specification
and
the
information
side.
B
B
A
B
A
Release
and
and
and
just
keep
it
keep
us
in
mind,
and
there
were
plenty
of
great
questions
today,
so
thank
you,
everybody
for
tuning
in
and
chris
short
for
producing
in
the
background
there.
So
I'm
really
pleased
to
have
you
here.
Ricardo
definitely
come
back
and
keep
us
posted
and
up
to
date,
and
everybody
join
us
on
the
community
slack
channel.
If
you
have
questions
that
he
didn't
answer
today,
we'll
try
and
get
them
there
all
right.
Well,
thank
you,
everybody
and
again,
ricardo!
Thank
you.