►
From YouTube: wasmCloud Community Meeting - 5 April 2023
Description
Welcome to the wasmCloud community! Tune in live where we discuss the latest developments in the wasmCloud ecosystem, WebAssembly standards, and break out sweet demos.
Agendas for wasmCloud community meetings can be found at: https://wasmcloud.com/community
A
B
All
right
anybody
can
you
confirm
that
you
can
see
my
terminal
window
here
looks
good
to
me,
Kevin,
okay,
so
just
like
last
time,
I
did
a
demo
on
concordance,
which
is
the
name
of
the
event
sourcing
framework
that
we've
that
we
built
there
is
no
UI
I'll
just
run
through
this
stuff
from
the
Turman
window,
but
one
thing
that
I
didn't
demo
last
time
was
replay,
so
hopefully
I'll
be
able
to
demonstrate
that
now.
B
B
B
Let
me
just
make
sure
that
my
streams
are
okay.
Let's
clear
some
of
this
stuff
out.
B
Okay,
so
that
was
an
awful
long
way
to
go
for
me
to
just
say:
there's
nothing
up.
My
sleeve
and
I
have
nothing
set
up
and
running.
So
what
I
have
running
is
the
bank
account
projector,
the
and
the
bank
account
aggregate
and,
like
I,
said,
I'll
submit
a
command
or
a
bunch
of
commands
and
the
event
sourcing
plumbing
will
just
go
through
and
you
know,
handle
the
the
commands
and
emit
the
events
and
the
events
will
produce
state
and
once
I
go
through.
This
I'll
show
some
of
the
code.
B
I
can't
remember
whether
I
showed
the
code
for
the
aggregate
last
time,
so
assuming
everything
is
in
order
all
right.
So
here
I've
submitted
a
bunch
of
commands
and
you
can
see
that
the
new
version
of
this
bank
account
shows.
You
know
that
all
the
all
the
various
transactions
went
through
so.
B
The
event
stream
you'll
see
that
these
are
all
Cloud
events
and
Cloud
event
is
a
specific
standard.
I
think
it's
part
of
the
cncf,
but
basically
it's
just
a
specific
type
of
Json
envelope
around
some
data.
That
has
you
know
the
event
ID
the
event
type,
which
is
the
The
Fairly
important
bit
and
then
the
data
that
came
with
the
event.
So
we
can
see
that
all
these
events
are
there
and
we
can
check
that
the
aggregate
has
state
by
looking
at
the
the
state.
Key
value
bucket
and
I
can
check
that
state.
B
There
we
go
yeah,
so
that's
the
state
of
the
aggregate
not
to
be
confused
with
the
state
of
the
projector
and
if
I
go
into
the
projector
you'll
see
I
can
I
get
the
current
balance
of
the
bank
account,
but
I
also
get
there.
We
go.
I
also
get
The
Ledger,
which
has
the
individual
transactions
that
are
part
of
the
bank
account,
and
so
what
I
wanted
to
show
today
was
replay.
So
let's
say
that
I
have
lost
all
of
my
projections,
so.
B
Delete
my
balance
and
I'll
delete
The
Ledger,
you
know,
oh
no,
what
am
I
going
to
do
everything
is
horrible,
so
what
I
can
actually
do
is
with
Concordance
all
of
the
streams
or
all
of
the
components
that
are
part
of
the
system
are
managed
through
consumers.
So
with
the
consumer,
you
know
that
the
events
consumers,
so
you
can
see
I've
got
a
consumer
for
the
aggregate,
a
consumer
for
the
project
for
the
process
manager
and
another
one
for
the
projector.
B
So
if
I've
just
blown
away,
my
projections
so
now,
if
I
want
to
trigger
a
replay
I,
can
just
delete
the
projection
consumer
and
then
recreate
it
and
see
if
I
actually
have
that
that
specific
command
yeah
here
it
is
so
I'm
going
to
take
the
configuration
data
from
this
consumer
and
save
it
off
into
a
configuration
file.
B
And
next
I'm
going
to
delete
and
what
I'm
copying
from
is
actually
the
concordance
documentation
on
the
cosmonic
website.
So
all
this
stuff
is
there:
if
you
want
it
so
now,
I'm
going
to
make
even
more
bad
things
happen.
Theoretically,
right,
I'm,
just
going
to
delete
this
consumer,
so
I've
deleted
the
consumer
and
I've
deleted
all
of
the
projections.
So
if
I
want
to
start
a
replay,
all
I
have
to
do
is
re-add
the
consumer
back
and
so
now
I
see
the
consumer
I.
Have
this
one
back?
B
What
I'm,
what
I'm
waiting
for
is
the
consumers
have
a
a
poll
timing.
So,
in
short,
what
that
means
is
that
they're
not
actually
they're
not
pulling
every
single
message
in
real
time,
there's
kind
of
an
exponential
back
off
in
there,
and
let
me
see
here
so
now:
you
can
see
Zero
for
unprocessed
messages.
B
That
means
that
the
replay
went
through
so
now
I
can
look
and
there's
my
balance
and
there's
my
ledger
and
everything
rebuilds
itself
within
a
matter
of
seconds
and
well
on
the
service
that
might
seem
like
a
fairly
simple
thing
being
able
to
do.
This
is
actually
one
of
the
the
key
things
that
you
need
to
be
able
to
do
if
you
want
to
run
and
manage
an
Event
Source
system.
So
here
I
just
manually
deleted
the
projection,
but
you
can
imagine
that
you
might
need
to
do
this
kind
of
Replay
or
Disaster
Recovery.
B
If
so,
you
lose
your
projection
database,
but
even
more
common
than
the
disaster
recovery
scenario
is:
let's
say
you
change
the
code
in
your
projector
and
you
redeploy
a
new
version.
What
you
want
to
be
able
to
do
is
then
rerun.
The
entire
set
of
events
through
that
new
projector,
so
that
the
data
that
you're
projecting
has
the
new
shape
and
to
do
that,
you
would
just
go
in
deploy
your
new
projector
delete
and
recreate
the
consumer
and
then
walk
away
and
everything
is
working.
Fine
and
this
all
works
in
distributed
fashion.
B
So
you
know
if
you're
running,
concordance
and
you've
got
the
capability
provider
running
on
multiple
nodes
and
you've
got
your
Aggregates
and
projectors
all
running
multiple
copies
on
multiple
different
hosts.
Everything
still
works
exactly
as
as,
though
as
I
demoed
it
here
so
like
I,
said:
there's
no,
no
fancy
UI,
but
hopefully
you
can
extrapolate
from
here.
How
easy
it
is
to
build
some
of
these
applications
and
I.
B
Think
I
showed
this
last
time,
but
we
just
want
to
show
that
the
aggregate
here
you
just
implement
the
aggregate
service
trait
and
so
with
the
aggregate
service
trait
there
there
is
the
handle
command
Handler,
and
in
here
we
just
we
handle
the
commands
and
in
response
to
the
individual
commands,
we
emit
events
and
then
the
aggregate
itself
modifies
its
internal
state
by
applying
those
events.
B
So
it's
a
subtle
distinction
but
important
that
the
command
the
aggregate
doesn't
modify
its
own
State
when
processing
commands
it
waits
for
the
events
for
it
to
be
able
to
modify
its
own
State,
and
part
of
that
has
to
do
with
being
able
to
take
take
part
in
in
replay.
But
you
know,
there's
a
number
of
other
long-winded
explanations.
I
can
go
into
if
you
want,
but
for
now
this
is
pretty
much.
B
What
I
wanted
to
show
is
just
how
easy
it
is
to
do
replay
and
how,
in
Gordon's
pretty
much
takes
care
of
all
of
the
so-called
hard
parts
of
managing
an
Event
Source
system.
A
A
If
you
visit
cosmotic.com
docs
and
take
a
look,
you'll
find
a
helpful,
I
think
even
intro,
as
well
as
the
emerging
developers
and
operations
guide
for
the
concordance
event,
sourcing
framework
for
awesome
cloud
and
there's
even
a
great
resources
section
here
that
links
you
out
to
some
of
the
classic.
A
You
know
documents
that
really
help
to
shape
the
space,
taking
a
big
step
back.
You
know.
Why
are
we
spending
time
on
the
call
talking
about
this?
You
know
one
of
the
things
that
we've
always
really
that
as
part
of
the
core
vision
for
webassembly,
that's
really
resonated
with
us
as
a
team
is
this
that
webassembly
is
going
to
transform
all
parts
of
application
development,
not
just
serverless
functions,
there's
so
many
other
types
of
software
architecture
like
microservices
event
sourcing,
where
we're
already
building
our
applications
with
webassembly.
A
To
do
this,
there
was
a
talk
we
did
at
the
last
kubecon
where
we
showed
the
back
end
of
cosmotic,
and
we
showed
that
it's
all
built
on
wazen
cloud
in
webassembly
I'm,
using
this
very
same
event,
sourcing
framework
that
we've
just
continued
to
iterate
on
and
emerge
from
there
Kevin
is
there
anything
you'd
like
to
add
along
those
lines
around
the
sort
of
like
high
level
strategic
Vision
here
for
where
we're
going.
B
Yeah
I
mean
the
the
main
motivation
here
is
to
make
it
easy
for
people
to
build,
distributed.
Event,
Source,
apps
event.
Sourcing
is
hard
enough
to
do
right
when
you
don't
when
you're,
when
the
framework
is
already
taken
care,
it
isn't
taken
care
of
for
you
and
it's
just
it
work.
It
gets
worse
when
you
have
to
do
everything
on
your
own.
So
part
of
what
we're
trying
to
do
here
is
not
only
make
it
easier
to
do
event,
sourcing
applications,
but
to
show
how
you
can
build.
B
Frameworks
and
platforms
like
this
on
top
of
wise
and
Cloud
to
you
know,
make
developers
lives
easier
and
I'll
be
giving
a
talk
on
wasmcloud
and
event
sourcing
and
concordance
at
kubecon
in
a
couple
of
weeks.
So
what
I
just
went
over
is
kind
of
a
quick,
condensed
version,
but
I'll
be
going
into
more
detail
on.
A
Yeah,
that's
maybe
a
good
segue
here,
maybe
a
little
out
of
order,
but
just
a
quick
preview
of
some
of
the
upcoming
events
where
you
can
catch
up
with
the
team
this
week,
Bailey
Hayes
and
Brooks
Townsend
are
both
in
devops
days
Nashville.
So
if
you're
in
that
area
feel
free
to
catch
up
with
them
down
there
and
then
I'm.
Looking
ahead,
two
weeks
out
to
Sunday
the
17th
or
the
16th
we've
got,
Cloud
native
rejects
kicking
off
I'm.
Sorry,
this
is
April.
A
17Th
is
when
we're
speaking
I
think
that's
the
Monday
there.
You
can
find
Brooks
and
Taylor
talking
about
using
wasm
now
and
then
Taylor
later
chatting
about
the
the
post
kubernetes
world.
A
You
know
looking
at
what
web
assembly
looks
like
from
there
moving
into
April
18th
there's
a
number
of
talks
that
will
be
featuring
wasmcloud
and
some
of
the
Watson
Cloud
community
members
to
highlight,
let's
start
with
Bailey
Hayes
opening
up
the
conference
with
evolution
of
laws
and
past
present
and
future
I'm
excited
to
announce
if
you
didn't
notice
yet,
but
I
was
able
to
convince
Kelsey
Hightower
one
of
the
OG
fathers
of
kubernetes
to
give
the
wasem
day
opening
keynote,
then
later
in
the
day,
we'll
see
Jordan
rash,
I'm
talking
about
zero
trust,
microservices
with
wasm
and
wireguard,
a
demo
that
you
may
have
seen
parts
of
here
I
know
he's
been
furiously,
working
on
that
and
building
out
some
better
demonstrations.
A
Jordan
I'll
give
you
a
moment.
If
you
want
to
Hype
your
talk
a
little
bit
more
to
do
that
and
then
Brooks
Townsend
has
got
a
lightning
talk
where
the
server
goes.
Nobody
Knows
I'm
sure
will
be
a
fun
and
exciting
talk
and
then
Sean,
Isom
occasional
wasm.
A
A
cloud
Community
attendee
is
going
to
be
doing
a
session
on
wasm
and
kubernetes,
and
if
you
didn't
have
a
chance
to
review
it,
we
actually
co-published
a
case
study
in
the
cncf
with
Adobe,
where
they
talk
about
some
of
the
Lessons
Learned
in
moving
microservices
to
Blossom,
Cloud,
so
I
think
that
was
a
pretty
exciting
and
then.
A
Finally,
on
the
as
we
move
into
the
kubernetes
main
session
on
the
19th
20
and
21st
on
Friday
in
Amsterdam
Netherlands,
you
can
find
Kevin
Hoffman,
giving
his
full
session
talk
about
distributed
event
sourcing
with
wasmcloud
Jordan
I'll
pass
to
you
real
quick.
If
you
want
do
you
have
anything
you
want
to
add
for
your
talk.
C
Cool
no
I
think
you
know
week
or
two
I'll
probably
have
a
better
idea
of
what
I'm
doing
with
my
life.
A
C
Really
focusing
on
like
problems
I
saw
early
days
is
like
in
a
sock
as
a
as
a
security
person,
and
you
know
stringing
scripts
together
with
pipes
and
and
redirects,
and
all
this
and
adding
that
with
the
supply
chain
and
really
just
like
diving
in
on
what
you
know:
zero
trust
means
and
I
think
Z
put
it
the
best
and
when
they
said
like
it's
not
about
mistrust,
it's
about
segmenting,
trust
and
I,
really
like
that
and
I'll
be
focusing
on
that
and
how
you
know.
A
Oh
thank
you
Jordan,
and
for
those
of
you
that
aren't
familiar,
Jordan
did
mention
z,
she's,
one
of
our
wonderful
community
members.
She
hangs
out
on
wasmcloud
slack
and
her
blog
is
a
great
if
you
ever
have
a
chance
to
to
look
at
this,
but
always
interesting
and
provocative
commentary
thoughts
and
things
like
that.
I'll
drop
that
into
I'll
drop
a
link
here
to
the
blog
right
into
Chat
friend,
but
it's
interested
and
then
I'm
on
the
agenda
today.
A
I
think
we
had
scheduled
an
update
around
wadham
but
I,
don't
believe
Taylor's
on
to
give
that
update
today.
A
So
we
may
just
postpone
that
one
to
next
week,
I
will
just
call
it
out
that
bottom
has
been
under
some
pretty
aggressive
development
in
the
last
few
weeks
and
Taylor
is
quickly
converging
on
his
his
view
of
a
1-0
here,
as
he
continues
to
build
around
all
the
open
application
manifest
and
really
realizing
this
Vision
inside
of
of
cosmonic
I'm,
sorry
inside
of
a
Watson
Cloud,
which
is
also
used
by
cosmonica
extreme
by
the
way,
not
that
anyone
cares
any
see.
A
Other
updates,
the
wozmio
videos
were
not
broadcast
live,
but
they
are
out.
There
are
some
phenomenal
ones
on
here.
The
two
sort
of
early
themes
of
of
where
people
seem
to
be
interested
are
around
the
component
model.
Bailey's
accumulated
almost
10
000
views
on
her
talk
and
garbage
collection.
A
There
there's
three
talks
here
that
very
realistically
are
about
garbage
collection
with
various
languages,
so
I
I
was
not
able
to
attend
this
event,
but
I
heard
it
was
phenomenal,
feel
free
to
check,
check
it
out,
and
you
know,
give
us
any
feedback
or
chat
about
it
on
our
slack
any.
Let
me
just
do
an
open
call
to
the
community
here.
A
What
does
oh,
so
Jordan's
question
Liam
said:
wadham
1-0
I've
never
thought
about
it,
but
what
does
wasn't
Cloud
want
to
look
like
I
I.
Think
that's
a
great
question.
Jordan
I
know:
Bailey
has
got
some
Dots
here
and
I'm
sure
Kevin
does
as
well
coming
out
of
kubecon.
We
actually
have
some
time
set
aside
to
plan
that
discussion
or
some
to
have
that
exact
discussion.
A
So,
look
for
maybe
some
ideas
there
over
the
next
few
weeks
and
we
can
go
from
there
open
open
floor
here.
Anybody
on
the
call
want
to
bring
anything
up
or
open
topics
coming
up
into
kubecon
here.
A
All
right,
well,
I,
hope
everybody
has
a
wonderful,
wasn't
Cloud
Wednesday,
because
we've
got
kind
of
a
quick
meeting
today
and
I
really
look
forward
to
seeing
many
of
you
at
kubecon
here
in
two
weeks
and
for
those
of
you
that
aren't
there
you
know
I'm
sure
we'll
be
we'll
have
a
ton
of
live
updates
and
the
WASP
Cloud
slack
will
be
the
place
to
pick
up.