►
Description
wasmCloud is a platform for writing portable business logic that can run anywhere from the edge to the cloud, that boasts a secure-by-default, boilerplate-free developer experience with rapid feedback loop.
https://wasmcloud.com
A
All
right,
hello,
everyone
welcome
to
awesome
cloud
wednesday
june
22nd
of
2022..
Today
we
are
going
to
get
started
not
with
a
demo,
but
with
talking
about
some
of
the
major
upgrades
that
are
going
to
be
coming
to
wasmcloud
by
the
end
of
this
week.
What
you
can
look
forward
to
how
you
can
find
communications
about
breaking
changes
and
things
like
that
so
to
get
started.
I
think
I'll
go
ahead
and
hand
it
to
steve
who's
going
to
talk
about
the
rpc
library
under
wasmcloud
was
and
bus
rpc.
B
Alrighty,
so
you
may
or
may
not
know,
wasn't.
Bus
rpc
is
a
library,
that's
included
by
actors
and
providers
and
provides
the
rpc
layer
for
sending
messages
on
top
of
nat's
communication
and
the
nas
library
until
recently
has
been
pretty
much
async,
sorry
synchronous,
only
the
rest,
nas
client,
and
they
they
had
it.
Now
they
had
said
they
were
interested
in
in
rewriting
the
rewriting
it
to
be
fully
async,
but
wasn't
happening.
B
So
we
wrote
our
own
called
that's
afloat
as
to
kind
of
bridge
the
time
which
is
basically
a
rewrite
of
the
nets.
B
Rus
client
to
use
rust,
async
and
we've
been
using
that,
for
I
don't
know
six
six
months
or
so,
and
but
the
nas
team
has
been
diligently
working
on
async,
that's
and
we've.
Our
team
has
contributed
a
bit
to
to
that
library
and
it's
now
ready
enough
for
production.
So
we've
we've
changed
our
infrastructure
in
wisem
cloud
to
use
the
new
async
nats
library
and
get
rid
of
via
float
library,
which
was
just
a
temporary
thing
anyway,
and
we're
testing
that
now
so
right.
B
Now
it's
in
a
in
a
few
prs
in
weld
and
examples
and
capability
providers
there
are
and
interfaces
it's
not
fully
released
yet,
but
when,
when
we
do
probably
either
this
week
or
next
week,
there
will
be
a
couple
of
breaking
api
changes,
though,
because
the
new
nasa
library
has
some
different
symbols,
so
we'll
have
we'll
have
release
notes.
It's
in
general.
It'll
only
take
you
five
minutes
to
to
do
the
changes,
so
it's,
but
it
will
be.
It
will
be
some
breakage
when
you
upgrade
western
bus
rpc
to
0.9.
B
The
protocols
are
all
the
same,
so
you
don't
have
to
upgrade.
You
don't
have
to
upgrade
immediately,
but
when
you
do
you'll
find
you'll
have
to
upgrade.
If
you've
built
your
own
custom
interface,
you
have
to
do
an
interface
and
your
actor
or
interface
and
your
provider
at
the
same
time,
because
the
interfaces
also
depend
on
that
library.
B
A
Steve,
I
actually
have
a
question
and
a
comment
so
here
I
pulled
up
the
on
your
your
branch.
That
branch
that's.
A
To
async
nats
the
change
log
under
rpc.rs.
This
is
where
all
the
breaking
changes
go.
A
And
looking
here,
I
just
kind
of
did
like
a
I
just
kind
of
did
a
quick
scroll
through
this.
If
you,
it
looks
like
a
lot
of
the
changes
that
you
need
to
do
is,
if
you
have
a
capability
provider
that
also
used
the
a-nats
re-export.
A
B
So
one
change
that
every
provider
will
need
to
do
is
that
the
provider
main
function
has
one
new
parameter,
so
that's
adding
an
optional
string
that
we
can
use
to
add
to
traces.
So
another
thing
that's
going
in
this
change
is
we're
adding
open,
telemetry
tracing
in
both
the
host
and
wisem
bus,
rpc
and
and
because
it's
in
wasmbus
rpc,
it
means
every
capability
provider
will
pick
up
open,
telemetry
for
free.
B
So
if
you
start
adding
tracing
and
you'll
be
able
to
do
end
to
end
spans
across
your
distributed
wasm
cloud
network,
so
the
the
extra
parameter
to
the
provider
main
function
was
for
that
purpose
other
than
that
most
capability
providers,
probably
don't
and
actors,
may
not
need
any
change
at
all,
except
for
a
recompile.
B
If
you
did
happen
to
use
the
a
nats
symbol
which
was
a
re-export
of
the
afloat
library,
then
there's
some
name
changes,
but
they're
really
just
name
changes
and
I
think
that'll.
So
that's
probably
in
like
the
one
or
two
percent
use
case.
So
probably
for
almost
everybody,
the
only
real
change
will
be
adding
a
parameter
to
provider
main
function.
A
Okay,
that's
really
good
to
know,
that's
really
not
a
bad
upgrade
at
all,
but
we
can
definitely
like
highlight
slash
bold
this
one
just
to
say
whenever
you
recompile
you're,
just
gonna
need
to
add
a
friendly
name,
you
should
be
good
to
go
for
most
providers
awesome.
Well,
I
also
kind
of
had
a
comment
and
just
that,
it's
you
know
with
this
and
last
week's
call
about
webassembly
components.
A
It's
really
exciting
to
see
a
lot
of
these
things
that
we've
kind
of
custom
built
in
the
meantime,
get
officially
picked
up
and
supported
and
and
to
a
point
where
we
can
replace
the
the
custom
logic
that
we're
writing.
It's
it's
really
exciting
to
get
to
replace
these
things
and
and
get
right
down
to
doing
what
we
do
best,
which
is
working
on
awesome
cloud,
the
distributed
platform
and
not
as
much
managing
and
underlying
rpc
or
a
custom,
nas
client,
or
anything
like
that.
A
So
I
guess
it's
probably
worth
probably
it's
worth
giving
thanks
to
steve.
I
know
it
was
tomas
and
one
other
person
from
the
nats
team.
That's
really
working
hard
on
the
async
gnats
rewrite
is
that
who
was
the
other
person.
B
Yeah,
there's
a
casper
and
there's
a
there's
a
there's,
a
few
folks.
I
think
a
lot
of
the
team
is
working
on
it,
but
casper
buyer.
A
Nice
yeah,
I
just
figured
we
might
as
might
as
well
throw
them
a
thank
you,
because
they're
working
really
hard
on
on
this
client
and
making
it
better
and
better
for
everybody.
B
B
A
Yeah
it'll
be
that'll,
be
exciting,
too,
to
bring
in
some
more
more
jet
stream
stuff.
Just
for
you
know,
clarity,
if
you
haven't
run
or
looked
into
the
setup
that
you
use
with
wasmcloud
just
streams.
The
additional
features
don't
require
anything
other
than
running
the
nat
server
with
the
js
or
jetstream
flag,
which
is
already
what
we
ask
you
to
do
in
our
like
intro
documentation.
So
there's
really
nothing
additional.
You
need
to
do
to
get
all
the
benefits
of
maths
there.
A
All
right:
well,
I
just
wanted
to
kind
of
talk
about
something
a
little
bit.
It's.
A
Yeah,
that's
right
stewart
I
did
actually
get
a
fix
into
the
the
async
nas
client,
which
is
fun
I'll,
show
up
in
the
contributor
list.
A
I
want
to
talk
about
something
a
little
tangential
to
this
we're
going
to
be
releasing
wasmcloud
0.55
alongside
wasn't
bus,
rpc
0.9-
and
you
know,
we've
done
some
due
diligence
here
to
make
sure
that
you
know
this
isn't
a
required
thing.
You
need
to
do
to
remain
compatible,
but
some
key
features
that
you'll
get
by
moving
to
watson,
cloud
55
and
the
newest
version
of
our
providers
and
awesome
bus
rpc
is
the
open,
telemetry
tracing
support
that
you've.
Seen
in
the
last
couple
of
meetings,
I
think
it
was
two
meetings
ago.
A
We
showed
off
the
full
the
full
hotel
trace
through
kv
counter,
which
is
really
exciting.
If
you
haven't
seen
that
yet
we
will
you'll
have
to
go
back
and
check
out
that
video
once
we
post
it,
but
as
soon
as
you
upgrade
to
the
newest
version
here,
you're
getting
that
automatically
there's
nothing
additional
that
you
need
to
do,
and
here
in
the
hotel
folder.
We
actually
have
a
little
bit
of
a
guide
on
on
how
to
set
up
that
stuff,
just
in
a
docker
compose
to
keep
it
simple.
A
And
then,
if
you
already
have
your
own
open,
telemetry
stack,
then
you'll
probably
you'll
know
how
to
integrate
that
you,
I
guess
just
to
elaborate
on
that.
Just
a
little
bit
more,
you
just
specify
the
exporter
for
the
hotel
exporter
endpoint.
You
know
you
point
that
to
your
own
custom
exporter,
so
just
to
make
another
one
or
one
or
two
comments
there
kevin.
You
know
our
very
own,
kevin
hoffman
has
put
in
a
couple
of
fixes
to
the
host
around
dispatching
rpc
to
actors.
A
So
hopefully,
hopefully
we
can
get
some
performance
numbers
published
around
that
to
show
you
it's
a
it's
a
small
difference,
but
to
show
you
some
of
the
difference
with
the
the
newest
versions
as
usual
as
soon
as
the
the
55
version
of
the
host
is
released,
you'll
be
able
to
find
release,
notes
and
and
downloadable
tar
balls
under
the
releases
section
in
github
we'll
get
some
of
our
instructions
updated
on
the
website
as
well
as,
if
you
go
to
wasmcloud.dev,
you
can
go
to
the
releases
section
to
get
just
kind
of
a
bird's
eye
view
on
what
we
added
what
we
changed.
A
I
think
that's
all
that
I
had
from
some
of
the
more
for
the
more
exciting
upgrades
that
are
coming
with
with
async
gnats
and
the
host
anybody
have
any
questions
or
want
to
dive
deeper
in
any.
You
know
dive
deeper,
a
little
in
the
rpc
or
anything
like
that.
A
All
right
short
week
also
maybe
a
little
short
meeting.
I
have
a
couple
of
really
just
kind
of
a
fun
community
announcement
for
from
the
the
cosmonic
side,
which
you
know
us
being
at
open
source
comp.
We
were
really
proud
about
how
how
cool
the
booth
is
shaping
up
and
and
how
we're
showing
us
up
at
some
of
these
conferences.
We're
still
there
if
anybody
lives
in
austin
wants
to
come
check
us
out.
A
Look
for
the
cosmonaut
booth,
we're
talking
about
that
and
and
wasn't
cloud
of
course
here
is
a
picture
of
our
ceo
liam
and
and
engineer
taylor
thomas
who
of
course,
couldn't
be
here
since
they
are
manning
the
booth
but
very
happy
getting
some
good
food
out
in
austin,
and
I
didn't
ask
for
their
permission
to
share
that.
A
So,
hopefully
they
are
fine
with
me
sharing
their
smiley
faces,
but
that
is
all
that
I
can
think
of
from
the
from
the
wasm
cloud,
cosmonic
community
side
of
things
for
now
other
than
that
keep
an
eye
out
a
little
bit
later
this
week,
we're
going
to
be
releasing
a
blog
post
about
actually
this.
Let's
see
this
sunday,
the
26th
yeah
this
sunday,
the
26th
is
actually
the
three
year
anniversary
of
wasmcloud
from
when
it
was
first
released
under
the
name
waxo
suit.
A
You
can
find
kevin's
blog
post
about
where
he
talked
about
the
introduction,
but
we're
also
going
to
be
writing
a
little
retrospective
going
back
on
on
three
years
of
wasn't
cloud,
what
we've
learned
and
and
how
far
we've
come
so
that
that
should
be
a
fun.
Read,
we'll
be
putting
that
out.
If
you
haven't
seen
any
of
our
developer
blogs
yet
they're
out
on
the
wasmcloud.com
site.
A
A
So
that
is
all
that
I
think
okay,
now
for
real.
I
think.
That's
all
that
I
had
from
the
community
side.
Does
anybody
else
have
anything
from
the
wasm
community
that
you
wanted
to
anybody
wanted
to
bring
up
and
chat
about
today.
A
D
See:
okay
yeah.
Most
of
my
experience
with
the
platform
has
been
just
like
reading
the
internet,
because
I'm
really
like
interested
in
how
it's
working-
and
I
came
across
the
w-a-p-c,
as
kind
of
like
the
protocol
for
executing
remote
procedure
calls,
and
I
was
wondering
if
that
was
essentially
the
backbone
of
how
active
to
act.
The
communication
is
done
in
the
western
cloud.
A
Yeah
wapc
was
actually
a
protocol
that
we
used
to
use.
Oh
hey
liam,
do
we
that
we
used
to
use
under
wasmcloud,
hey
liam,
welcome
hey?
How
are
you
good?
Are
you
tuning
in
from
the
booth.
C
We
are
at
the
cosmonautic
booth
at
open
source
summit
here
taylor
and
I
having
a
good
time
I'll,
go
back
up,
muted,.
A
Nice
well
liam,
we
actually
just
showed
off
the
the
booth,
the
the
picture,
and
then
your
ta,
your
picture
with
taylor
happy
smiling
faces.
So
that's
great
to
catch
up.
Richard
just
asked
a
great
question
about
about
ypc
the
the
library
and
wondering
if
it
was
really
similar
to
how
we
run
rpc
between
actors
and
providers
and
that's
exactly
that's
exactly
right.
A
Excuse
me:
when
we
moved
to
the
dot
50
release
with
the
elixir
version,
we
ended
up
adapting
ypc
a
very
similar,
very
similar
rpc
mechanism,
for
our
wasn't
cloud
actors
and
the
whole
rpc
framework,
we're
calling
it
you
know
with
with
wasmbus
and
r
and
and
ypc.
That's
really
all
in
a
temporary
space.
A
It's
one
of
those
things
like
using
the
a
nats
library
or
using
or
using
smithy
instead
of
components,
and
things
like
that,
where
it
fills
a
gap
that
the
ecosystem
doesn't
really
have
today,
which
is
passing
arbitrary,
byte,
bytes
back
and
forth
in
in
favor,
and
then
you
know
deserializing
them
as
strongly
type
structs
and
rust
and
everything.
But
all
of
that
is
planned
to
be
replaced
by
this
exploration.
A
That
taylor
has
kind
of
done
with
webassembly
components
and
the
reason
why
I'm
moving
there
is
that
the
the
important
thing
is
instead
of
having
a
for
from
our
perspective
instead
of
having
this
proprietary
rpc
framework
underneath
us,
which,
even
if
you're
not
exposed
to
it's
still
something
that
you
need
to
compile
your
actors
in
mind
or
with
that
in
mind.
D
A
Great
question
happy
to
answer
any
other
questions
too.
We
got
a
couple
people
here
from
the
wasmcloud
team.
A
All
right:
well
then,
it
may
be
a
quick
one
today,
but
we
we
got
a
lot
of
good
discussion.
Hopefully
you
are
looking
forward
to
some
of
the
new
updates
with
wasmbus
rpc
and
the
new
version
of
the
host
looking
forward
to
get
you
all
trying,
I'm
looking
forward
to
getting
you
all
to
try
the
open,
telemetry
stuff,
which
is
really
exciting.
I'm
gonna
go
ahead
and
stop
recording.
A
We
can
all
hang
out
looking
forward
to
hearing,
maybe
a
little
bit
more
from
liam
about
how
the
booth
is
going
and
everybody
have
a
good
rest
of
your
day.